Pricing Configuration Entries

In this activity, you can display the list of supported fields that represent price-relevant business attributes. If you want to include additional fields in the field catalog, you can add these fields to the field catalog.

You select these fields from the field catalog when you create a condition table. Technically, these selected fields are by default key fields for the corresponding condition table.

You can only delete custom fields from the field catalog that are not used in a condition table.

Requirements

You have created a custom field in the Custom Fields and Logic app for one of the following business contexts:

Sales: Sales Document

Sales: Sales Document Item

Sales: Billing Document

Sales: Billing Document Item

In the same app, you have enabled the usage of this custom field for the respective business scenario, which can be one of the following:

Sales Document to Pricing Communication on Header Level

Sales Document to Pricing Communication on Item Level

Billing Document to Pricing Communication on Header Level

Billing Document to Pricing Communication on Item Level

In this activity, you define condition tables in which the system persists condition records. A condition table defines the combination of fields that specifies the validity of an individual condition record. The validity is characterized by validity dates, business attributes (such as business partner, material and so on), and a condition type.

Requirements

You have checked the following:

All fields that you need for your condition table are already part of the field catalog.

The condition tables supplied with the standard system are not sufficient for your business need.

Activities

1. We recommend copying an existing condition table. In this case, in the Copy from Condition Table area, you enter a pre-delivered table number, for example 304:

The Table Number field controls if the system selects a consecutive number automatically or you can enter a new number.

For simplicity reasons, we recommend that the system selects the new number. In this case you do not have to manage the name spaces. The customer name space is from 501 to 999 and from 9AA to 9VV.

2. Choose ENTER.

3. In the Field Overview screen, you can select predefined and custom fields from the field catalog by double-clicking the fields to add them to the list of Selected Fields for the new condition table.

We recommend using the Sales Organization and Distribution Channel fields as the first two key fields for the condition table.

When you create a table, you define the sequence of the fields and whether they appear in the header or item area, for example, of the Set Material Prices app.

You can make only limited changes to existing condition tables. For example, you can change the description of the table or the format of the fast entry screens for the condition records. Therefore, you must, for example, add all header fields before you add the item fields.

Note: When the condition table has been created, you can no longer change the sequence.

4. We recommend creating the condition table with a validity period and a release status.

5. Enter a description for the condition table.

6. Create the new condition table by choosing Generate.

In this step, you define access sequences. An access sequence is a search strategy that the system uses to search for valid condition records of a certain condition type. For example, you can define for a price that the system first searches for a customer-specific price and then for a price-list price.

Activities

1. Check whether the access sequences contained in the standard system satisfy your business requirements.

2. Create a new access sequence by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key, which can have a maximum of 4 digits, and a descriptive text.

Note: If you define your own access sequences, the key must start with the letters Y or Z as SAP reserves these namespaces for new access sequences created in customer systems.

Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. The sequence defines the order of priority of the accesses.

When you adapt the copied access sequence, you have the following options:

a) You can add or delete accesses. When you add accesses, you must select a condition table. In the value help for the condition table, you can search for key fields and their combinations that meet your business requirements.

b) You can control whether an access is applicable during pricing by specifying a requirement. You can use the predelivered requirements or you can define your own requirements using the Custom Fields and Logic app.

c) You can change the Exclusive indicator: It controls whether the system stops searching for a record after the first successful access for a condition type within an access sequence.

For each access, you can change the source field from where the corresponding value is filled during price determination. To do so, select the respective row and then press Field Catalog.

In this step, you define condition types. In the system, 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.

For condition types for which you wish to maintain conditions with their own validity period, you must assign an access sequence. With this, you define which fields the system checks when searching for a valid condition record.

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.

Actions

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 this activity, you define pricing procedures.

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

In addition, you assign the pricing procedures to transactions by defining the following dependencies:

Customer

Sales document type

Sales area

In the pricing procedure, you define which condition types are to be taken into account and in which sequence. During pricing, the system automatically determines which pricing procedure is valid for a business transaction. The system then takes the condition types contained in the pricing procedure into account, one after the other.

You create new pricing procedures, for example, by copying a similar pricing procedure. Define your own pricing procedures that contain only those condition types that you actually use. Otherwise, the system makes unnecessary accesses to conditions.

Set Customer Pricing Procedures

You specify the customer pricing procedure in the customer master record for each sales area.

To determine the procedure, you allocate the customer pricing procedure and the document pricing procedure to a pricing procedure within a sales area.

If several condition records are valid for pricing in a document item, you can define rules that specify which condition records are and are not included. You use condition exclusion for this purpose.

