SAP MCP_GET_CONFIG_DATA Function Module for NOTRANSL: Übergabe von Statistikdaten an Merkmalsvorplanung

Search SAP Function Modules

MCP_GET_CONFIG_DATA is a standard mcp get config data 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: Übergabe von Statistikdaten an Merkmalsvorplanung 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 mcp get config data FM, simply by entering the name MCP_GET_CONFIG_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: MCP2
Program Name: SAPLMCP2
Main Program: SAPLMCP2
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCP_GET_CONFIG_DATA 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 'MCP_GET_CONFIG_DATA'"NOTRANSL: Übergabe von Statistikdaten an Merkmalsvorplanung
  EXPORTING
   I_WERK =  "Plant
   I_MATNR =  "Material Number
*  I_VRSIO = 000 "Version number in the information structure
   I_GSTRU =  "Generated DDIC table for LIS, conditions, messages
   I_VONDAT =  "ABAP System Field: Current Date of Application Server
   I_BISDAT =  "ABAP System Field: Current Date of Application Server
*  I_NO_CUCY = ' ' "

TABLES
   T_DATA =  "Display structure: usage probabilities - charac. planning
   T_IDATF =  "Data Fields Table

EXCEPTIONS
   NO_OBJECTS_FOUND = 1    INVALID_INFOSTRUCTURE = 2    INFOSTRUCTURE_NOT_THERE = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMCP2_008 User Exit: Processing Header Data in a Purchase Order from an IDoc
EXIT_SAPLMCP2_009 User Exit: Processing Item Data in a Purchase Order from an IDoc

IMPORTING Parameters details for MCP_GET_CONFIG_DATA

I_WERK - Plant

Data type: T001W-WERKS
Optional: No
Call by Reference: No ( called with pass by value option)

I_MATNR - Material Number

Data type: MARA-MATNR
Optional: No
Call by Reference: No ( called with pass by value option)

I_VRSIO - Version number in the information structure

Data type: P44V-VRSIO
Default: 000
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GSTRU - Generated DDIC table for LIS, conditions, messages

Data type: TMC4-GSTRU
Optional: No
Call by Reference: No ( called with pass by value option)

I_VONDAT - ABAP System Field: Current Date of Application Server

Data type: SY-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

I_BISDAT - ABAP System Field: Current Date of Application Server

Data type: SY-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

I_NO_CUCY -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MCP_GET_CONFIG_DATA

T_DATA - Display structure: usage probabilities - charac. planning

Data type: RM60C
Optional: No
Call by Reference: No ( called with pass by value option)

T_IDATF - Data Fields Table

Data type: IDATF
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_OBJECTS_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_INFOSTRUCTURE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INFOSTRUCTURE_NOT_THERE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MCP_GET_CONFIG_DATA 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.

ABAP code using 7.40 inline data declarations to call FM MCP_GET_CONFIG_DATA

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