Descriptions of several standard cost condition and account configurations defined by SD-SAP

Vrps:
N in the standard version, Condition Type VPRs is used to retrieve the standard cost of the material.
N it is used as a statistical value by the pricing procedure.
N using condition Category G, VPRs accesses the valuation segment of the material master locating either the standard cost or the moving average cost, as specified in the material master.
N condition category S will always access the standard cost, while condition category T will always access the moving average cost.
N the profit margin is calculated using formula 11 in the pricing procedure. This formula subtracts the cost from the net value 2 subtotal.
 
Skto:
N in the standard system, Condition Type skto is used to retrieve the cash discount rate.
N it is used as a statistical value by the pricing procedure.
N table t052 is accessed using condition category E and an amount is calculated from the first percentage rate of the item payment terms.
 
Edi1 & edi2:
N the customer expected price can either be entered manually in the order, or retrieved from the incoming IDOC in an EDI environment.
N condition type edi1 is used to compare the net price for each item. Condition Type edi2 is used to compare the overall item value (net price * quantity ).
N calculation formula 9 is assigned to Condition Type edi1 in the pricing procedure. This formula tests for a maximum deviation of 0, 05 currency units.
N calculation formula 8 is assigned to Condition Type edi2 in the pricing procedure. This formula tests for a maximum deviation of 1.0 currency units.
N if the customer expected price differs from the automatically determined price or value by more that the maximum difference allowed, the system will regard this order as incomplete when it is saved.
N you may process lists of Orders having differences in prices, allowing the system to use or correct the price it determined.
 

What is the difference between VPRs (cost) and ek01 (actual cost) and where these are used?
VPRs
VPRs cost is mainly used to determine weather the material is having the standard price or moving average price
The condition type VPRs is labeled as a statistical condition in the pricing procedure.
In this, using the condition Category G, the condition type VPRs goes into the valuation segment of the material master and determines from here the standard or average price.
The condition category s always accesses the standard price whereas condition category T always accesses the average price.

Ek01

1) ek01 can be used as a basis for determining a price for the make-to-order item.
2) ek02 is a statistical condition which can used instead of VPRs to calculate the profit margin for the Assembly item.
3) Condition Type ek01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
4) Condition Type ek01 is selected for sales Document Type TA (Standard Order ). this means that the value from the cost estimate goes directly into pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated.

1) There must be a pricing procedure in the sales order. Otherwise, an error occurs during the sales order stage.

2) pricing procedure has various condition types, such as the unit price (pr01/pr00), tax (mwsi/Mwst), and discount (k004/k005/k007.

3) for the three types of condition types mentioned above, there must be an account key after pricing procedure. The price class ERL indicates revenue, and the traffic-to-tax class MWs indicates export items, and the discount class ERB indicates sales deduction.

4) vkoa connects the two functional components "price conditions" in the SD module with "Revenue Account": In the customer master data (for invoices, it should be payer) there is a customer account group, and sales data 2 in the material master data has a material account group. The three elements of the sales region are brought from the sales order. In this way, accounts can be written to the 001 table to automatically find accounting accounts.

5) for vkoa, The 4.6c standard configuration should be 1 --> 2 ---> 3 ----> 5 ----> 4. If the Table 001 ~ In 005, the same account key corresponds to a different g/L number, then the system will read the g/L subject and take it strictly in the finite order of "1 --> 2 --> 3 --> 5 --> 4" (this is called access sequence.

In the case of discounts, the first line records the accounts receivable, corresponding to the customer; the second line records the sales net income, corresponding to the sales subject; the third line records the discount subject, corresponding to the accounting subject determined by ERs under vkoa; line 4 records the sales tax, corresponding to the turnover tax subject. Because in pricing procedure, the discount class (k00x) is placed before the turnover tax (tax discount, unless the head enters the water, usually not to the buyer after tax discount ), therefore, the discount row in the accounting credential is placed before the tax.

FI/SD uses tcode vkoa to set posting accounts for billing. Users can create their own account definition data tables. The subjects are coa-level. The two condition types of Kofi/kofk are used to determine that they are respectively posted to the FI and CO creden. Because pricingproc. is the same as salesorg. associated, so the subject must first be salesorg in organization. level. The following accountkey is in the pricingproc. the association with different priceconditiontypes determines that the final sales revenue, discounts, additional charges, and preferences have passed to different subjects.