Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
LO-MD (Application Component) Logistics Basic Data⤷
WRF_CM_MD (Package) Category Management - Master Data
IMG Activity
| ID | W_CM_0002 | Edit Hierarchy Levels |
| Transaction Code | S_XB4_60000007 | (empty) |
| Created on | 20040112 | |
| Customizing Attributes | W_CM_0002 | Edit Hierarchy Levels |
| Customizing Activity | W_CM_0002 | Edit Hierarchy Levels |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_CM_0002 |
Use
In this IMG activity, you define hierarchy level semantics descriptions of the hierarchy levels to simplify navigation in the article hierarchy. The levels are defined top-down, which means the first level corresponds to the top node level of the article hierarchy in the article structure, the second level corresponds to the child node level of the top node, and so on.
You can maintain a level of the article hierarchy as the category level in the Customizing table. When a hierarchy node is created (in hierarchy maintenance or from an external system via the BAPI interface), the system checks whether a node of this category level is involved.
Defining a node or level in the article hierarchy as a category has the following effects:
- The category is the root node of the assigned CDT (Consumer Decision Tree).
- The category defines the top assortment-forming node.
- The category is the top relevant node for update to the SAP BW in category management.
- If multiple article assignment is used, the category is the node used to resolve the multiple assignment. The article is always assigned uniquely within the category.
- If multiple article assignment is used, the category is the node used to determine the department store-shop assignment.
- Defining a category level simplifies maintenance of the category when a certain level of the article hierarchy - and thus all the nodes in this level - are defined as categories. Alternatively, manual maintenance of hierarchy nodes is possible in the hierarchy maintenance transaction. This is only possible, however, if no level is marked as a category. A plausibility check ensures that only one level is defined as the category level.
You can only change the category flag if no article hierarchies exist yet in the system.
You can define an event pushbutton for every level of the article hierarchy in the dialog screen. This button enables modification-free navigation to any other program or any other transaction. You can define a label for the event pushbutton here.
Requirements
Defining hierarchy level semantics only makes sense in properly defined hierarchy structures. The node in the hierarchy does not transfer the semantics when nodes are moved between levels. Once the semantics have been defined, they can only be changed if no article hierarchy exists yet in the system.
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | W_CM_0002 | 0 | HLA0006434 | Logistics Basic Data |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_WRF_MATGRP_TRE | V - View | SM30 |
History
| Last changed by/on | SAP | 20040719 |
| SAP Release Created in | 111 |
