SAP ABAP Data Element LVS_BENUM (Requirement Number)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ LVS (Package) Application development Warehouse Management (WM)
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ LVS (Package) Application development Warehouse Management (WM)
Basic Data
Data Element | LVS_BENUM |
Short Description | Requirement Number |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LVS_BENUM | |
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 | Rqmnt.No. |
Medium | 15 | Req. Number |
Long | 20 | Requirement Number |
Heading | 10 | Req. No. |
Documentation
Definition
Goods transfers and stock quantities in the Warehouse Management system contain a reference to their origin. The requirement type refers to the origin type, for example, goods receipt for purchase order or goods issue to cost centers. The requirement number is the originating document itself, for example, the purchase order number or the cost center.
Dependencies
As a rule, you must enter the requirement type and the requirement number together.
If the field is set to the value '**********', the origin cannot be clearly defined. In the case, a transfer order for multiple deliveries, which is created for several outbound deliveries, is in question. The outbound delivery cannot be uniquely defined by this.
History
Last changed by/on | SAP | 19971006 |
SAP Release Created in |