SAP ABAP Data Element TCUNCGR (Trading Contract: Incompleteness Group)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
LO (Application Component) Logistics - General
⤷
WB2B_DDIC (Package) Trading Contract: DDIC Objects Retained in AL0
SAP_APPL (Software Component) Logistics and Accounting⤷
LO (Application Component) Logistics - General⤷
WB2B_DDIC (Package) Trading Contract: DDIC Objects Retained in AL0
Basic Data
| Data Element | TCUNCGR |
| Short Description | Trading Contract: Incompleteness Group |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR2 | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | IncomplGrp |
| Medium | 15 | Incompleten.Grp |
| Long | 20 | Incompleteness Group |
| Heading | 1 | I |
Documentation
Definition
Group of fields in trading contracts in which it is important or obligatory that data be entered.
Example
Incompleteness groups can be defined for different types of trading contracts.
In two-sided trading contracts, purchasing and sales prices must exist. This means that the sales price and the purchasing price must be included in the incompleteness group.
In a one-sided purchasing contract, only price data is required on the purchasing side. It is therefore important that the purchasing price be included in the incompleteness group.
History
| Last changed by/on | SAP | 20020107 |
| SAP Release Created in |
