SAP ABAP Data Element WBEDNR_KL (Requirement tracking number)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WPOS (Package) IS-R: POS interface
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WPOS (Package) IS-R: POS interface
Basic Data
| Data Element | WBEDNR_KL |
| Short Description | Requirement tracking number |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | TrackingNo |
| Medium | 15 | Tracking Number |
| Long | 20 | Req. Tracking Number |
| Heading | 10 | TrackingNo |
Documentation
Definition
Document number used to monitor procurement of a requirement. This number is assigned in the partner system and can refer to a requisition note not created in the system.
Use
The requirement number is transferred from the purchase requisition to the purchasing documents (e.g. RFQ or purchase order) that are created with reference to the purchase requisition. As a result, you can use the requisition note number to group together the purchasing documents received for a particular requirement.
History
| Last changed by/on | SAP | 19980505 |
| SAP Release Created in |
