SAP ABAP Data Element COPA_TR_SPLIT (Split Objects into Workbench and Customizing Requests)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE0C (Package) Customizing for Profitability Analysis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE0C (Package) Customizing for Profitability Analysis
Basic Data
Data Element | COPA_TR_SPLIT |
Short Description | Split Objects into Workbench and Customizing Requests |
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 | Splitting |
Medium | 15 | Splitting |
Long | 50 | Split into Workbench + Customizing |
Heading | 70 | Split into Workbench and Customizing requests |
Documentation
Definition
If you set this indicator, the transport objects are transferred according to their category into the different transport requests.
Transport objects fall into the following categories:
- CUST: client-specific Customizing (Customizing request)
- SYST: cross-client settings (Workbench request)
- Master data (tables from delivery class "A")
- Data dictionary objects
- Cross-client Customizing
If you do not select this indicator, all objects are written to a Workbench request (SYST).
Note:
- Select this indicator if you want to distribute Customizing automatically into different clients using the TMS (Transport Management System) functions. This occurs via Customizing requests with transport target groups.
Workbench requests then contain cross-client settings only and have only one target client.
Important: Ensure that the correct transport sequence is applied. First release SYST (Workbench requests) and then CUST (Customizing requests).
- You do not need to select this indicator if you want to use transport requests to supply just one target client.
History
Last changed by/on | SAP | 20000201 |
SAP Release Created in | 46C |