Data Determination using Routines 
Data Determination using Routines
Use
The previous unit describes data determination for fields within accesses using communication structure KOMPAZD. You can not use communication structure KOMPAZD to determine data for fields that are not used in accesses, such as the scale quantity or the pricing date. In these cases, you must carry out the data transfer using routines.
First of all the data is determined using a condition type such as PBUD, for example. This includes the access sequence PBUD assigned to the condition type PBUD and the pricing date field, which is indicated as a data determination field.
Afterwards a routine can be assigned to the discount, which uses the data for pricing.
Prerequisite: Indicate a field as a data determination field
Data determination in the access for pricing takes place at field level. A field is selected for this. It is used for data determination, not pricing. This is carried out as follows:
When maintaining a condition table, you can choose a field from the key in the Technical Settings field. It is then designated as a data field and is automatically indicated with C in the access. This is only possible when creating. In exceptional cases you can use it when changing: delete – add new one
In the pricing procedure, condition type PBUD is used for data determination. You can then assign as many discounts/surcharges for use in pricing to the following routines:
Conditions in the pricing procedure:
Condition type |
Requirement in the the pricing procedure |
PBUD (Data determination) |
|
KXXX (Use of data) |
202 (used to apply the pricing date determined using condition type PBUD for pricing) |
The data used in the following example are provided in the standard system as example data.
Pricing Date Example
You want to grant prices from a previous year to customers in a certain customer group. These prices are however no longer valid. You enter pricing date 12.31 from the previous year for pricing.
To do this, data must be determined and applied to pricing again. In this example, condition type PBUD is used for determining the data. Pricing then uses this data to determine a suitable discount. In the following example the condition type KXXX is specified. Both conditions must be copied to the pricing procedure.
Data Determination
The access sequence PBUD contains the field KDATU.
The field KDATU is indicated as the data determination field.
Access sequence PBUD with the following access:
Field |
Name |
Processing type in access (field AType) |
KDATU |
Pricing date |
C (data field for data determination) |
This access can be used to read a customer specific condition record, which determines a pricing date as the date from the previous year.
Using the Data for Pricing
You can now assign requirement 202 to a discount in the pricing procedure. This ensures that the pricing date from the previously determined field KDATU is used for pricing.