Hierarchy
⤷
⤷
Basic Data
| Data Element | CACS_TR_FLAG |
| Short Description | Transport Indicator for Versioned Tables |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Transp.ID |
| Medium | 15 | Transport |
| Long | 20 | Transport Indicator |
| Heading | 2 | TI |
Documentation
Definition
Used in tables with ICM versioning to differentiate between normal entries and transport entries. This field is generelly initial, but transport entries are set to X.
Use
If a table uses ICM version management and you want to be able to transport the table entries, the table must have a key field with data element CACS_TR_FLAG and field name TR_FLAG. (Tables with keys containing the commission application APPL currently do not need a transport indicator.)
Applications must never operate in the transport space. Consequently, if database tables with the transport indicator are read the WHERE condition TR_FLAG = ' ' must always be specified. Transport entries must only be generated and processed with the functions of the transport interface of ICM version management.
History
| Last changed by/on | SAP | 20050219 |
| SAP Release Created in | 600 |