SAP TRINT_MERGE_COMMS Function Module for Internal: Merge Requests

Search SAP Function Modules

TRINT_MERGE_COMMS is a standard trint merge comms SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal: Merge Requests 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 trint merge comms FM, simply by entering the name TRINT_MERGE_COMMS into the relevant SAP transaction such as SE37 or SE38.

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

Function TRINT_MERGE_COMMS 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 'TRINT_MERGE_COMMS'"Internal: Merge Requests
  EXPORTING
   IT_E070 =  "
*  IV_E071_FILLED = ' ' "
*  IV_E071K_FILLED = ' ' "
*  IV_E071KF_FILLED = ' ' "
*  IV_E071K_STR_FILLED = ' ' "
*  IV_APPEND_COMM = 'X' "
*  IV_ADJUST_CLIENT = 'X' "
*  IV_KEEP_FLAGS = ' ' "

CHANGING
   CS_TARGET_REQUEST =  "Target Request
*  CT_E071 =  "
*  CT_E071K =  "
*  CT_E071KF =  "
*  CT_E071K_STR =  "

EXCEPTIONS
   DB_ACCESS_ERROR = 1    INVALID_TARGET_REQUEST = 2    INVALID_SOURCE_REQUEST = 3 

.

IMPORTING Parameters details for TRINT_MERGE_COMMS

IT_E070 -

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

IV_E071_FILLED -

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

IV_E071K_FILLED -

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

IV_E071KF_FILLED -

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

IV_E071K_STR_FILLED -

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

IV_APPEND_COMM -

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

IV_ADJUST_CLIENT -

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

IV_KEEP_FLAGS -

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

CHANGING Parameters details for TRINT_MERGE_COMMS

CS_TARGET_REQUEST - Target Request

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

CT_E071 -

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

CT_E071K -

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

CT_E071KF -

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

CT_E071K_STR -

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

EXCEPTIONS details

DB_ACCESS_ERROR - Database access error

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

INVALID_TARGET_REQUEST -

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

INVALID_SOURCE_REQUEST -

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

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

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