Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KBAS (Package) Overhead Cost Controlling
Basic Data
| Data Element | HNAME |
| Short Description | Group name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | HNAME | |
| Data Type | CHAR | Character String |
| Length | 12 | |
| Decimal Places | 0 | |
| Output Length | 12 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | HNA | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Group |
| Medium | 15 | Group name |
| Long | 20 | Group name |
| Heading | 24 | Group name |
Documentation
Definition
Name under which objects are combined into groups with the master data maintenance transaction.
This designation is simultaneously the name of a node.
You can combine the following into groups:
- Cost and revenue elements
- Cost centers
- Activity types
- Statistical key figures
- Orders
- Profit centers
- Business processes
- Cost objects
The group name must be unique. You must use different names, for example, for order, cost center, and business process groups.
Example
You create an order group and a cost center group. The names must start with the following prefixes:
- ORD for the order group
- COST for the cost center group
Use
Groups are meant to ease processing. You can work on multiple objects simultaneously with the CO transactions.
Supplementary Documentation - HNAME 0001
Use
You must enter individual cost centers or cost center ranges for the areas on the bottom level of each hierarchy. This means that the bottom hierarchy levels are areas directly above individual single cost centers.
Supplementary Documentation - HNAME 0002
Use
The reference_node is the node in the hierarchy to which the functions lower level, same level, and higher level refer when you insert a new node.
Dependencies
Because the hierarchy has one top node only, note the following exceptions:
- If the reference node is the top node in the hierarchy, you cannot insert a node on the same level.
- If the reference node is one level lower than the top node, you cannot insert a node on a higher level.
Supplementary Documentation - HNAME 0003
Use
One of two things occurs when you enter a new name:
- The entry does not exist.
The entry is added as a new node.
- The entry is defined in the system as a hierarchy or a single node.
The complete sub-hierarchy is added in the relevant place.
Procedure
Examples
Dependencies
Supplementary Documentation - HNAME 0100
Use
Cost center groups are used to
- reflect the structure of your company in the SAP System
- define alternative hierarchy structures
- define special structures for reporting purposes
- create work aids for carrying out Cost Center Accounting
History
| Last changed by/on | SAP | 19971002 |
| SAP Release Created in |
