Kontakt

Ansicht
Dokumentation

W_CM_MD_0005 - Define Function Module for Structuring a Master Data Hierarchy

W_CM_MD_0005 - Define Function Module for Structuring a Master Data Hierarchy

General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you store the function module, which determines the values of the master data attributes that need to be 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 attribute (a planning level in the planning hierarchy) and for each set of characteristics, on which the attribute values to be determined 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, store the relevant function modules in this IMG activity.

You have programmed the required function modules for determining the master data attributes.

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 (Attribute for the name of the master data attribute and Context for the characteristics on which the attribute values are dependent), the customer settings are used.

SAP already provides some function modules in the category management scenario 1_CM, which you can use directly to enrich attributes in Merchandise and Assortment Planning. The relevant Customizing entries in the SAP namespace are already entered in the table to be maintained.

If an attribute is not dependent on other characteristics, you do not need to enter the context structure.

Maintain the entry in the SPACE field as follows: It is conceivable that for a specific context, no valid values can be determined for an attribute. In this case, the function module has to return an entry that indicates exactly this situation. You cannot use the constant value SPACE as, depending on the data type of the attribute (for example, NUMC), this value is not possible. A type-relevant initial value (in the case "NUMC 0...0") does not automatically mean that a value was not found: so for example, 0000 is a possible value for the season. You can therefore define your own value that indicates the situation described above and store it here.

The following entry, among others, is already contained in the standard system:

  • Priority: SAP
  • Attribute: REGIO
  • Context: WISP_CM_CONTEXT_4_REGIO
  • Function module: CM_MAP_ATTR_REGIO_4_HIEID_LAND
  • Space:

The entry can be interpreted as follows:

  • Priority SAP indicates that it is a standard delivery.
  • REGIO (Region) is the name of the attribute for which the values are to be defined.
  • The context WISP_CM_CONTEXT_4_REGIO is a DDIC structure with the components HIER_ID (hierarchy ID) and CM_LAND1 (country/region). The values to be determined for the region should depend exactly on these characteristics.
  • The function module WISP_CM_CONTEXT_4_REGIO therefore has to determine the values of the relevant regions for a specified hierarchy ID and a specified country/region.
  • The initial entry in the Space field indicates that if no region is found, an initial entry will be returned.





Addresses (Business Address Services)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 3668 Date: 20240523 Time: 202037     sap01-206 ( 70 ms )