Hierarchy
BBPCRM (Software Component) BBPCRM⤷
AP-PRC-PR (Application Component) Pricing⤷
VKON (Package) Application development R/3 conditions
Basic Data
| Data Element | KOTABNR_SO |
| Short Description | Source condition table |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KOTABNR | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | T681 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | KON | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | SourceTabl |
| Medium | 15 | Source table |
| Long | 20 | Source table |
| Heading | 4 | SoTa |
Documentation
Definition
A combination of particular fields which form the key of a condition record.
Use
In a pricing procedure you determine an access sequence for every condition type. The access sequence determines, where exactly the system should search for the condition records relevant for a particular condition type (for example, a rebate for a customer).
Each access in the access sequence refers to a condition table. The system can use the fields defined in the table (the key) to find the valid condition records.
Procedure
During the creation of a condition table you define one or more target fields as table key.
In addition, you must enter the information, from where the system is to take the value for the target field. You do this by entering a source field.
Source field and target field are usually identical, they do not have to be, however. If the target field "customer" is part of the key, you can define, that the system uses the source field "ship-to party" and copies the corresponding value.
History
| Last changed by/on | SAP | 19940827 |
| SAP Release Created in |
