SAP CGPL_MSP_MAPPING_CUSTOMIZING Function Module for Call Customizing for MSP Field Mapping
CGPL_MSP_MAPPING_CUSTOMIZING is a standard cgpl msp mapping customizing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call Customizing for MSP Field 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 cgpl msp mapping customizing FM, simply by entering the name CGPL_MSP_MAPPING_CUSTOMIZING into the relevant SAP transaction such as SE37 or SE38.
Function Group: CGPL_MSP_INTERFACE
Program Name: SAPLCGPL_MSP_INTERFACE
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CGPL_MSP_MAPPING_CUSTOMIZING 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 'CGPL_MSP_MAPPING_CUSTOMIZING'"Call Customizing for MSP Field Mapping.
EXPORTING
IM_APPLICATION = "Application in Project Planning
* IM_ALTERNATIVE = ' ' "Alternative
* IM_DISPLAY = ' ' "Display mode
TABLES
IM_STRUCTURES = "Table with Structure Name
* IM_EXCL_FIELDS = "Fields to Be Excluded from Field Assignment
* IM_NO_IMPORT_FIELDS = "Fields for Which Import Is Not Allowed
IMPORTING Parameters details for CGPL_MSP_MAPPING_CUSTOMIZING
IM_APPLICATION - Application in Project Planning
Data type: CGPL_APPLICATION_TYPEOptional: No
Call by Reference: Yes
IM_ALTERNATIVE - Alternative
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
IM_DISPLAY - Display mode
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for CGPL_MSP_MAPPING_CUSTOMIZING
IM_STRUCTURES - Table with Structure Name
Data type: CGPL_TABNAMESOptional: No
Call by Reference: Yes
IM_EXCL_FIELDS - Fields to Be Excluded from Field Assignment
Data type: DCBTFIELDSOptional: Yes
Call by Reference: Yes
IM_NO_IMPORT_FIELDS - Fields for Which Import Is Not Allowed
Data type: DCBTFIELDSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CGPL_MSP_MAPPING_CUSTOMIZING 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: | ||||
| lt_im_structures | TYPE STANDARD TABLE OF CGPL_TABNAMES, " | |||
| lv_im_application | TYPE CGPL_APPLICATION_TYPE, " | |||
| lv_im_alternative | TYPE CHAR1, " SPACE | |||
| lt_im_excl_fields | TYPE STANDARD TABLE OF DCBTFIELDS, " | |||
| lv_im_display | TYPE FLAG, " SPACE | |||
| lt_im_no_import_fields | TYPE STANDARD TABLE OF DCBTFIELDS. " |
|   CALL FUNCTION 'CGPL_MSP_MAPPING_CUSTOMIZING' "Call Customizing for MSP Field Mapping |
| EXPORTING | ||
| IM_APPLICATION | = lv_im_application | |
| IM_ALTERNATIVE | = lv_im_alternative | |
| IM_DISPLAY | = lv_im_display | |
| TABLES | ||
| IM_STRUCTURES | = lt_im_structures | |
| IM_EXCL_FIELDS | = lt_im_excl_fields | |
| IM_NO_IMPORT_FIELDS | = lt_im_no_import_fields | |
| . " CGPL_MSP_MAPPING_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM CGPL_MSP_MAPPING_CUSTOMIZING
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.| DATA(ld_im_alternative) | = ' '. | |||
| DATA(ld_im_display) | = ' '. | |||
Search for further information about these or an SAP related objects