Define price dependencies (condition tables)

In this IMG activity, you define price dependencies. You can make prices, surcharges, and discounts dependent on almost all the fields in a document. You define these dependencies using the condition tables . In a condition table, you define the combination of fields for which you can create condition records.

Recommendation

Do not change the condition tables in the standard system.

Activities

1. Check to what extent you can use the condition tables contained in the standard system.
To do this, you can display the condition tables.
2. Before you create a new condition table, you should check whether the fields listed in the field catalog meet your requirements. If you require a field in pricing which is not intended for this usage in the standard system, you must enter it in the field catalog. You can only enter fields from tables KOMG, KOMK or KOMP.
3. Create new condition tables. Copy a similar condition table and proceed as follows:
Bear in mind that you can only choose names between 501 and 999. If you do not make a specification, the system automatically assigns a sequential number.

Note

If, for example, you want to make pricing dependent on the ship-to party, you can only select the customer field in the condition table. You cannot specify the ship-to party in the condition tables since only customer master records exist. It is not until you create an order document that you have the specific function 'ship-to party'. When you subsequently define the access, you can assign the ship-to party source field to the customer field.

1. Specify the condition tables in the access sequences.
This way, you establish the link between condition type, access sequence and condition record.

Note

For information on entering fields in the tables KOMK, KOMG, and KOMP, see the System modification section.