Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KKR (Package) CO Hierarchy Summarization
Basic Data
Data Element | KKR_POSNO |
Short Description | Sequence for Summarization Object Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC2 | |
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Sequence |
Medium | 15 | Sequence |
Long | 22 | Sequence SummObjType |
Heading | 4 | Prio |
Documentation
Definition
Priority by which the values of fields are used for summarization if an account assignment object is assigned to multiple summarization object types.
Use
You can summarize multiple account assignment objects (such as orders or WBS elements) simultaneously.
It may happen that an account assignment object (such as an internal order or production order) is assigned to a project hierarchy. If the fields within the project hierarchy are passed downwards, you specify here which value takes priority.
Example
Suppose that Mr. Miller is responsible for an order.
This order is assigned to a WBS element for which Mr. Schultz is responsible. Mr. Schultz should also be responsible for the assigned objects.
In your summarization hierarchies, you use the responsible employees as a summarization characteristic.
To prevent an order from being evaluated in two different summarizations, assign Priority 1 to the summarization object type "WBS element" and Priority 2 to the summarization object type "Order".
History
Last changed by/on | SAP | 19980428 |
SAP Release Created in |