Hierarchy
BBPCRM (Software Component) BBPCRM⤷
AP-PRC-PR (Application Component) Pricing⤷
VKON (Package) Application development R/3 conditions
Basic Data
| Data Element | KOTABNR |
| Short Description | Condition table |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KOTABNR | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | KON | |
| Default Component name | TABLE_NO | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Table |
| Medium | 15 | Table |
| Long | 20 | Table |
| Heading | 3 | Tab |
Documentation
Definition
A combination of fields that defines the key of a condition record.
Use
For each condition type in a pricing procedure, you define an access sequence. The access sequence tells the system where to look for relevant condition records for a particular condition type (a rebate for a specific customer, for example). Each access in the access sequence refers to a condition table. The fields defined in the table (the key) help the system to locate valid condition records.
Procedure
When you create a condition table, you specify one or more target fields as the table key. You must also tell the system where to find the value for each target field. You do this by specifying source fields. The source fields are usually the same as the target fields, but they can differ. For example, if the target field "Customer" is part of the key, you can specify that the system uses "Ship-to party" as the source field and takes the value from there.
History
| Last changed by/on | SAP | 20140802 |
| SAP Release Created in |
