Copy Control in MM (Conditions, Fields and Texts):
Copy Control in MM (Conditions, Fields and Texts):
I would like to share some useful copy controls in MM.
1. Copy Control for Pricing Conditions:
The copy control functionality in pricing allows you to copy the data in existing condition records to number of new condition records in one step. The functionality can be used to
- Condition records of same condition type – within the same condition table and cross table.
- Condition record of one condition type to another condition type -within the same condition table and cross table.
If you want to copy condition record from one condition type to another, both the condition type should have the same properties like calculation rule, scale type, condition class, plus / minus indicator etc.
If you want to copy from one condition table to another, both these table should have the same number of fields in which one field may differ.
The copying rules may be defined in customizing in the path: OLME – Conditions – Define Price Determination Schema – Copy Control for Conditions.
For example, you have a condition type FRA1 with condition records say, purchase org / vendor combination. Now, based on business requirement, a new similar condition type, say ZFR1 has added to the pricing procedure. Suppose you want to create condition record for the new condition type similar to the original condition record.
Step 1: Define copying rules for condition types: Go to the path: OLME – Conditions – Define Price Determination Schema – Copy Control for Conditions – Define copying rules for condition types.
Here, add new entries: Maintain source and target condition types and save.
Step 2: Define copying rules for conditions: Go to the path: OLME – Conditions – Define Price Determination Schema – Copy Control for Conditions – Define copying rules for conditions.
Here, maintain the source and target condition tables. For access sequence LF01 (for the source condition type FRA1), condition table 44 is maintained. Maintain it in the copying rule.
You may use different source and target tables, provided the points mentioned initially (both these table should have the same number of fields in which one field may differ.) are satisfied.
The “Copy date” flag will copy the validity to target object.
The “Default Rule” flag will make the condition copying rule as default rule. Other rules can be selected from “Select Rule” option while copying.
The standard programs for copying rules ( RV15CC**) are listed below:
|RV15CC01||Copying : Material Pricing Groups|
|RV15CC02||Copying: Material to material pricing group|
|RV15CC03||Copying : Material to Material|
|RV15CC04||Copying : Material Pricing Group to Material|
|RV15CC05||Copying : Pricing Groups|
|RV15CC06||Copying : Customer to Price group|
|RV15CC07||Copying : Customer to Customer|
|RV15CC08||Copying : Price Group to Customer|
|RV15CC09||Copying: Currency to currency|
|RV15CC10||Copy service agent to service agent|
|RV15CC20||Copy: vendor to vendor|
|RV15CC21||Copying : Material to Material|
|RV15CC22||Copying : Material Group to Material Group|
|RV15CC23||Copy: plant to plant|
In F4 option, if the system is not showing these programs, you may insert RV15CC* in the program field and press F4.
You may define your own custom program also, by copying the standard program, with your own copying logic.
Step 3: Go to MEK2 or MEK3 transaction and check the condition record for source condition type:
Suppose you want to copy the condition record of vendor 300000 from FRA1 to ZFR1 condition for multiple vendors:
Select the condition type and click on copy button as shown below:
Note: If you want to copy with other copy rules than default rule, you may click in “Select Rule button”
Enter the target vendor, target condition type etc as shown below:
System will display the list of characteristics which will can be copied. Select the required conditions and click on continue.
It will automatically redirect you to MEK2 screen with new condition type.
Go to details:
Here, remove the “propose field content” indicator, which will prevent copying the content from the reference material:
Similarly, if you want a field to be copied always from the reference material, maintain the “propose field content” for the field. For example, division (MARA – SPART)
Save the settings and test the scenario:
Material Master Creation by using reference material:
Here, division is copied from the reference material, while the material description is not copied.
Note: The same settings logic can be used for almost all fields in material master.
3. Copy Control for text from vendor master to PO.
Suppose there is a business requirement that a new text is to be maintained in vendor master and the same is to be copied from vendor master to PO.
To create a new text type for vendor master, follow the path: OLME – Vendor Master – Define Text Types for Central Texts / Define Text Types for Purchasing Organization Texts. Click on new entries and create new text (Not mandatory. You can link the existing text also to PO)
In order to create a new text for PO, follow the path : OLME – Purchase Order – Texts for Purchase Orders – Define Text Types for Header Texts.
Click on new entries and create new text. (Not mandatory. You can link the vendor text to any of the existing PO text too)
Now, in order to link the vendor master text to PO text, follow the path: OLME – Purchase Order – Texts for Purchase Orders -Define Copying Rules for Header Texts.
Select the required text and go to “text linkages”
Click on “new entries” to create new text linkage.
One information message will be displayed as shown below:
The information message says that the source object and source text can be selected from F4 option, even though its is greyed out.
Place the cursor on the first line of “source object” and press F4.
Repeat the same for the source text field:
Maintain the fixed indicator for texts accordingly. The fixed indicator determines whether, when and how the texts are to be copied. The indicator has 3 options:
- ” ” (Blank) : In this case, the text will be always copied from the source object and is changeable. The changed object doesnt have any effect on source object.
- ” * ” (asterisk) : In this case, the text can be adopted manually.
- “N” : Here, the text is not fixed and is only displayed in the document and cant be changed.
Maintain the indicator and save.
Now, maintain the text in the source object and create a new PO. In the PO, the text will be copied from the corresponding source text.
Note: The same configuration logic can be applied in other similar cases also.
Thanks for reading the document and expecting your valuable feedback!.
Thanks & Regards,