Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | GLSETS |
| Short Description | Transport: Transport sets |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Sets |
| Medium | 15 | Transport sets |
| Long | 40 | Transport sets |
| Heading | 4 | Sets |
Documentation
Definition
You are transporting Special Purpose Ledger. The settings you defined in system configuration are written to a transport request. These settings might contain sets (for example, in the rollup, in the ledger selection, in planning parameters, in cycles). If you want to transport these sets as well, you must choose this option. However, sets will only be transported, if the configuration settings on which the sets are based are also transported.
Example: If you have defined sets in the ledger selection, these sets will only be transported if you also check off the option 'Ledger selection conditions'.
Note: Sets are transported in their entirety, that is, all subordinate objects in the set (variables, other sets contained in the set to be transported) will also be transported.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
