SAP ABAP Data Element UG_MD_TR_INCLUDE_SUB_OBJ (Simultaneously Transport Reusable Lower-Level Objects)
Hierarchy
FINBASIS (Software Component) Fin. Basis
   FIN-FB (Application Component) Financials Basis
     UGWB (Package) FI General: Workbench
Basic Data
Data Element UG_MD_TR_INCLUDE_SUB_OBJ
Short Description Simultaneously Transport Reusable Lower-Level Objects  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type UG_FLG    
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 SubObj. 
Medium 15 Subobjects 
Long 29 Reusable Lower-Level Objects 
Heading SubObj. 
Documentation

Definition

Use

You set this indicator to also include the reusable values in the transport request for optional reusable parts of Customizing.

For some Customizing objects you can optionally specify a key for reuse.

  • If you do not specify a key then the object can only be used directly in the context of Customizing from which you created it; it is not reusable.
  • If you specify a key then the object can also be used in other places; it is reusable

The system behaves as follows when transporting a combined Customizing object:

  • Customizing elements that are inseparably part of the selected value for the transport, are automatically simultaneously transported.
  • Customizing elements that can be maintained independently, must also be transported independently.

For optional reusable objects this means that non-reusable Customizing elements are simultaneously transported as an integrated part of the higher-level Customizing. However Customizing elements as independent objects are not.

You can influence this behavior with this indicator.

Example

You transport data entry layout A in Consolidation (SEM-BCS). This data entry layout contains two structures S1 and S2. S1 is only defined for this data entry layout and has no key for reuse, S2 is reusable.

  • If you do not set this indicator, then only S1 will be transported during the transport of data entry layout A, but not S2.
  • If you do set this indicator, then both structures will be automatically transported during the transport of data entry layout A.

History
Last changed by/on SAP  20041006 
SAP Release Created in 300