Tuesday, September 7, 2010 Real time tickets in SAP SD Examples of Tickets, 1) Billing Document not released to accounting / Accounts

determination: To resolve the error, you can analyze account determination in the billing docum ent. Process: Go to T.Code: VF02 & Enter Invoice number Next (On the top most strip) go to Environment Next (Select Environment) go to Account determination Next (In Account Determination) select Revenue Account Determination (first opti on) This will list all the condition types in the Billing document & analyze each co ndition & check for which G/L accounts is not determined. Possible errors: 1. VKOA not maintained for required combination Solution: Maintain the combination in VKOA. 2. Account Assignment of Customer / material not maintained in Customer / Materi al Master (If maintained in combination in VKOA). Solution: Option 1 (Standard solution): step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel S ales 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 chang e mode of Billing document, which will release Billing Document to Accounting. -----------------------------------------------------------------------------------------------2) 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 procedu re, it will not be post the relevant condition type to G/L account. FI consultant requires to take corrective action. -----------------------------------------------------------------------------------------------3) 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 Bil ling 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 ABAP-er. 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 cl ient to upload through LSMW / SCATT / BDC. In Billing Document in change mode (in the first screen where we enter Billing D ocument number), on the top most left hand corner, take a dropdown on Billing Do cument & select Release to accounting. Here you can get the under mentioned poss

