Sie sind auf Seite 1von 8

Hi Raju, Below are the Real Time Tickets Reward If Help Full....

Tickets I need few examples of real time L1,L2 ang L3 tickets.(2 examples for each priority will do). Examples like shipping point determination is not determined...possible reasons could be shipping point not assigned in org structure, shipping point determination not maintained (shipping cond + loading group + plant) etc.. 1. Someone coming back to us that they cannot create a delivery note for xyz company or cannot use VA01 transaction. SOL : Basically authorization issues...usually we analyse what rights he would require and pass on the same to basis team to give the adequate authorization. 2. Sometimes endusers are not completely aware of the business process leading to not performing a step which is required in the flow of material/documents and surely leading errors in subsequent steps. We need to figure out the same and take necessary action to fix the flow in some cases and surely get the user gear up to the correct process. 3. In many cases we have to analyse why a particular document was not created either manually or through automated process. Example be like why the delivery document creation failed ? 4. Cases are also raised related to customized development where it does not perform as required like a particular should have been in the report but is not there..or any sort of bugs etc. It requires to analyse the development and find the casue of the issue. 5. Enhancements..they usually contribute the most in support projects. I feel in software industry we cannot have a complete specification..something is surely misinterpreted or missed out, which is usually realised after few months of go live. They are usually classified as enhancements ..leading to small modifications or developments. Case 1 : Material: X Plant : Y Stock in Storage Location - A : 1 Unit Stock in Storage Location - B : 1 Unit Sales Order N0 1111111111 is created against storage location A & Sales Order N0 2222222222 is created against storage location B & In Case 1 I am able to do availbility check for Both the sales order as stocks are available in both the storage location

In Case 2 Carried out availability check for sales order 1111111111 - Shedule lines were generated against stocks in Storage Location A. Now I transfer the stock from Storage - A through 309 movement to some other material no - Z Problem / Issue. Since no stock is availble in Storage - A , Sales Order which was created for Storage A pulls the stock from storage B for availablity to promise. Now In this case I am not able to carry out availabilty check for Sales Order 2222222222 inspite having stocks in storage - B as it has been confirmed/pulled by sales order 1111111111. Looking for following solution. [1] I dont want Availability check at Plant level - I need at Storage Section Level. [2] As soon as 309 movement is carried out or stock is moved out to any other storage or Plant then - Shedule lines for Sales Order 1111111111 should get deleted automatically as the material in storage location is no more available. Solution: ATP at SL level, you need to insert the SL at item level of the sales order. This will restrict the search. 2. For automatic recheck of ATP, I can suggest a batch job of V_V2 transaction .

Case 2: Back Order 1. When a sales order is created by end user there is no material available. I checked this by checking schedule line the confirmed quantity shows 0 qty at schedule line. Soln: Backorder processing Logistics-SD-sales-Environment-backorders-backorder processing-enter sales order number 2.END USER GOT A PROBLEM WHEN CREATING A SALES ORDER FOR MAKE TO ORDER QUANTITY ENTERED IN SALES ORDER IS NOT PICKED AUTOMATICALLY AND IS ALSO NOT PICKED WHEN ENTERED MANUALLY SOLN:- SOLVED BY GOING TO MM02 SALES/GENERAL PLANT VIEW CHANGE AVAILABILITY CHECK TO INDIVIDUAL REQUIREMENT (02) FROM DAILY REQUIREMENT (01) IN MATERIAL MASTER 3.In the client site complete SAP system got struck by giving error: short dump When creating a sales order it didnt allow me to save any order Soln:I solved it first by going to lt22 and came to know its due to short dump Caused by S687 Infostructure Goto img->logistics general->logistics data warehouse->updating->updating control->Activate update chhose sales and distibution double click on u r infostructure radio button and select asynchronous only

synchronous is not recommended. Here s687 is selected synchronous which gave the error. 4. When customer returned goods.client want to make a gate pass by which u can track the material returned or received Soln: Go to Tcode LECI and enter the details about the truck like time,licence plate,driver and save & print it. There could be many such cases. Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three severity High, Medium and Low. Each and every severity as got its time limits before that we have to fix the error. The main job of the supporting consultant is to provide assistance on line to the customer or the organization where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand, to analyze, to actuate and to give the right solution in right time. This is the job of the support consultant. The issues or the tickets (problems) which are raised is taken care of on priority basis by the support team consultants. The work process in support projects are given below for your reference. 1. The customer or the end user logs a call through any tool or by mail (RADIX). 2. Each one of the support team is a part of support group. 3. Whenever a customer logs a call he /she has to mention to which work group (by name). 4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top, High, Med, Low, None) 5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR (Transport Request through the basis admin) 6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process. These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client. An example: Tickets in SD can be considered as the problems which the end user or the employees in the company face while working on R/3. Tickets usually occur during the implementation or after the implementation of the project. There can be numerous problems which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline. To begin with, we should give "TICKET" to you for not knowing it. Here is an eg of a ticket raise:

