Maintaining pricing data in SAP S/4HANA can be time-consuming, especially when new condition records closely resemble ones that already exist.
Rather than entering the same values again from scratch, you can use the copy function to transfer data from an existing condition record into a new one. In this post, we'll walk through the prerequisites for copying condition records, including the copy control settings in Customizing, and then look at a practical example using condition type K004.
Prerequisites
The copy function is only available if, within the configuration of pricing, the appropriate copy controls for conditions are set up. The settings can be found using menu path IMG > Sales and Distribution > Basic Functions > Pricing > Copy Control for Conditions.
An existing condition record has a condition type and a condition table assigned, which are referred to in the definition of the copying rules as the source condition type and source (condition) table. On the Copying Rule for Condition Types screen, the possible assignment of target condition types to source condition types is performed (see figure below). Here, for example, two possible Target condit.types, K004 and K029, are assigned to the Source condit.type K004.
The assignment of target condition tables to source condition tables is done in a second step. The following principles apply:
- If the condition tables of the source and target condition records differ, then the following are true:
- Only one field may be different in the condition tables.
- The condition tables must have the same number of fields.
- If the condition types of the source and target condition records are different, the condition types must have the same calculation type, scale basis, condition class, and plus/minus sign rule.
Several target condition tables can be assigned to one source condition table; in this case, one of them is automatically marked as the proposed default rule. For example, the figure below shows that condition tables 004 and 029 are assigned to condition table 004.
There’s a detailed view for each entry on the overview screen.
Here, you assign the source and target fields. You also determine whether the expiration date of the source condition record is proposed in the target condition records. In addition, a selection report is assigned, which controls the selection screen for the selection criteria, which appears when you perform the copy function.
You can define your own selection report to use, for example, individual selection parameters. For this purpose, standard report RV15CC01 is delivered as a template. This report also includes information for creating a new report in the customer namespace.
Application Example
Due to the previously presented Customizing settings, the following situation arises when copying condition type K004 (Material Discount): Rule 1 is assigned as the proposed default rule. However, this can be changed by clicking the Select Rule button.
If you use rule 1 and click the Copy button, the associated selection screen is displayed. It will determine the number of the copied condition records.
Due to the entry in the selection screen, all materials that have the text CROSSFUN included in the short text are proposed in the results list (see figure below). For the selected entries, the corresponding condition records are then created with the values of the template condition record(s).
In principle, copying is a very useful feature. However, if it’s frequently used to copy prices of customer A to customers B and C, for example, that could be an indication that you might need to adapt your configuration. For example, you can define a new price condition type on the customer group level, which is then applicable for customers A, B, and C with the commonly assigned customer group XY. That is, you then have a condition record that is valid for many customers, instead of many condition records for individual customers.
Conclusion
The copy function is a practical way to reduce maintenance effort when creating condition records that share values with existing ones, as long as the required copy controls for condition types and condition tables are configured in Customizing. Keep in mind that heavy reliance on copying, such as repeatedly duplicating one customer's prices for others, may signal that your pricing configuration should be adjusted instead, for example by defining a condition type at the customer group level so a single condition record can serve many customers at once.
Learn SAP S/4HANA Sales with Rheinwerk Courses!
Ready to level up your SAP S/4HANA Sales skills? Explore our SD-focused online courses, covering the full order-to-cash process from organizational structure, master data, ATP, shipping, and billing to an in-depth deep dive into sales pricing, including the condition technique, pricing procedure configuration, advanced pricing controls, and troubleshooting. Each one is instructor-led (live and on-demand), includes recordings and slide decks, and is designed to give you practical take-away skills you can apply right away in your SAP landscape. Click on the banner below to get started!
Editor’s note: This post has been adapted from a section of the book Pricing and the Condition Technique with SAP S/4HANA by Ursula Becker, Jan Fischer, Werner Herhuth, Manfred Hirn, Markus Urbanek, and Moritz Wilhelm. Ursula has been the development architect responsible for the pricing functionality in SAP solutions since 2009. Jan, product manager for pricing in SAP S/4HANA, joined SAP in 2004. Werner is a certified consultant in the area of order fulfillment in SAP ERP and the author of several SAP courses. Manfred was responsible for the development of the condition technique, as well as the billing and pricing functionalities that he helped program, in SAP R/3. Markus has been the chief development architect and chief product owner for condition contract management and settlement management since 2004. Moritz has been working on the pricing functionality of SAP S/4HANA as a developer and architect since 2018.
Comments