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

Function MEREP_T51_SCHEDULE_REPLICATION 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_T51_SCHEDULE_REPLICATION'"Schedule T51 Replication.
EXPORTING
NAME' ' = "Namespace
APPLICATION_NAME = "Mobile Component
APPLICATION_VERSION = "Version of Offline Application
SYNCBO = "SyncBO ID
TABLES
* RETURN = "Return Parameter
EXCEPTIONS
SCHEDULE_FAILED = 1
IMPORTING Parameters details for MEREP_T51_SCHEDULE_REPLICATION
NAMESPACE - Namespace
Data type: NAMESPACEOptional: No
Call by Reference: No ( called with pass by value option)
APPLICATION_NAME - Mobile Component
Data type: MSDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
APPLICATION_VERSION - Version of Offline Application
Data type: BWAFVERSOptional: No
Call by Reference: No ( called with pass by value option)
SYNCBO - SyncBO ID
Data type: MEREP_SCENARIOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MEREP_T51_SCHEDULE_REPLICATION
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
SCHEDULE_FAILED - Failed to schedule the replication
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MEREP_T51_SCHEDULE_REPLICATION 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: | ||||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_namespace | TYPE NAMESPACE, " | |||
| lv_schedule_failed | TYPE NAMESPACE, " | |||
| lv_application_name | TYPE MSDNAME, " | |||
| lv_application_version | TYPE BWAFVERS, " | |||
| lv_syncbo | TYPE MEREP_SCENARIO. " |
|   CALL FUNCTION 'MEREP_T51_SCHEDULE_REPLICATION' "Schedule T51 Replication |
| EXPORTING | ||
| NAMESPACE | = lv_namespace | |
| APPLICATION_NAME | = lv_application_name | |
| APPLICATION_VERSION | = lv_application_version | |
| SYNCBO | = lv_syncbo | |
| TABLES | ||
| RETURN | = lt_return | |
| EXCEPTIONS | ||
| SCHEDULE_FAILED = 1 | ||
| . " MEREP_T51_SCHEDULE_REPLICATION | ||
ABAP code using 7.40 inline data declarations to call FM MEREP_T51_SCHEDULE_REPLICATION
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