Requirement Description:
In the actual business, there is often a purchase and sales of the price increase or difference mode, for example, the car according to the configuration of high configuration, low configuration, for whether to choose the vehicle image configuration will have different price increases, the configuration of the computer is standard, the choice of different CPU or graphics card price difference is also different, this involves SAP VC management mode, VC is the abbreviation of Variant Configuration, we are accustomed to call variant configuration, VC involves classification, characteristics, configuration parameter files, Relevance (BOM, routing, class, characteristics, characteristic values), for procurement business, such as: the diameter or length of the purchased wood exceeds a certain value, the unit weight needs to be increased, how to maintain the variable price of configurable materials and how to apply it, and whether the variable price can achieve the difference of each purchase?
Test system version: SAP EHP7 ERP 60 test process.
Solution: Enable variable pricing for configurable items and configurable items.
The following is the variant-based configuration and testing process.
1. Configuration basis of variant **:
Variable pricing involves defining a conditional table, defining the order of access, assigning the table of conditions to the order of access, assigning the condition type to the order of access, and maintaining it to the corresponding pricing process, and the calculation scheme affects the pricing management of the purchase order.
1.1 Define the Condition Table:
Each condition table contains a set of key fields and sets of data storage rules. The following is an example of maintenance based on the purchase variant**:
Path: img->-material management->procurement-> conditions-> definition**Determine process -> maintenance condition table.
Condition Table 160 is a collection of vendors, purchasing organizations, factories, record categories, materials, and variants.
Table 161 of the conditions is a collection of merchants, purchasing organizations, information record categories, materials, and variants.
1.2 Define and view the order of access.
In actual business, a ** confirmation often requires several sets of keyword combinations, each combination has a wide range or a focus, and the program finds and confirms the required data in a certain order. This is the service of defining an access sequence, which consists of several condition tables.
Path: IMG > Material Management > Procurement > Conditions > Define ** Determine Process > Define Access Order.
The access order configuration contains the following data: header, access order, and condition table fields.
Once the access order is defined, it cannot be directly applied to the foreground maintenance data, it needs to be assigned to condition types. Only the conditional type that binds the access order can maintain ** data with t-code: vk11 (sales pricing), mek1 (purchase pricing), etc.
The above access order 0014 contains two condition tables, which are retrieved first if there are values in the condition table at 160 in order of priority.
1.3 Condition type va00 and the order of access of the assignment.
As mentioned above, the condition type va00 is bound to the access order 0014, and the access order 0014 contains two condition tables.
1.4 Maintain the pricing process, and add the variant condition type to the pricing process.
The pricing process is assigned to a calculation scenario, which then affects the purchase order.
2. Maintenance of classification characteristic values:
2.1 CL02 creates 300 classifications.
Transaction code: CL02
Path: SAP Menu -> Cross-Application Components -> Classification System -> Master Data ->CL02 -Class.
2.2 CT04 Create Properties.
Transaction code: CT04
Path: SAP Menu > Cross-Application Components > Classification System > Master Data >CT04 - Features.
This characteristic value is created for the material characteristics, such as: the length and width of the material, the configuration parameters of the computer, etc.;
Refer to the MMCOM field in the table vkond to create the purchase variant attributes.
2.3 CL02 to assign properties to classifications.
Transaction code: CL02
Path: SAP Menu -> Cross-Application Components -> Classification System -> Master Data ->CL02 -Class.
3. Material master data can be configured for material and classification maintenance.
3.1 Maintain a configurable material and assortment view of the material master data.
Transaction code: mm01
Path: SAP Menu > Logistics - > Material Management - > Material Master Data - > Material - > Create (General) - MM01 - Immediately.
Select Configurable Items in Basic View 2 of the Material Master Data tab, and assign 300 variant categories to the Classification tab, as follows:
4. Variants, correlations and parameter files.
4.1. Create a variant.
Transaction code: vk30
Path: SAP Menu > Logistics - > Production - > Master Data - > BOM - > Environment - > Variant Configuration - > Environment - > Pricing - > VK30 - Definition Code.
This variant is mainly used to define different conditional variants, such as: defining different specifications of steel, so that different specifications can be assigned different price differences**;
4.2 cu01 creates affinity and maintains syntax.
Transaction code: cu01
Path: SAP Menu > Logistics > Production - > Master Data - > BOM - > Environment - > Variant Configuration - > Dependencies - > Single Dependencies - > CU01 Create.
Affinity provides rules and logic during the configuration process.
Precondition": a certain characteristic or characteristic value is brought out only when the condition is satisfied;
Select Condition": Only when the condition is met can the property value in the property be selected;
Program": the value is calculated by the formula rule;
In the following figure, if the maintained characteristic value is greater than or equal to 30 and less than or equal to 100, the characteristic value of the purchased variant "zmm l1" is brought out, and if the characteristic value is greater than 100, the characteristic value of the purchased variant "zmm l2" is brought out. The specific definitions are as follows:
self.varpur='zmm_l1' if $self.nat8x19ssfc_1500zs8_l>=30
and $self.nat8x19ssfc_1500zs8_l<=100,self.varpur='zmm_l2' if $self.nat8x19ssfc_1500zs8_l>=100.
4.3 cu41 creates a configuration parameter file and assigns dependencies to the configuration parameter file.
Transaction code: CU41
Path: SAP Menu > Logistics > Production - > Master Data - > BOM - > Environment - > Variant Configuration - > Configuration File - >CU41 Creation.
Maintain the parameter file name, press enter, and double-click to enter the next screen
Fifth, the application of the variant of the material.
5.1 Maintenance Variant**.
Transaction code: mek1
The variant maintained in the following figure needs to meet the conditions of merchant, purchasing organization, factory, information record category, variant and validity period when creating a purchase order.
5.2 Create a purchase information record.
Transaction code: me11
5.3 Creation of a purchase order.
Transaction code: me21n
Variant Example 1:
Based on the data maintenance of the relevance of the previous parameter file, if the characteristic value is less than 30, the variant ** will not be added, as follows:
The length of the wire rope maintained in the figure below is 20m, and according to the correlation formula, the condition is not met, there is no characteristic that brings out the variant condition, and the variant ** cannot be obtained.
The above **only brings out the procurement information record**, no variant**.
Variant Example 2:
Based on the data maintenance of the correlation of the previous parameter file, if the characteristic value is greater than or equal to 30 and less than or equal to 100, zmm l1 will be brought out and the ** of the variant condition type will be updated, as follows:
Click Configure to select the configurable item, and automatically bring out the variant condition after maintenance, and synchronously bring out the ** corresponding to the variant condition, and automatically update the ** of the variant condition on the basis of the original procurement information record, as shown in the following figure:
After maintenance, the variant condition will be automatically brought out, and the corresponding condition of the variant will be brought out synchronously, and the ZMM L1 variant condition will be automatically updated on the basis of the original procurement information record;
Variant Example 3:
Based on the data maintenance of the correlation of the previous parameter file, if the characteristic value is greater than 100, ZMM L2 will be brought out and the ** of the variant condition type will be updated, as follows:
After maintenance, the variant condition will be automatically brought out, and the corresponding ** of the variant condition will be brought out synchronously, and the ** of the ZMM L2 variant condition will be automatically updated on the basis of the original procurement information record.