SAP MSAM_MO_SERVER_DRIVEN_TRIGGER Function Module for MSAM : Server Driven Replication

Search SAP Function Modules

MSAM_MO_SERVER_DRIVEN_TRIGGER is a standard msam mo server driven trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MSAM : Server Driven 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 msam mo server driven trigger FM, simply by entering the name MSAM_MO_SERVER_DRIVEN_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

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

Function MSAM_MO_SERVER_DRIVEN_TRIGGER 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 'MSAM_MO_SERVER_DRIVEN_TRIGGER'"MSAM : Server Driven Replication
  EXPORTING
*  OBJTYP =  "
*  FIXED_DESTINATIONS = ' ' "
*  QUEUE_NAME =  "Queue Name for Background RFC
*  LOCK =  "General Flag

TABLES
*  KEYS =  "R/3 Keys for Transfer to Server Drives
*  DESTINATIONS =  "MSAM RFC Destinations for Server Drives
*  RETURN =  "

.

IMPORTING Parameters details for MSAM_MO_SERVER_DRIVEN_TRIGGER

OBJTYP -

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

FIXED_DESTINATIONS -

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

QUEUE_NAME - Queue Name for Background RFC

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

LOCK - General Flag

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

TABLES Parameters details for MSAM_MO_SERVER_DRIVEN_TRIGGER

KEYS - R/3 Keys for Transfer to Server Drives

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

DESTINATIONS - MSAM RFC Destinations for Server Drives

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

RETURN -

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

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

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