You control condition record exclusion using exclusion groups. An exclusion group is a list of condition types which are compared with each other during pricing and result in the exclusion of an entire group or individual condition types within a group.

Thus, the result of pricing can be influenced with regard to a required criterion (for example, best price) by excluding certain condition types while others are taken into account during pricing.

Example

You can define a condition exclusion which determines the best price for the customer and excludes other less favorable results of pricing. The best price then reverses the priority of condition types which would have been predefined by the access sequence.

The procedure according to which the selection is carried out within or between the condition exclusion groups is defined in the pricing procedure. The following options are possible:

Selection of the most (least) favorable condition type within a condition exclusion group

Selection of the most (least) favorable condition record of a condition type, if more valid condition records exist (for example, selection from different condition records of the condition type PR00)

Selection of the most (least) favorable of two condition exclusion groups (in this case, all condition types of the two groups are cumulated and the totals are compared)

Exclusion procedure: If a condition type in the first group exists in the document, all condition types in the second group are set to inactive.

Actions

1. Create a condition exclusion group.

Enter an alphanumeric key with a maximum of four characters and a description. You can create your condition exclusion group from scratch or by copying from an existing entry.

Note: The key must start with letter Z. SAP has reserved this name space for you to create your own entries.

2. Assign condition types to the condition exclusion group.

A condition exclusion group can contain any number of condition types.

3. Enter the condition exclusion group in your created pricing procedure.

Note the sequence (sequential number) in which the exclusion groups should be processed.

You can use two exclusion groups for condition exclusion. In this case, you must choose the procedure 'C' which determines the best price between two exclusion groups.

In pricing, requirements are used for the condition technique. They check various criteria during the execution of pricing. You can enter them in a step of the pricing procedure or in an access of an access sequence.

Example

A requirement checks whether a condition type is taken into account in the document during pricing. The requirement can define, for example, that a condition type is only taken into account for import and export transactions.

Note

For pricing, you can implement a requirement for document, for example, as a pre-step; it is then used as a response time improvement that first checks the document fields. Or you can use the requirement for document as a stand-alone check that checks only the header attributes.

In both cases, the document item fields do not have to be checked if the result of the check is negative.

Requirements

Depending on the implementation type of the process enhancement option task, you must implement the relevant Business Add-In (BAdI) and assign a unique filter value to this implementation. When you register a routine number in a later step, you use this filter value as an enhancement identifier.

If you want to execute the optional pre-step, you must have implemented the Define Requirement in Pricing for Document custom logic for the Pricing business context. The implementation of the requirement for document is optional.

If you want to execute the requirement for item, you must have implemented the Define Requirement in Pricing for Document Item custom logic for the Pricing business context. You must use this requirement, if item fields are involved.

You can decide if you want to use either the requirement for document or the requirement for item or both.

If one of the two requirements has not been implemented, the system sets the result for the respective requirement automatically to fulfilled.

Note: If an implementation is assigned in the registration, but corresponding implementation does not exist an error will be raised in pricing.

Activities

1. Check whether you can use the requirements delivered with the standard system.

2. To register a routine number, define a routine number, for example, routine number 3000001. The system automatically enters the Requirement used in Pricing (PRICING_REQUIREMENT) process enhancement option. You use this routine number in a later step in the pricing procedure or access sequence configuration.

Note: The general number range of the routine number is from 3000000 to 3009999.

3. Assign the filter value of the BAdI implementations to this routine number as an enhancement identifier (ID) for a valid process enhancement option task. For example, for the Requirement for Document Item (PRCG_RQMT_FOR_DOCUMENT_ITEM) process enhancement option task.

Note: Use the field help for the enhancement ID.

Follow up activity:

Enter the routine number in the Requirement field in the appropriate place of the control data in pricing:

In the Set Pricing Procedures configuration step, enter the routine number to a step of your custom pricing procedure.

In the Set Access Sequences configuration step, enter the routine number in an access of your custom access sequence.

In this activity, you can define alternative ways to influence the calculation logic that is used for the condition amount during price calculation in a business document.

Routines are used in pricing and influence the determination of prices according to predefined rules. You can specify them in different places in pricing control. Routines can contain custom logic to reflect all necessary checks and calculations. You enter these routines for a condition type in a pricing procedure.

Routines that determine the condition amount contain custom logic to determine the condition amount according to criteria that are not defined in the standard system. You enter the routines that determine the condition amount in the pricing procedure in the Alt. Calc.Cndn Amnt field. A routine for the condition amount can define, for example, that the system determines the best price for the customer.

