Hierarchy
DMIS (Software Component) DMIS 2011_1⤷
CA-EUR (Application Component) European Monetary Union: Euro⤷
BTP_DL (Package) BTP Application Data Layer Basis
Basic Data
| Data Element | BTP_DL_OBJ_HIDDEN |
| Short Description | BTP Object Flag 'Hidden' |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BTP_DL_FLAG | |
| 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 | Hidden |
| Medium | 15 | Hidden |
| Long | 20 | Hidden |
| Heading | 20 | Hidden |
Documentation
Definition
The flag indicates that an object is hidden in SAP LT.
Use
Objects (especially portfolio objects) which are already shipped as content to the customer may be used by the customer in projects, project templates, and so forth. Hence, these objects must not be deleted any more because this deletion would lead to an inconsistency on customer side.
To avoid such an inconsistency an object can be flagged as 'hidden'. This makes the object to disappear on several user interface screens but keeps the data consistent because the object is still available in the system.
Example
A transformation requirement has already been shipped to customers and a customer has created a project using a project template with this transformation requirement. If the next software release import would delete the transformation requirement because the functionality has been replace by a different requirement then the already started customer project would become inconsistent.
If the transformation requirement has been flagged as 'hidden' then the requirement is still shipped but does not appear any more in the SAP LT portfolio. Hence, the transformation requirement cannot be used in new projects but existing projects and project templates keep consistent.
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in | 2006_1_700 |
