How to Add a Field to a New Condition Table in Pricing (Condition Technique)

Creating a new condition table in Pricing often requires adding custom fields to the Pricing Field Catalog. This process is essential for building complex pricing architectures, ensuring accurate pricing determination based on various criteria. 

What Is a Condition Table in Pricing?

A condition table in SAP pricing is a combination of fields used to determine a price, discount, surcharge, or any other pricing condition. It is defined in the condition technique, which includes structures like KOMP, KOMK, KOMG, and more. 

Step-by-Step Guide: Adding a Field to a New Condition Table

Step 1: Add the Field to the Field Catalog

To add a new field to the Pricing Field Catalog, follow these steps: 
  • Check Field Catalog: First, try to locate the required field from the existing field catalog.
  • Create Field If Not Found: If the field isn’t available, proceed to create it using the following steps.

Step 2: Creating Data Type in ABAP Dictionary (Transaction SE11)

  1. Open Transaction SE11 (ABAP Dictionary).
  2. Create Data Type: 
    • Define a new data type, e.g., ZZPSTYV.
    • Choose PSTYV (Sales Document Item Category) as the domain.
    • Provide a descriptive short text such as "ZZ - Sales Document Item Category".
    • Use the field labels of PSTYV.
  3. Save, Check, and Activate the new entries.

Step 3: Modify Structure KOMPAZ in ABAP Dictionary (Transaction SE11)

  1. Open Transaction SE11 and access the structure KOMPAZ in change mode.
  2. Add New Component: 
    • Component: ZZPSTYV
    • Component Type: ZZPSTYV
  3. Save, Check, and Activate the changes made to KOMPAZ.
Note: Since KOMPAZ is included in structures KOMG (Allowed Fields for Condition Structures) and KOMP (Pricing Communication Item), the new field ZZPSTYV is now recognized in both structures.

Step 4: Update the Field Catalog (Transaction SPRO)

  1. Navigate to SPRO: Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control
  2. Execute ‘Define Condition Tables’.
  3. Choose ‘Conditions: Allowed Fields’.
  4. Add New Entry: Include ZZPSTYV as a new entry.
  5. Save the configuration.
Note: You can now use the field ZZPSTYV as a key field when creating a new condition table (e.g., Axxx).

Step 5: Supply the New Field via User Exits

To ensure your new field is usable, include the following source code line in the user exit:  
    MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
    
  • In Order Processing: Add the above code in Include MV45AFZZ.
  • In Billing Document Processing: Add the code in Include RV60AFZZ.
Ensure you correctly map the field from your source structure to the target structure for accurate processing.

Step 6: Adding Header Fields (If Required)

For header-level fields, you need to modify different structures and user exits: 
  • Structure: Use KOMKAZ instead of KOMPAZ.
  • User Exit: Implement the code in USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.

Reasons and Prerequisites

The process above is required because: 
  • Certain fields, like PSTYV, are only included in the structure KOMP but not in KOMG.
  • Without adding the field to KOMG, the system cannot access it during pricing condition table creation.
  • Modifying these structures is essential for incorporating customer-specific fields or criteria.

Useful Resources

To learn more about creating new fields using the condition technique, refer to: 
  • Transaction SPRO Path: Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing
  • SAP OSS Note 21040

Frequently Asked Questions (FAQs)

1. Why isn't my custom field visible in the condition table creation screen?

Your field may not be included in the KOMG structure. Follow the above steps to include it in the KOMPAZ structure, which is then automatically recognized by KOMG. 

2. What happens if I miss activating the changes in SE11?

The system will not recognize the new field, and your configurations will be incomplete. Always ensure to Save, Check, and Activate every change. 

3. Can I use the same steps for header fields?

Yes, but instead of using KOMPAZ, you should modify KOMKAZ and apply changes in the exit USEREXIT_PRICING_PREPARE_TKOMK. 

4. Is it safe to modify SAP standard structures?

Modifying standard structures should be done carefully and ideally in a development environment first. Always follow best practices for testing and transporting changes.

5. What if I need to use other custom fields?

The same process applies. Define your custom field in SE11, include it in KOMPAZ or KOMKAZ, and update the field catalog via SPRO.

6. Where can I find detailed documentation on this process?

Refer to OSS Note 21040 and the SPRO path mentioned above for official SAP guidelines.

Adding a field to a new condition table in pricing is a straightforward process if you follow the steps outlined above. With the right configuration, you can enhance your pricing architecture for improved flexibility and efficiency.

Related SD Queries:

Get help for your SAP SD problems
SAP SD Forums - Do you have a SAP SD Question?

SAP Sales and Distribution Books
SAP SD Books - Certification, Interview Questions and Configuration

SAP Sales and Distribution Tips
SAP SD Discussion Forum and Sales/Distribution Tips

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.