Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NPAS (Package) Application development patient accounting system
Basic Data
| Data Element | ISH_SDUMK |
| Short Description | IS-H: Access Collection Cost Center for Sender Determination |
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 | SendColl. |
| Medium | 14 | SendColl. CC |
| Long | 20 | Sender Coll. CCtr |
| Heading | 0 |
Documentation
Definition
Using this setting, you can control whether the system is to use a collective cost center when determining the sender for internal activity allocation.
The collective cost center always takes effect if the actual cost center based on the assignment rules defined in the system cannot be determined due to the specifications of the organizational unit (OU) performing a service, for example, because the specification of the performing OU is missing from the service, or because the OU - cost center assignment table is incomplete.
Note
You can make the specification of the collective cost center in this OU - cost center assignment table (by specifying a * in the fields OE_1 and OE_2).
Recommendation
It is recommended to avoid using collective cost centers in production systems.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
