Ansicht
Dokumentation

SIMG_EXG_0037 - Maintain Sales Price Conditions

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Set condition types for pricing in sales.

In this step, you define condition types. In a business document, price elements are represented by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or freight, and are stored in the system in condition records. You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.

If you use a condition type as price element, you specify an access sequence in every condition type. In this way you define which fields the system checks when searching for a valid condition record.

If you use a condition type as an inclusion point, you must set the Inclusion Pointcheckbox. Once you have defined a formula for subprocedure determination, you can use its formula ID in the inclusion point. In this way you prepare inclusion points to set up main procedures and subprocedures for a later subprocedure determination:

• The pricing procedure groups all condition types together that the system is to take into account automatically during pricing for a business transaction.

Remember that in a business document, you can only specify manually those condition types that are contained in the pricing procedure.

• You can change the outcome of pricing in the business document manually.

• If you define your own condition types, the key should start with the letter Z as SAP reserves this namespace for this purpose in the system.

• Do not change the condition types that are contained in the system.

• If you define your own condition types, the key must start with the letter Z as SAP reserves this namespace for this purpose in the system.

You can change the value of certain fields in condition types that are delivered by SAP. If you want to change the values of these fields, you should carefully consider that these changes could affect existing documents and, therefore, change the pricing result.

1. Check to what extent you can use the condition types contained in the standard system.
2. Create new condition types by copying a similar condition type and changing it according to your requirements. One reason for creating a new condition type is that you may require a calculation rule for a discount which is not available in the standard system.
3. Specify a 4-character, alphanumeric key that starts with a Z and a textual description.
4. Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
5. Maintain the detail screen of the condition type. You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.

In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.

Checking settings

You can use the SDCHECKT685A report to check the settings for the condition types. This is not a complete check but it does, for example, check the scale type setting for group conditions. For more information, read the report documentation.

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3799 Date: 20240524 Time: 001246     sap01-206 ( 83 ms )