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_PIFD_VAR_FINAL |
| Short Description | BTP PIFD Final Flag |
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 | Final |
| Medium | 15 | Final |
| Long | 20 | Final |
| Heading | 20 | Final |
Documentation
Definition
The final flag states that a variant which is used for an interface will overwrite all variant definitions in the object hierarchy below.
Use
Set the final flag if you want to apply the variant for all subsequent interfaces in the object hierarchy below.
Dependencies
Example
You specifiy a variant for an interface on project level and set the final flag. Independently, if there will be defined further variants for a single step in the project execution plan or even for a single activity in the process structure of an execution package, the variant on project level will be applied.
If the final flag is not set then the variant on project level will be used as default, i.e. also for a step in the project execution plan. But if there is specified another variant on execution plan step this variant will overwrite the variant on project level and will be used instead.
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in | 2010_1_700 |
