SAP ME_DEL_APP_CONDITIONS Function Module for









ME_DEL_APP_CONDITIONS is a standard me del app conditions 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 del app conditions FM, simply by entering the name ME_DEL_APP_CONDITIONS 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_DEL_APP_CONDITIONS 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_DEL_APP_CONDITIONS'"
  EXPORTING
   NAME =  "
*  NAME' ' =  "Namespace
   VERSION =  "Version of Offline Application

TABLES
   CONDITION_VALUES =  "

EXCEPTIONS
   APP_NOT_FUUND = 1    ERROR_DURING_DELETION = 2
.



IMPORTING Parameters details for ME_DEL_APP_CONDITIONS

NAME -

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

NAMESPACE - Namespace

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

VERSION - Version of Offline Application

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

TABLES Parameters details for ME_DEL_APP_CONDITIONS

CONDITION_VALUES -

Data type: MEMSD_DEP_INTERFACE_LIST
Optional: No
Call by Reference: Yes

EXCEPTIONS details

APP_NOT_FUUND -

Data type:
Optional: No
Call by Reference: Yes

ERROR_DURING_DELETION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ME_DEL_APP_CONDITIONS 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_name  TYPE MSDNAME, "   
lv_app_not_fuund  TYPE MSDNAME, "   
lt_condition_values  TYPE STANDARD TABLE OF MEMSD_DEP_INTERFACE_LIST, "   
lv_namespace  TYPE NAMESPACE, "   
lv_error_during_deletion  TYPE NAMESPACE, "   
lv_version  TYPE BWAFVERS. "   

  CALL FUNCTION 'ME_DEL_APP_CONDITIONS'  "
    EXPORTING
         NAME = lv_name
         NAMESPACE = lv_namespace
         VERSION = lv_version
    TABLES
         CONDITION_VALUES = lt_condition_values
    EXCEPTIONS
        APP_NOT_FUUND = 1
        ERROR_DURING_DELETION = 2
. " ME_DEL_APP_CONDITIONS




ABAP code using 7.40 inline data declarations to call FM ME_DEL_APP_CONDITIONS

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!