SAP CM_MAP_BUILD_HIER Function Module for NOTRANSL: Aufbau einer Stammdatenhierarchie
CM_MAP_BUILD_HIER is a standard cm map build hier SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Aufbau einer Stammdatenhierarchie processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for cm map build hier FM, simply by entering the name CM_MAP_BUILD_HIER into the relevant SAP transaction such as SE37 or SE38.
Function Group: CM_MAP_MD
Program Name: SAPLCM_MAP_MD
Main Program: SAPLCM_MAP_MD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CM_MAP_BUILD_HIER pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CM_MAP_BUILD_HIER'"NOTRANSL: Aufbau einer Stammdatenhierarchie.
EXPORTING
I_BATCH = "
* I_DYNPRO = "Retail Planning: Screen Fields
* I_DYNPRO_CM = "Retail Planning: Additional Screen Fields for CM
IMPORTING Parameters details for CM_MAP_BUILD_HIER
I_BATCH -
Data type: COptional: No
Call by Reference: Yes
I_DYNPRO - Retail Planning: Screen Fields
Data type: WISP_DYNPROOptional: Yes
Call by Reference: Yes
I_DYNPRO_CM - Retail Planning: Additional Screen Fields for CM
Data type: WISP_DYNPRO_CMOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CM_MAP_BUILD_HIER Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_batch | TYPE C, " | |||
| lv_i_dynpro | TYPE WISP_DYNPRO, " | |||
| lv_i_dynpro_cm | TYPE WISP_DYNPRO_CM. " |
|   CALL FUNCTION 'CM_MAP_BUILD_HIER' "NOTRANSL: Aufbau einer Stammdatenhierarchie |
| EXPORTING | ||
| I_BATCH | = lv_i_batch | |
| I_DYNPRO | = lv_i_dynpro | |
| I_DYNPRO_CM | = lv_i_dynpro_cm | |
| . " CM_MAP_BUILD_HIER | ||
ABAP code using 7.40 inline data declarations to call FM CM_MAP_BUILD_HIER
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects