SAP ABAP Data Element PPC_HEADID_INT (Internal backflush header key (GUID, format RAW16))
Hierarchy
☛
ECC-DIMP (Software Component) DIMP
⤷
IS-A-PPC (Application Component) Production Backflush
⤷
PPC1 (Package) Backflushing in PP
ECC-DIMP (Software Component) DIMP⤷
IS-A-PPC (Application Component) Production Backflush⤷
PPC1 (Package) Backflushing in PP
Basic Data
| Data Element | PPC_HEADID_INT |
| Short Description | Internal backflush header key (GUID, format RAW16) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SYSUUID | |
| Data Type | RAW | Uninterpreted sequence of bytes |
| Length | 16 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | HEADID | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 0 | |
| Long | 29 | Backflush header key (UID) |
| Heading | 0 |
Documentation
Definition
A backflush document is created for every backflush that is transferred to the ERP system from an external system (for example, APO). The header of this document is saved in Table PPC_HEAD. The key to specifically identify this document is a GUID (globally unique identifier) of the type PPC_HEADID_INT.
Semantically speaking, this data element corresponds to data element PPC_HEADID. However, the domains are different: in the ERP system, the recommended RAW16-Format is used for the GUID, for the interface, (BAPI) the CHAR32-Format.
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in |
