SAP ABAP Data Element KUNNR_KH (Customer)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷
VSH (Package) B2R: BAPI Structures
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VSH (Package) B2R: BAPI Structures
Basic Data
| Data Element | KUNNR_KH |
| Short Description | Customer |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KUNNR | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | KNA1 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | VHI | |
| Default Component name | CUSTOMER | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Customer |
| Medium | 15 | Customer |
| Long | 20 | Customer |
| Heading | 10 | Customer |
Documentation
Definition
Number that uniquely identifies the node in a customer hierarchy. A node can be defined for
- an existing customer master record
- an organizational unit in the customer's structure
- In this case, you need to create a master record for the organizational unit.
Note
When you create a master record for a node in a customer hierarchy, you are creating a kind of scaled down customer master record. If a node represents a particular organizational unit in the customer's own structure (for example, a regional sales office), you can specify basic information, such as address and contact person data as well as indicators to say whether the node is relevant for pricing and rebate processing.
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
