SAP CNV_20100_WRITE_ME_MAPPING Function Module for Initializes the complete ME mapping
CNV_20100_WRITE_ME_MAPPING is a standard cnv 20100 write me mapping SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initializes the complete ME mapping 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 cnv 20100 write me mapping FM, simply by entering the name CNV_20100_WRITE_ME_MAPPING into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_20100_CONTROLSYSTEM
Program Name: SAPLCNV_20100_CONTROLSYSTEM
Main Program: SAPLCNV_20100_CONTROLSYSTEM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CNV_20100_WRITE_ME_MAPPING 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 'CNV_20100_WRITE_ME_MAPPING'"Initializes the complete ME mapping.
EXPORTING
IV_PCL_PACK = "package information/creator/creation date/scenarion
* IV_CLEAR_MAPPING = "boolean variable (X=true, -=false, space=unknown)
* IT_KTOPL_MAPPING = "Chart of Accounts mapping (in ME)
* IT_T004_MAPPING = "Customizing for new chart of accounts (in ME)
* IT_BUKRS_MAPPING = "Extended mapping for participating company codes (in ME)
* IT_SAKNR_MAPPING = "Extended G/L accounts mapping (in ME)
* IT_KSTAR_MAPPING = "Extended secondary cost elements mapping (in ME)
* IT_OTHERS_MAPPING = "Extended OTHERS mapping (in ME)
IMPORTING
EV_ERROR_OCCURRED = "boolean variable (X=true, -=false, space=unknown)
EV_REASON = "reason for error
IMPORTING Parameters details for CNV_20100_WRITE_ME_MAPPING
IV_PCL_PACK - package information/creator/creation date/scenarion
Data type: CNV_MBT_PACKIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_CLEAR_MAPPING - boolean variable (X=true, -=false, space=unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_KTOPL_MAPPING - Chart of Accounts mapping (in ME)
Data type: CNV_20100_T_KTOPLOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_T004_MAPPING - Customizing for new chart of accounts (in ME)
Data type: CNV_20100_T_T004Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_BUKRS_MAPPING - Extended mapping for participating company codes (in ME)
Data type: CNV_20100_T_BUKRS_HIEROptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SAKNR_MAPPING - Extended G/L accounts mapping (in ME)
Data type: CNV_20100_T_SAKNR_HIEROptional: Yes
Call by Reference: No ( called with pass by value option)
IT_KSTAR_MAPPING - Extended secondary cost elements mapping (in ME)
Data type: CNV_20100_T_KSTAR_HIEROptional: Yes
Call by Reference: No ( called with pass by value option)
IT_OTHERS_MAPPING - Extended OTHERS mapping (in ME)
Data type: CNV_20100_T_OTHERS_HIEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_20100_WRITE_ME_MAPPING
EV_ERROR_OCCURRED - boolean variable (X=true, -=false, space=unknown)
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
EV_REASON - reason for error
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNV_20100_WRITE_ME_MAPPING 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_iv_pcl_pack | TYPE CNV_MBT_PACKID, " | |||
| lv_ev_error_occurred | TYPE BOOLEAN, " | |||
| lv_ev_reason | TYPE STRING, " | |||
| lv_iv_clear_mapping | TYPE BOOLEAN, " | |||
| lv_it_ktopl_mapping | TYPE CNV_20100_T_KTOPL, " | |||
| lv_it_t004_mapping | TYPE CNV_20100_T_T004, " | |||
| lv_it_bukrs_mapping | TYPE CNV_20100_T_BUKRS_HIER, " | |||
| lv_it_saknr_mapping | TYPE CNV_20100_T_SAKNR_HIER, " | |||
| lv_it_kstar_mapping | TYPE CNV_20100_T_KSTAR_HIER, " | |||
| lv_it_others_mapping | TYPE CNV_20100_T_OTHERS_HIER. " |
|   CALL FUNCTION 'CNV_20100_WRITE_ME_MAPPING' "Initializes the complete ME mapping |
| EXPORTING | ||
| IV_PCL_PACK | = lv_iv_pcl_pack | |
| IV_CLEAR_MAPPING | = lv_iv_clear_mapping | |
| IT_KTOPL_MAPPING | = lv_it_ktopl_mapping | |
| IT_T004_MAPPING | = lv_it_t004_mapping | |
| IT_BUKRS_MAPPING | = lv_it_bukrs_mapping | |
| IT_SAKNR_MAPPING | = lv_it_saknr_mapping | |
| IT_KSTAR_MAPPING | = lv_it_kstar_mapping | |
| IT_OTHERS_MAPPING | = lv_it_others_mapping | |
| IMPORTING | ||
| EV_ERROR_OCCURRED | = lv_ev_error_occurred | |
| EV_REASON | = lv_ev_reason | |
| . " CNV_20100_WRITE_ME_MAPPING | ||
ABAP code using 7.40 inline data declarations to call FM CNV_20100_WRITE_ME_MAPPING
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