Real Time Issue: <b>Billing Document not released to accounting / Accounts determination</b>: 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. 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 / 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.

which is required to be maintained by Core team / person responsible from the client. Once the pricing procedure is determined. are in place. customer pricing procedure . Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). system will through an error message. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the necessary changes in new pricing procedure. Step 3: Condition Type: If existing condition type meets the requirement.In both the above cases. the condition records can be uploaded using tools like SCAT. <b>Pricing</b>: This is very specific & differs from client to client & may also differ based on scenario. Here we assign the condition table to access sequence. Considering the requirement for new condition type. the price is determined. the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure. <b>Sales Document not assigned to Sales Area</b>: . It is always recommended to copy an existing similar condition type & make the necessary changes. b. etc. During new implementation. which will store condition record). If Mandatory pricing condition is missing. Write-up on Pricing In SD. Condition record: Condition record is a master data. we need not create a new access sequence. LSMW. 5. Sales Area is determined in Sales Order Header Level. In SD. Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. FI consultant requires to take corrective action. Considering the requirement for new condition table. 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. Considering the requirement for new Pricing Procedure. the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. Customer Pricing Procedure is determined from Customer Master. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure. Condition records are fetched. It is assumed that document pricing procedure. Considering the requirement for new sequence.. the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination. Step 4: a.. . Here we assign Access sequence to Condition type. we need not create a new condition table. we need not create a new condition type. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. the steps to configure Pricing procedure are as under: Step 1: Condition table: If existing condition table meets the requirement. Step 2: Access Sequence: If existing access sequence meets the requirement.

Pricing will not be determined. 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. T-code SM36. for eg: Sales org 1000 & sales org 1000. but it is a must in sales area data & can be skipped in company code data. If customer statistic group is left blank.. reconciliation account is maintained by FI person. 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. but if SD person is authorized & has the knowledge of which reconciliation account to be maintained.. 4. similarly for distribution channel & Division..) <b>Issues related to Customer Master data</b>: 1. 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. Who maintains reconciliation account in customer master? Ideally. so that the Sales area combination is available for assignment to Sales Document Type. It is a standard feature of SAP that it is not populated automatically if maintained at either of the field. then data will not flow to standard reports. 2. 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. 3.auto PGI The above are few examples. /message/3690162#3690162 [original link is broken] .SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Document Types --> Assign sales order types permitted for sales areas (do ensure to maintain combined Sales organization. combined Distribution channel & combined division. Sales org 2000 & sales org 2000. Terms of payment appear in Company Code Data & sales Area Data. then even SD person can maintain the same. & so on . What is the impact of each? why is it not populated automatically. 37 38 or you can use the userexit CSO_P_DLVRT_GOODS_ISSUE_CREATE .