1. Table erdiagram used by Condition Technology
2. Description of the SD Pricing Process configuration (note that this figure is used to analyze the data Relation Diagram determined by the subject. Some table names may be incorrect for pricing)
1. The sequence numbers behind each table are customized operation orders;
2. The first step is to define the storage table (V/12, V/13, V/14) based on the allowed fields of the required table );
3. Step 2 defines the storage sequence as needed;
4. Step 4 is to set the data storage tables used in the storage sequence as needed;
5. Step 5 defines the condition type (pricing condition type) as needed, and specifies the storage sequence to meet the conditions; step 6 and Step 6 set the upper and lower limits of the condition type (pricing condition type) as needed (t685z );
7. Step 4 defines the process (pricing) as needed, and specifies the control data of the process (that is, specifying the condition type );
8. Step 1 defines the type of the Credential (tvkv) as needed );
9. Step 1 sets the type of the certificate corresponding to the order as needed. Multiple Orders can correspond to one certificate type;
10. Step 1 sets the type of the certificate corresponding to the invoice as needed. Multiple invoices can correspond to one certificate type;
11. Step 5 sets the Pricing Process for the sales documents as needed (t683v); Step 12 and step 10th define the conditional exclusion group (t684) as needed)
13. Step 1 sets the Price Condition Type (t684g) for the condition exclusion group as needed)
14. Step 4 sets the use of the exclusion group in the pricing process as needed (t684s)
3. Description of SD pricing process determination
Pricing confirmation is based on the order (or invoice) first) type locate credential type-confirm the pricing process based on the credential type and sales region-Get pricing control data based on the Pricing Process-exclude some pricing conditions based on the exclusion groups in the pricing process-according the rest of the pricing conditions take the storage order-read and maintain the pricing condition data first based on the relationship between the storage tables in the storage order-calculate the pricing after obtaining the non-computing-class pricing condition data
Recommendation link:
SD-description of the functions of 16 fields in the Pricing ProcessHttp://blog.csdn.net/CompassButton/archive/2007/08/25/1759141.aspx
Information about the SD pricing formula of SAP (strongly recommended, I will translate it if I have time)Http://blog.csdn.net/CompassButton/archive/2006/08/25/1115036.aspx
How to control the pricing conditions varies with users (some can be entered or not)Http://blog.csdn.net/CompassButton/archive/2008/01/20/2053976.aspx
How to shield or display cost display in SAP orders based on User PermissionsHttp://blog.csdn.net/CompassButton/archive/2006/08/15/1066287.aspx
Several standard cost condition descriptions and subject configurations defined by SAPHttp://blog.csdn.net/CompassButton/archive/2007/08/11/1738029.aspx
SD-how to extract SD pricing information by programmingHttp://blog.csdn.net/CompassButton/archive/2006/08/28/1132569.aspx