SAP ABAP Data Element KUNAG_CUST (Sold-To Party for Customizing Data)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
SD-BIL-IV-SBI (Application Component) Self-Billing Proced.
⤷
VASB (Package) Application Development R/3 Sales / Self-Billing Process
⤷
⤷
Basic Data
| Data Element | KUNAG_CUST |
| Short Description | Sold-To Party for Customizing Data |
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 | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | SP Cust. |
| Medium | 15 | SP Cust. |
| Long | 20 | SP Customizing |
| Heading | 4 | SPCu |
Documentation
Definition
Sold-to party for which the Customizing settings (OVD7) are used.
Use
On receiving a credit memo record the sold-to party is determined in table T661W. If the search is succesful, the (first) sold-to party found is used. Among other things, the inbound parameters of the sold-to party (cf. transaction OVD7) determined above are used. The field provides you with the information on the sold-to party whose OVD7 data is used.
Procedure
Examples
Dependencies
Using delivery determination, which takes place after the sold-to party search (T661W), another sold-to party can be determined.
If this is the case, the sold-to party's Customizing settings that are used are also changed retroactively.
History
| Last changed by/on | SAP | 20030411 |
| SAP Release Created in |