SAP MEREP_GET_SCENARIO Function Module for Return Metadata for Outside Caller









MEREP_GET_SCENARIO is a standard merep get scenario SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Return Metadata for Outside Caller 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 merep get scenario FM, simply by entering the name MEREP_GET_SCENARIO into the relevant SAP transaction such as SE37 or SE38.

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



Function MEREP_GET_SCENARIO 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 'MEREP_GET_SCENARIO'"Return Metadata for Outside Caller
  EXPORTING
   LANGUAGE =  "Language key
*  ALL_FLAG = 'X' "SAP Mobile: Action Flag for Metadata RFC
*  PUBLISHED_ONLY = ' ' "SAP Mobile: Action Flag for Metadata RFC

 IMPORTING
   RETURN =  "Return Parameter

TABLES
*  SCENARIO_ID =  "SAP Mobile: Structure for scenario import
   SCENARIO =  "SAP Mobile: Structure for scenario
   SCENARIO_RELATION =  "SAP Mobile: Structure for Scenario Relations
   STRUCTURE_LIST =  "SAP Mobile: Structure for structure list

EXCEPTIONS
   INVALID_SCENARIO = 1
.



IMPORTING Parameters details for MEREP_GET_SCENARIO

LANGUAGE - Language key

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

ALL_FLAG - SAP Mobile: Action Flag for Metadata RFC

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

PUBLISHED_ONLY - SAP Mobile: Action Flag for Metadata RFC

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

EXPORTING Parameters details for MEREP_GET_SCENARIO

RETURN - Return Parameter

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

TABLES Parameters details for MEREP_GET_SCENARIO

SCENARIO_ID - SAP Mobile: Structure for scenario import

Data type: MEREP_SCEN_IMPORT
Optional: Yes
Call by Reference: Yes

SCENARIO - SAP Mobile: Structure for scenario

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

SCENARIO_RELATION - SAP Mobile: Structure for Scenario Relations

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

STRUCTURE_LIST - SAP Mobile: Structure for structure list

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

EXCEPTIONS details

INVALID_SCENARIO -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MEREP_GET_SCENARIO 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_return  TYPE BAPIRETURN, "   
lv_language  TYPE MEREP_401T-LANG, "   
lt_scenario_id  TYPE STANDARD TABLE OF MEREP_SCEN_IMPORT, "   
lv_invalid_scenario  TYPE MEREP_SCEN_IMPORT, "   
lv_all_flag  TYPE MEREP_FLAG, "   'X'
lt_scenario  TYPE STANDARD TABLE OF MEREP_RFC_SCENARIO, "   
lv_published_only  TYPE MEREP_FLAG, "   ' '
lt_scenario_relation  TYPE STANDARD TABLE OF MEREP_SCEN_RELATION, "   
lt_structure_list  TYPE STANDARD TABLE OF MEREP_STRUCTURE_LIST. "   

  CALL FUNCTION 'MEREP_GET_SCENARIO'  "Return Metadata for Outside Caller
    EXPORTING
         LANGUAGE = lv_language
         ALL_FLAG = lv_all_flag
         PUBLISHED_ONLY = lv_published_only
    IMPORTING
         RETURN = lv_return
    TABLES
         SCENARIO_ID = lt_scenario_id
         SCENARIO = lt_scenario
         SCENARIO_RELATION = lt_scenario_relation
         STRUCTURE_LIST = lt_structure_list
    EXCEPTIONS
        INVALID_SCENARIO = 1
. " MEREP_GET_SCENARIO




ABAP code using 7.40 inline data declarations to call FM MEREP_GET_SCENARIO

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 LANG FROM MEREP_401T INTO @DATA(ld_language).
 
 
 
DATA(ld_all_flag) = 'X'.
 
 
DATA(ld_published_only) = ' '.
 
 
 


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!