SAP ABAP Data Element LIFNR_LH (Vendor number of vendor hierarchy)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
WLIF (Package) IS-R: Vendor master
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
WLIF (Package) IS-R: Vendor master
Basic Data
| Data Element | LIFNR_LH |
| Short Description | Vendor number of vendor hierarchy |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | LIFNR | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | LFA1 |
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 | Hierarchy |
| Medium | 15 | Hierarchy |
| Long | 21 | Vendor hierarchy |
| Heading | 10 | Hierarchy |
Documentation
Definition
Number which uniquely identifies a node in the vendor hierarchy. A node can be defined
- for an existing vendor master record
- for an organizational unit in the vendor structure
- In this case, you must create a master record for the organizational unit.
Note
If you create a master record for a node in a vendor hierarchy, create a short version of a vendor master record. If the node represents a particular organizational unit in the vendor structure, you can enter basic data such as the address, and set an indicator which determines whether the node is relevant for pricing.
History
| Last changed by/on | SAP | 19971006 |
| SAP Release Created in |
