SAP EM_GET_MERGE_INFO_FOR_REQUEST Function Module for

Search SAP Function Modules

EM_GET_MERGE_INFO_FOR_REQUEST is a standard em get merge info for request 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 em get merge info for request FM, simply by entering the name EM_GET_MERGE_INFO_FOR_REQUEST into the relevant SAP transaction such as SE37 or SE38.

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

Function EM_GET_MERGE_INFO_FOR_REQUEST 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 'EM_GET_MERGE_INFO_FOR_REQUEST'"
  EXPORTING
   IV_KORR =  "

 IMPORTING
   EV_SYSTEM =  "

TABLES
   ET_MERGE =  "
   ET_MERGETA =  "
   ET_MERGEOBJ =  "
   ET_E07T =  "

EXCEPTIONS
   EM_NO_TRANSPORT = 1    EM_NOT_DELIVERED = 2    EM_CUSTOMER_SYSTEM = 3    EM_COMMUNICATION_FAILURE = 4 

.

IMPORTING Parameters details for EM_GET_MERGE_INFO_FOR_REQUEST

IV_KORR -

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

EXPORTING Parameters details for EM_GET_MERGE_INFO_FOR_REQUEST

EV_SYSTEM -

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

TABLES Parameters details for EM_GET_MERGE_INFO_FOR_REQUEST

ET_MERGE -

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

ET_MERGETA -

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

ET_MERGEOBJ -

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

ET_E07T -

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

EXCEPTIONS details

EM_NO_TRANSPORT -

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

EM_NOT_DELIVERED -

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

EM_CUSTOMER_SYSTEM -

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

EM_COMMUNICATION_FAILURE -

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

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

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