SAP INTEGRATION_AFTER_UPDATE Function Module for









INTEGRATION_AFTER_UPDATE is a standard integration after update 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 integration after update FM, simply by entering the name INTEGRATION_AFTER_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHPR
Program Name: SAPLRHPR
Main Program: SAPLRHPR
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function INTEGRATION_AFTER_UPDATE 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 'INTEGRATION_AFTER_UPDATE'"
EXPORTING
* ENQUEUE = 'X' "
* IV_LANGU = ' ' "
* IV_SESSION_NAME = ' ' "
* IV_NO_BATCH = ' ' "

TABLES
XPLOG_TAB = "
* XTB_PLOG_TAB = "
.



IMPORTING Parameters details for INTEGRATION_AFTER_UPDATE

ENQUEUE -

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

IV_LANGU -

Data type: RH_USE_NO_LANGU_T527X
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_SESSION_NAME -

Data type: APQ_GRPN
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_NO_BATCH -

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for INTEGRATION_AFTER_UPDATE

XPLOG_TAB -

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

XTB_PLOG_TAB -

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

Copy and paste ABAP code example for INTEGRATION_AFTER_UPDATE 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_enqueue  TYPE PPPAR-VTASK, "   'X'
lt_xplog_tab  TYPE STANDARD TABLE OF HRDBTAB, "   
lv_iv_langu  TYPE RH_USE_NO_LANGU_T527X, "   SPACE
lt_xtb_plog_tab  TYPE STANDARD TABLE OF HRTBUFFER, "   
lv_iv_session_name  TYPE APQ_GRPN, "   SPACE
lv_iv_no_batch  TYPE FLAG. "   SPACE

  CALL FUNCTION 'INTEGRATION_AFTER_UPDATE'  "
    EXPORTING
         ENQUEUE = lv_enqueue
         IV_LANGU = lv_iv_langu
         IV_SESSION_NAME = lv_iv_session_name
         IV_NO_BATCH = lv_iv_no_batch
    TABLES
         XPLOG_TAB = lt_xplog_tab
         XTB_PLOG_TAB = lt_xtb_plog_tab
. " INTEGRATION_AFTER_UPDATE




ABAP code using 7.40 inline data declarations to call FM INTEGRATION_AFTER_UPDATE

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 VTASK FROM PPPAR INTO @DATA(ld_enqueue).
DATA(ld_enqueue) = 'X'.
 
 
DATA(ld_iv_langu) = ' '.
 
 
DATA(ld_iv_session_name) = ' '.
 
DATA(ld_iv_no_batch) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!