End user is not able to 1. Create Sales order for a customer from a new plant, since shipping point determination is not happened. (Without shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING). He raises a ticket and the priority is set in one of the below: 1. Low 2. Medium 3. High. Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant. You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it. Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support. Real Time Experience: 1. Billing Document not released to Accounting. The error was due to material master not maintained appropriately. The scenario was analysed & the result was if Profit Centre is maintained, but MRP type is not maintained, it does nor releases Billing document to accounting in some cases. It is strange, but yes, its true. There were around 85 - 90 invoice & ideally the solution would be cancelling Invoice, Reversing PGI, Cancelling the delivery & cancelling order & redo every thing again after rectifying Material master. This was happening for 2 material Master newly created. But we selected alternative route i.e in Debug mode, we forced the profit center in billing document & then it released to accounting. 2. Sales Order incomplte for Material Availability Date, Actual Delivery date & so on.............. This was another classic case where this was odd. I verified & was clear that incompletion log has no problem & these are not included in incompletion log. This again was an master data issue. The reason was Availablity Check was not maintained in Material Master & I had spend 3 days analysing configuration, before checking material master data. It was a learning that I should have checked the master data also, as however expert an user may be, even he is human & can make error. 3. Common error in an new implementation project with users new to SAP is Billing is not happening. The highest possiblity is PGI not done or Billing document already created, but overlooked by user in hurry. The best solutiuon is to train the end user to check the document flow, before bringing it as a issue. 4. Modification in Pricing Procedure Calculation or addition of new condition type. This is very subjective to clients requirement & not possible to explain it here. Regards.... Praveen Kumar.D

Hi Friend, There are many tickets you get on a support project. I am giving you a few examples: 1. Billing Document not released to accounting / Accounts determination: To resolve the error, you can analyze account determination in the billing document. Process:

Goto T.Code: VF02 & Enter Invoice number Next (On the top most strip) goto Environment Next (Select Environment) go to Account determination Next (In Account Determination) select Revenue Account Determination (first option) This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined. 1. VKOA not maintained for required combination Solution: Maintain the combination in VKOA. 2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA). Solution: Option 1 (Standard solution): step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order step 2: Maintain Customer master / Material Master correctly. step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing. Option 2: Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting. 3. Account Key not maintained in Pricing Procedure: Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account. 4. Billing Document not being released to accounting -In Material Master, there is some link between Profit Centre & MRP Type. If one of it is not maintained, erratically few documents get stuck while releasing Billing Document to accounting. Few of course get posted. Solution1: Cancel Billing Document --> Reverse PGI --> Cancel Delivery --> Block the sales Order & Create new sales Cycle all over again after rectifying Material master. Solution 2: (Temporary Solution) In Debug mode in Billing, force the Profit Center in Billing Document with the help of Abaper. But ensure Material master is rectified. From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client to upload through LSMW / SCATT / BDC. In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message: 1. G/L account not found 2. Cost Element not maintained for G/L account. In both the above cases, FI consultant requires to take corrective action.

few are, Issues related to Customer Master data: 1. what is the impact of leaving customer pricing procedure & customer statistic group blank in customer master --> sales area data --> sales tab: If Customer Pricing Procedure is left blank, Pricing will not be determined. If customer statistic group is left blank, then data will not flow to standard reports. 2. Who maintains reconciliation account in customer master? Ideally, reconciliation account is maintained by FI person, but if SD person is authorized & has the knowledge of which reconciliation account to be maintained, then even SD person can maintain the same. 3. Terms of payment appear in Company Code Data & sales Area Data. What is the impact of each? why is it not populated automatically, once it is maintained at either field? Terms of payment from company code data is for reporting purpose & it is from sales area data that it flows to sales order. It is a standard feature of SAP that it is not populated automatically if maintained at either of the field, but it is a must in sales area data & can be skipped in company code data. 4. Unable to select Sales Area for Customer Master Creation? Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions

Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error. The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant. The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants. The work process in support projects are given below for your reference. 1. The customer or the end user logs a call through any tool or by mail (RADIX). 2. Each one of the support team is a part of support group. 3. Whenever a customer logs a call he /she has to mention to which work group (by name). 4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None) 5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin) 6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process. These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client. An example: Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline. To begin with , we should give "TICKET" to you for not knowing it. Here is an eg of a ticket raise: End user is not able to 1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING). He raises a ticket and the priority is set in one of the below: 1. Low 2. Medium 3. High. Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it. Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.