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

Function MEREP_SCENARIO_COPY 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_SCENARIO_COPY'"SyncBO Copy.
EXPORTING
SCENARIO = "SAP Mobile: Scenario ID
EXCEPTIONS
NO_SYNCBO_FOUND = 1 NO_SYNCBO_SPECIFIED = 2
IMPORTING Parameters details for MEREP_SCENARIO_COPY
SCENARIO - SAP Mobile: Scenario ID
Data type: MEREP_SCENARIOOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SYNCBO_FOUND -
Data type:Optional: No
Call by Reference: Yes
NO_SYNCBO_SPECIFIED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MEREP_SCENARIO_COPY 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_scenario | TYPE MEREP_SCENARIO, " | |||
| lv_no_syncbo_found | TYPE MEREP_SCENARIO, " | |||
| lv_no_syncbo_specified | TYPE MEREP_SCENARIO. " |
|   CALL FUNCTION 'MEREP_SCENARIO_COPY' "SyncBO Copy |
| EXPORTING | ||
| SCENARIO | = lv_scenario | |
| EXCEPTIONS | ||
| NO_SYNCBO_FOUND = 1 | ||
| NO_SYNCBO_SPECIFIED = 2 | ||
| . " MEREP_SCENARIO_COPY | ||
ABAP code using 7.40 inline data declarations to call FM MEREP_SCENARIO_COPY
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