Requirements

Depending on the implementation type of the process enhancement option task, you must implement the relevant Business Add-In (BAdI) and assign a unique filter value to this implementation. When you register a routine number in a later step, you use this filter value as enhancement identifier.

You have implemented the following custom logics for the Pricing business context:

Define Alternative Calculation of Condition Amount in Document (for group conditions)

Define Alt. Calculation of Condition Amount in Document Item

Activities

To define your own routines, proceed as follows:

1. To register a routine number, define a routine number, for example, routine number 3000001. The system automatically enters the Condition Amount (CONDITION_AMOUNT) process enhancement option. You use this routine number in a later step in the pricing procedure configuration.

Note: The general number range of the routine number is from 3000000 to 3009999.

2. Assign the filter value of the BAdI implementation to this routine number as an enhancement identifier (ID) for a valid process enhancement option task. For example, for the Condition Amount in Document Item (CONDITION_ITEM_AMOUNT) process enhancement option task.

Note: Use the field help for the enhancement ID.

Follow up activities:

Enter the routine number in the appropriate place of the control data in pricing. For example, in the Set Pricing Procedures configuration step, enter the routine number to your pricing procedures in the Routine for Alternative Calculation of Condition Amount (Alt. Calc.Cndn Amnt) field.

Create a new entry for the determination of your pricing procedure in the Set Pricing Procedure Determination activity.

In this activity, you can define alternative ways to influence the calculation logic that is used for the condition base value during price calculation in a business document.

Routines are used in pricing and influence the determination of prices according to predefined rules. You can specify them in different places in pricing control. Routines can contain custom logic to reflect all necessary checks and calculations. You enter these routines for a condition type in a pricing procedure.

Routines that determine the condition base value contain custom logic to determine the condition base value according to criteria that are not defined in the standard system. You enter the routines that determine the condition base value in the pricing procedure in the Alt. Cndn Base Value field. A routine for the condition base value can define, for example, that the condition determination is based on net value or volume.

Requirements

Depending on the implementation type of the process enhancement option task, you must implement the relevant Business Add-In (BAdI) and assign a unique filter value to this implementation. When you register a routine number in a later step, you use this filter value as enhancement identifier.

You have implemented the following custom logic for the Pricing business context:

Define Alternative Calculation of Condition Base Value in Document Item

Activities

To define your own routines, proceed as follows:

1. To register a routine number, define a routine number, for example, routine number 3000001. The system automatically enters the Condition Base Value (CONDITION_BASE_VALUE) process enhancement option. You use this routine number in a later step in the pricing procedure configuration.

Note: The general number range of the routine number is from 3000000 to 3009999.

2. Assign the filter value of the BAdI implementation to this routine number as an enhancement identifier (ID) for a valid process enhancement option task. For example, for the Condition Base Value for Document Item (CNDN_BASE_VAL_FOR_DOC_ITEM) process enhancement option task.

Note: Use the field help for the enhancement ID.

Follow up activities:

Enter the routine number in the appropriate place of the control data in pricing. For example, in the Set Pricing Procedures configuration step, enter the routine number to your pricing procedures in the Routine for Alternative Calculation of Condition Base Value (Alt. Cndn Base Value) field.

Create a new entry for the determination of your pricing procedure in the Set Pricing Procedure Determination activity.

You use price list types to structure the pricing model across your sales areas: You can group customers by assigning them to the same price list type. To simplify your price maintenance, you can, for example, create a condition record with this price list type as a key field. As a result, the system considers this record for all assigned customers.

Note: The customer name space starts with 'Z'.

You use customer price groups to structure the pricing model across your sales areas: You can group customers by assigning them to the same customer price group. To simplify your price maintenance, you can, for example, create a condition record with this customer price group as a key field. As a result, the system considers this record for all assigned customers.

Note

When creating your own customer price group, please be aware of the following namespace restriction. Ensure that the key does not start with any of the following alphanumeric characters, which are reserved for system use:

Alphabet letters: S, Q, R, P, X, Y

Numbers: 0, 5, 6, 7, 8, 9

You use material price groups to structure the pricing model across your sales areas: You can group materials (or services) by assigning them to the same material price group. To simplify your price maintenance, you can, for example, create a condition record with this material price group as a key field. As a result, the system considers this record for all assigned materials.

Note

When creating your own material price group, please be aware of the following name space restriction. Ensure that the key does not start with any of the following alphanumeric characters, which are reserved for system use:

Alphabet letters: S, Q, R, P, X, Y

Numbers: 0, 5, 6, 7, 8, 9