.html September 7. Possible errors: 1.blogspot. ( Without Shipping point the d ocument becomes INCOMPLETE and he will not be able to proceed further like DELIV ERY. Cost Element not maintained for G/L account. Solution: Option 1 (Standard solution): step 1: Cancel Billing Document --> Reverse PGI -> cancel Delivery --> Cancel Sales Order step 2: Maintain Customer master / Mate rial Master correctly. it will not be post the relevant condition type to G/L account. Billing Document not being released t o accounting -. Option 2: Force the Account Assignment Group of Customer / Material through Debug in ch ange mode of Billing document. 4. Posted by Sappy Guy at 8:17 PM 1 comments: Sappy Guy said. which will release Billing Document to Accounting . Few of course get posted.com/2010/09/real-time-sap-sd-tickets-part-2.Code: VF02 & Enter Invoice number Next (On th e top most strip) goto Environment Next (Select Environment) go to Account deter mination Next (In Account Determination) select Revenue Account Determination (f irst option) This will list all the condition types in the Billing document & an alyze each condition & check for which G/L accounts is not determined. you can analyze account determination in the billing document. erratically few documents get stuck whi le releasing Billing Document to accounting. Process: Goto T. VKOA not maintained for required combination Solution: Maintain the c ombination in VKOA. Solution1 : Cancel Billing Document --> Reverse PGI --> Cancel Delivery --> Block the sale . Please find more real-life Support tickets faced by me in this link http://sapsdexpert. FI consultant requires to take corrective action. 2. 3. but d o not have account key maintained in pricing procedure. G/L account not found 2. but if condition type. which are to be posted to account. If one of it is not maintained. sin ce shipping point determination is not happened .. Possible errors: SP configuration not done for the new plant. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA). Account Key not maintained in Pricing Procedure: Impact: This may create acco unting document. -----------------------------------------------------------------------------------------------4) End user not able to create sales order: End user is not able to create Sales order for a customer from a New plant .In Material Master. there is some link between Profit Centre & M RP Type. 2010 8:43 PM Post a Comment Links to this post Create a Link Newer Post Older Post Home Subscribe to: Post Comments (Atom) Real Time Issue: [b]Billing Document not released to accounting / Accounts deter mination[/b]: To resolve the error. BILLING).ible message: 1. step 3: Recreate sales Order --> Delivery --> PGI --> Inv oicing.

Once the pricing procedure is determined. system will through an error message. Pricing Procedu re: It is recommended to copy a similar pricing procedure & make the necessary c hanges in new pricing procedure. LSMW. & so on .. During new implementation. the configur ation will be done in spro as follows: IMG --> Sales & Distribution --> Basic Fu nction --> Pricing Control --> Condition Table (select the required fields combi nation. . Condition records are fetc hed. etc. Sales org 2000 & sales org 2000. G/L accou nt not found 2. Here we assign the condition table to access sequence.In SD. we nee d not create a new condition type. Step 4: a. which is required to be maintained by Core team / per son responsible from the client. the condition record s can be uploaded using tools like SCAT.... Condition record: Conditio n record is a master data. on the to p most left hand corner.s Order & Create new sales Cycle all over again after rectifying Material master . Write-up on Pricing . combined Distribution channel & combined divi sion. Here you can get the under mentioned possible message: 1. similarly for distribution channel & Division. so that the Sales ar ea combination is available for assignment to Sales Document Type. Step 2: Access Sequence: If existing access sequence meets the requirement. Considering the requirement for new sequence. b.Code: FS00. Customer Pricing Procedure is determined from Customer Master. Sales Area is determined in Sales Order Hea der Level. In both the above c ases. It is assumed that document pricing procedure. we need not create a new access sequence . It is always r ecommended to copy an existing similar condition type & make the necessary chang es. the configuration will be done i n spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing C ontrol --> Access Sequence (Access sequence is made up of Accesses (Tables) & th e order of priority in which it is to be accessed. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. If appropriate condition records are found. But ensure Material master is rectified. Considering the requirement for new condition type. Here we assign Access sequence to Condition type. take a dropdown on Billing Document & select Release to accounting. In SD . FI consultant requires to take corrective action. G/L account being Master data has to be created in each client to upload through LSMW / SCATT / BDC. which will store condition record). for eg: Sales org 1000 & sales org 1000. Configuration for determining pricing procedure in SPRO is as f ollows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure. In Billing Document in cha nge mode (in the first screen where we enter Billing Document number). Step 3: Condition Type: If existing condition type meets the requirement. From FI Side. [b]Sales Docum ent not assigned to Sales Area[/b]: SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Documen t Types --> Assign sales order types permitted for sales areas (do ensure to mai ntain combined Sales organization.. 5. Considering the requirement for new Pricing Procedure. Solution 2: (Temporary Solution) In Debug mode in Billing. If Man datory pricing condition is missing. are in place. the configuration will be done in sp ro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Contr ol --> Pricing Procedure --> Maintain Pricing Procedure. force the Profit Ce nter in Billing Document with the help of Abaper. the price is determined. Cost Element not maintained for G/L account. the steps to configure Pricing procedure are as under: Step 1: Condition table : If existing condition table meets the requirement. Considering the requirement for new condition table. [b]Pricing[/b]: This is very specific & differs from client to client & may also differ based on scenari o. Pricing Procedure: A fter maintaining the pricing procedure the next step will be determination of pr icing procedure. you require to check that all the G/L account has been maintained through T. the configuration will be done in spro as follows: IMG --> Sales & Distri bution --> Basic Function --> Pricing Control --> Condition Type. we need not create a new co ndition table.) [b]Issues re . customer pricing procedure . Pricing Procedure is determined based on Sales A rea (Sales Organization + Distribution Centre + Division) + Customer Pricing Pro cedure + Document Pricing Procedure. Docume nt Pricing Procedure is determined from Sales Document Type / Billing Type (if c onfigured).

to analyse. If customer statistic group is left blank. In summary. Pricing will not be determined. The main job of the supporting consultant is to provide assistance on line to th e customer or the organisation where SAP is already implemented for which the pe rson should be very strong in the subject and the process which are implemented in SAP at the client side to understand. These are the process.High. what I understand is that if any configuratio n or customization is required to solve the issue.This is the job of the support consultant. what is the impact of leaving customer pri cing procedure & customer statistic group blank in customer master --> sales are a data --> sales tab: If Customer Pricing Procedure is left blank. Unable to select Sales Ar ea for Customer Master Creation? Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. debugged by the support consultant or the team. Rajesh Banka Reward suitable points.lated to Customer Master data[/b]: 1. 37 38 or you can use the userexit CSO_P_DLVRT_GOODS_ISSUE_CREATE . 3. (Top.aut o PGI The above are few examples. reconciliation account is maintained by FI person. Terms of payment appear in Company Code Data & sales Area Data. 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.None) 5. 2. T-c ode SM36.sdn. The customer or the end user logs a call through any tool or by mail (RADIX). The issues or the tickets(problems) which are arised is taken care of on priorit y basis by the support team consultants. https://www.Low. 2. The work process in support projects are given below for your reference. 1. 4. once it is maintained at either field? Terms of payment from company code data is for reporting purpose & it is from sales area data th at it flows to sales order. Each one of the support team is a part of support group. then even SD person can maintain the same. but it is a must in sal es area data & can be skipped in company code data.Med. then data will not flow to standard reports. Each and every seviority as got its time limits before that we ha ve to fix the error.sap. Then after testing properly by generating TR(Transport Request through the basis adm in) 6. then the consultant have to w . M edium and Low. 3.to actuate and to give the ri ght solution in right time. The errors or bugs forwarded b y the end user to the support team are prioritized under three seviority High. It is a standard feature of SAP that it is not popul ated automatically if maintained at either of the field.com/irj/sdn/thread?threadI D=462513&messageID=3690162#3690162 Regards. Who maintains reconciliation account in customer m aster? Ideally. Then the error is fixed. Handling tickets is called Issue Tracking system. Whenever a customer logs a call he /she has to mention to which work group (b y name). What is the impact of each? why is it not populated automatically. 4. Then it is informed to the end user/customer/super user about the changes whi ch have moved to the production server by CTS process. but if SD per son is authorized & has the knowledge of which reconciliation account to be main tained. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions [b]Other queries[/ b]: Where is the control for Automatic PGI? For this you can set batch jobs.

Finally.php?t=991507&page=8 http://www. You would analyze the problem and identify th at the SP configuration has to be done for the new plant. You do the change and Req uest one more Transport to BASIS for QA client. http://www. What I have given is a small example. There can be numerous pr oblem which can occur in the production support and a person who is working in t he support has to resolve those tickets in the limited duration. Medium 3.com/showthread. every ticket ha s the particular deadline alert so your responsibility is to finish it before th at deadline.com/docs/12421334/Telugu-Srungara-Boothu-Kathalu . He raises a ticket and the priority is set in one of the below: 1. Once the cha nge is deployed in production the TICKET is closed.ork on DEV Client. High.com/showthread. The End user will test the same by creating a sales order for the new plant and approve it. You would request a transport for DEV CLIENT to BASIS. you request a transport to move the changes to PRODUCTION.docstoc. we should give "TICKET" to you for not knowing it.php?p=28278044 http://www.exbii. since shipping point det ermination is not happened . Low 2.exbii. then the end user will test it in the QA client and after app roval the BASIS consultant has to transport it to the PRODUCTION client. Reward points if useful.com/showthread. ( Without Shipping point the document becomes INCOM PLETE and he will not be able to proceed further like DELIVERY.exbii. Now you need to solve this ticket. Create Sales order for a customer from a New plant . You would get some real issues with severity HIGH in your day-day supp ort.php?t=11618&page=42 http://www. To begin with . An example: Tickets in SD can be considered as the problems which the end user or the employ ee in the company face while working on R/3. Here is an eg of a ticket raise: End user is not able to 1. Tickets usually occur during the im plementation or after theimplementation of the project. BILLING).