SAP ABAP Data Element CO_GSBTR (Overall commitment date)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-CIC (Application Component) Interaction Center WinClient
⤷
CO (Package) R/3 Application development: PP Production orders
BBPCRM (Software Component) BBPCRM⤷
CRM-CIC (Application Component) Interaction Center WinClient⤷
CO (Package) R/3 Application development: PP Production orders
Basic Data
| Data Element | CO_GSBTR |
| Short Description | Overall commitment date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| 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 | Ov.commit. |
| Medium | 15 | Ov.commitment |
| Long | 20 | Overall commitment |
| Heading | 10 | Committed |
Documentation
Definition
The overall commitment date is determined by the material availability check (only if ATP logic is used for the check).
It specifies the earliest date by which the complete order is to be produced (depending on the availability situation at the time of the last availability check).
The overall commitment date is calculated by calculating for all material components that were checked how many days they will be available after their requirements date. The overall commitment date is calculated from these delays and from the basic finish date of the order.
History
| Last changed by/on | SAP | 19981210 |
| SAP Release Created in |
