SAP ME_UPD_APP_DEPENDENCY Function Module for

Search SAP Function Modules

ME_UPD_APP_DEPENDENCY is a standard me upd app dependency SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 me upd app dependency FM, simply by entering the name ME_UPD_APP_DEPENDENCY into the relevant SAP transaction such as SE37 or SE38.

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

Function ME_UPD_APP_DEPENDENCY 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 'ME_UPD_APP_DEPENDENCY'"
  EXPORTING
   NAME =  "
*  NAME' ' =  "Namespace
   VERSION =  "Version of Offline Application
   DEPENDENT_APP_NAME =  "
*  DEPENDENT_APP_NAME' ' =  "Namespace
   DEPENDENT_APP_VERSION =  "Version of Offline Application
*  INSTALLATION_SEQUENCE =  "

EXCEPTIONS
   APP_NOT_FOUND = 1    DEPENDENT_APP_NOT_FOUND = 2    ERROR_DURING_CREATION = 3 

.

IMPORTING Parameters details for ME_UPD_APP_DEPENDENCY

NAME -

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

NAMESPACE - Namespace

Data type: MEMSD-NAMESPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

VERSION - Version of Offline Application

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

DEPENDENT_APP_NAME -

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

DEPENDENT_APP_NAMESPACE - Namespace

Data type: MEMSD-NAMESPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEPENDENT_APP_VERSION - Version of Offline Application

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

INSTALLATION_SEQUENCE -

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

EXCEPTIONS details

APP_NOT_FOUND - Application does not Exist

Data type:
Optional: No
Call by Reference: Yes

DEPENDENT_APP_NOT_FOUND - Dependent Application does not Exist

Data type:
Optional: No
Call by Reference: Yes

ERROR_DURING_CREATION - Error During Creation

Data type:
Optional: No
Call by Reference: Yes

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

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