Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KE1C (Package) Customizing for Profit Center Accounting
Basic Data
| Data Element | PCAT03 |
| Short Description | Transport flag: Profit center groups |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | 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 | PrCtr grps |
| Medium | 15 | PrCtr groups |
| Long | 21 | Profit center groups |
| Heading | 10 | PrCtr grps |
Documentation
Definition
Indicator for choosing the customizing settings during transport.
Supplementary Documentation - PCAT03 0001
Use
If you select this indicator, the following customizing settings are activated or deactivated in the correction:
- Profit center groups (sets)
Procedure
- To include the settings in the correction request number specified, choose Include in Correction.
- To remove the settings from the correction request, choose Delete from Correction.
In both cases the system may display a screen on which you can restrict your selection of entries to be transported (by controlling area or chart of accounts, for example).
Dependencies
Profit center groups (sets) let you summarize profit center master data. When you transport profit center groups, make sure that all the profit centers in the groups also exist in the target system.
Technical information
The system enters the following in the transport request:
"R3OB SETS GR/0H/GLPCT/<prctr-gruppe>"
The standard hierarchy is transported separately. The groups are each summarized at the highest node, and the entire hierarchy is transported. This requires fewer entries in the transport request.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
