SAP RSHDB_PC_MERGE_TRIGGER Function Module for Triggering the NewDB Merges
RSHDB_PC_MERGE_TRIGGER is a standard rshdb pc merge 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 Triggering the NewDB Merges 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 rshdb pc merge trigger FM, simply by entering the name RSHDB_PC_MERGE_TRIGGER into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSHDB_PC
Program Name: SAPLRSHDB_PC
Main Program: SAPLRSHDB_PC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function RSHDB_PC_MERGE_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 'RSHDB_PC_MERGE_TRIGGER'"Triggering the NewDB Merges.
EXPORTING
I_T_TLOGO = "BW Repository: TLOGO Object, type and type of association
* I_REQUID = "Data Transfer Process Request
IMPORTING
E_SUBRC = "Return Value from ABAP Statements
E_T_MSG = "BW: Table with Messages (Application Log)
IMPORTING Parameters details for RSHDB_PC_MERGE_TRIGGER
I_T_TLOGO - BW Repository: TLOGO Object, type and type of association
Data type: RSTRAN_T_TLOGOOptional: No
Call by Reference: No ( called with pass by value option)
I_REQUID - Data Transfer Process Request
Data type: RSBKREQUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSHDB_PC_MERGE_TRIGGER
E_SUBRC - Return Value from ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
E_T_MSG - BW: Table with Messages (Application Log)
Data type: RS_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSHDB_PC_MERGE_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.DATA: | ||||
lv_e_subrc | TYPE SY-SUBRC, " | |||
lv_i_t_tlogo | TYPE RSTRAN_T_TLOGO, " | |||
lv_e_t_msg | TYPE RS_T_MSG, " | |||
lv_i_requid | TYPE RSBKREQUID. " |
  CALL FUNCTION 'RSHDB_PC_MERGE_TRIGGER' "Triggering the NewDB Merges |
EXPORTING | ||
I_T_TLOGO | = lv_i_t_tlogo | |
I_REQUID | = lv_i_requid | |
IMPORTING | ||
E_SUBRC | = lv_e_subrc | |
E_T_MSG | = lv_e_t_msg | |
. " RSHDB_PC_MERGE_TRIGGER |
ABAP code using 7.40 inline data declarations to call FM RSHDB_PC_MERGE_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."SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
Search for further information about these or an SAP related objects