Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SD-BF-PR (Application Component) Pricing and Conditions⤷
VF_PRC_CORE (Package) Central Pricing Routines
Basic Data
| Data Element | KNBTXT |
| Short Description | Additional Text for the Conditions |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TEXT20 | |
| Data Type | CHAR | Character String |
| Length | 20 | |
| Decimal Places | 0 | |
| Output Length | 20 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Addnl Text |
| Medium | 15 | Accomp. Text |
| Long | 20 | Additional Text Cond |
| Heading | 20 | Accomp. Text |
Documentation
Definition
The condition additional text is controlled together with the relevant document condition. In the corresponding Customizing it can either be entered or changed manually in the document, or determined using condition maintenance.
Use
The condition additional text must be stored in a separate table (not in the standard system). Also the structure KOMV and the table KONP must be extended with an additional field, with description KNBTXT. Then the functionality in condition maintenance, Customizing of the condition type, and on the condition screen of the document is automatically available. (Initially only for the purchasing application).
Dependencies
You can implement the SD_KONV_SELECT BAdI to read in additional texts from the separate table. For the posting previous to this you must use a suitable BAdI from the application. (In purchasing this is ME_PURCHDOC_POSTED.)
Example
History
| Last changed by/on | SAP | 20030605 |
| SAP Release Created in | 470 |
