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

Function MEMGMT_MCD_UPDATE 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 'MEMGMT_MCD_UPDATE'"ME: Update MCD.
EXPORTING
* NAME' ' = "Namespace
NAME = "Mobile Component
VERSION = "Version der mobilen Komponente
* TEXT = "Short Text for Mobile Component Descriptor
* APPLTYPE = "Mobile Component Descriptor Property Value
* RUNTIME = "Mobile Component Descriptor Property Value
* CLIENT_BUILDNUMBER = "Mobile Component Descriptor Property Value
* ROLEDEFAULT = "Mobile Component Descriptor Property Value
* HOMEPAGE_VISIBLE = "Mobile Component Descriptor Customizing Attribute Value
TABLES
* SETUPFILES = "Mobile Solution Descriptor: Customizing Data for Interface
RETURN = "Return Parameter
* PROPERTIES = "Mobile Solution Descriptor: Property for Interface
IMPORTING Parameters details for MEMGMT_MCD_UPDATE
NAMESPACE - Namespace
Data type: MEMSD-NAMESPACEOptional: Yes
Call by Reference: No ( called with pass by value option)
NAME - Mobile Component
Data type: MEMSD-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
VERSION - Version der mobilen Komponente
Data type: MEMSD-VERSIONOptional: No
Call by Reference: No ( called with pass by value option)
TEXT - Short Text for Mobile Component Descriptor
Data type: MEMSD_TEXT-TEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLTYPE - Mobile Component Descriptor Property Value
Data type: MEMSD_PROP-VALUEOptional: Yes
Call by Reference: No ( called with pass by value option)
RUNTIME - Mobile Component Descriptor Property Value
Data type: MEMSD_PROP-VALUEOptional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT_BUILDNUMBER - Mobile Component Descriptor Property Value
Data type: MEMSD_PROP-VALUEOptional: Yes
Call by Reference: No ( called with pass by value option)
ROLEDEFAULT - Mobile Component Descriptor Property Value
Data type: MEMSD_PROP-VALUEOptional: Yes
Call by Reference: No ( called with pass by value option)
HOMEPAGE_VISIBLE - Mobile Component Descriptor Customizing Attribute Value
Data type: MEMSD_CUST-ATTRIBUTE_VALUEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MEMGMT_MCD_UPDATE
SETUPFILES - Mobile Solution Descriptor: Customizing Data for Interface
Data type: MEMSD_CUST_INTERFACEOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: Yes
PROPERTIES - Mobile Solution Descriptor: Property for Interface
Data type: MEMSD_PROP_INTERFACEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for MEMGMT_MCD_UPDATE 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_namespace | TYPE MEMSD-NAMESPACE, " | |||
| lt_setupfiles | TYPE STANDARD TABLE OF MEMSD_CUST_INTERFACE, " | |||
| lv_name | TYPE MEMSD-NAME, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_version | TYPE MEMSD-VERSION, " | |||
| lt_properties | TYPE STANDARD TABLE OF MEMSD_PROP_INTERFACE, " | |||
| lv_text | TYPE MEMSD_TEXT-TEXT, " | |||
| lv_appltype | TYPE MEMSD_PROP-VALUE, " | |||
| lv_runtime | TYPE MEMSD_PROP-VALUE, " | |||
| lv_client_buildnumber | TYPE MEMSD_PROP-VALUE, " | |||
| lv_roledefault | TYPE MEMSD_PROP-VALUE, " | |||
| lv_homepage_visible | TYPE MEMSD_CUST-ATTRIBUTE_VALUE. " |
|   CALL FUNCTION 'MEMGMT_MCD_UPDATE' "ME: Update MCD |
| EXPORTING | ||
| NAMESPACE | = lv_namespace | |
| NAME | = lv_name | |
| VERSION | = lv_version | |
| TEXT | = lv_text | |
| APPLTYPE | = lv_appltype | |
| RUNTIME | = lv_runtime | |
| CLIENT_BUILDNUMBER | = lv_client_buildnumber | |
| ROLEDEFAULT | = lv_roledefault | |
| HOMEPAGE_VISIBLE | = lv_homepage_visible | |
| TABLES | ||
| SETUPFILES | = lt_setupfiles | |
| RETURN | = lt_return | |
| PROPERTIES | = lt_properties | |
| . " MEMGMT_MCD_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM MEMGMT_MCD_UPDATE
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.| "SELECT single NAMESPACE FROM MEMSD INTO @DATA(ld_namespace). | ||||
| "SELECT single NAME FROM MEMSD INTO @DATA(ld_name). | ||||
| "SELECT single VERSION FROM MEMSD INTO @DATA(ld_version). | ||||
| "SELECT single TEXT FROM MEMSD_TEXT INTO @DATA(ld_text). | ||||
| "SELECT single VALUE FROM MEMSD_PROP INTO @DATA(ld_appltype). | ||||
| "SELECT single VALUE FROM MEMSD_PROP INTO @DATA(ld_runtime). | ||||
| "SELECT single VALUE FROM MEMSD_PROP INTO @DATA(ld_client_buildnumber). | ||||
| "SELECT single VALUE FROM MEMSD_PROP INTO @DATA(ld_roledefault). | ||||
| "SELECT single ATTRIBUTE_VALUE FROM MEMSD_CUST INTO @DATA(ld_homepage_visible). | ||||
Search for further information about these or an SAP related objects