Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-MAP (Application Component) Merchandise and Assortment Planning⤷
CM_MAP (Package) Category Management - MAP
IMG Activity
| ID | W_CM_MD_0006 | Define Function Module for Uploading Attributes |
| Transaction Code | S_AX8_68000135 | Generated |
| Created on | 20010807 | |
| Customizing Attributes | W_CM_MD_1000 | Attributes for Category Management |
| Customizing Activity | W_CM_MD_0006 | Define Function Module for Uploading Attributes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_CM_MD_0006 |
In this IMG activity, you store the function module, which determines the records of the master data hierarchy that is transferred to a planning hierarchy in Merchandise and Assortment Planning.
You need to perform this IMG activity before you can use the function "Automatic Generation of the Planning Hierarchy using Master Data".
The function module is specified for each master data hierarchy structure and for each set of characteristics on which the hierarchy records to be constructed depend.
To be able to automatically enrich other planning levels in the planning hierarchy in addition to the planning levels belonging to the master data hierarchy, create the relevant function modules in the IMG activity Define Function Module for Structuring a Master Data Hierarchy.
Example
Requirements
You have programmed the required function module for determining the hierarchy records.
Standard settings
The table to be filled in this IMG activity has separate namespaces for SAP deliveries (priority = SAP) and customer developments (priority = customer). If the other entries are the same (determination characteristics for characteristics on which the master data hierarchy depends, and hierarchy for master data hierarchy), the customer settings are used.
SAP already provides some function modules in the category management scenario 1_CM, which you can use directly to transfer the CDT to Merchandise and Assortment Planning. The relevant Customizing entries in the SAP namespace are already entered in the table to be maintained.
Recommendation
Activities
If the master data hierarchy is not dependent on other characteristics, you do not need to enter the determination characteristics.
Example
The following entry, among others, is already contained in the standard system:
- Priority: SAP
- Determination characteristics: WISP_CM_HIER_ID_2_CDT1
- Hierarchy: WISP_CM_CDT2_2_CDT4
- Function module: CM_MAP_BUILD_CDT2_2_CDT4
- The entry can be interpreted as follows:
- Priority SAP indicates that it is a standard delivery.
- The determination characteristics WISP_CM_HIER_ID_2_CDT1 describe a DDIC structure that contains the characteristics HIER_ID (Hierarchy-ID) and CDT1 (CDT Level 1- Category) The master data hierarchy to be constructed is dependent on these two characteristics.
- The hierarchy WISP_CM_CDT2_2_CDT4 is a DDIC structure with the components CDT2 (CDT Level 2 - Subcategory), CDT3 (CDT Level 3 - Segment) and CDT4 (CDT Level 4 -Subsegment). The hierarchy records to be constructed should contain exactly these characteristics.
- Therefore, for a category for a certain hierarchy ID, the function module CM_MAP_BUILD_CDT2_2_CDT4 must determine the lower-level nodes of the CDT up to level CDT4.
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 |
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_TWISPC_FBATTRB | V - View | SM30 |
History
| Last changed by/on | SAP | 20020909 |
| SAP Release Created in | 1999_1_46C |
