SAP EXIT_SAPLJG21_108 Function Module for Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC
EXIT_SAPLJG21_108 is a standard exit sapljg21 108 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC 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 exit sapljg21 108 FM, simply by entering the name EXIT_SAPLJG21_108 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJG2
Program Name: SAPLXJG2
Main Program: SAPLXJG2
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLJG21_108 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 'EXIT_SAPLJG21_108'"Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC.
EXPORTING
LFA1_IN = "
LFB1_IN = "
LFBK_IN = "
TXTUSR = "
TABLES
BDCDATA = "
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISP_DEBITOR_CUSTOMER_UPDATE IS-M/SD: Customer-Specific Customer Updates in Non-SAP System
ISP_DEBITOR_ITEM_READ IS-M/SD: Customer - Get Open Items for ISP from Non-SAP System (FI)
ISP_DEBITOR_VAT_REG_NO_SORT IS-M: Resort VAT Registration Number for Change of Country
ISP_INSERT_DEBITOR IS-M/SD: Add Customer from IS-M/SD to a Different ERP System
ISP_INSERT_KREDITOR IS-M/SD: Add Vendor from IS-M/SD to Another ERP System
ISP_KREDITOR_ITEM_READ IS-M/SD: Get Vendor Open Items for ISP from Non-SAP System (FI)
ISP_READ_DEBITOR IS-M/SD: Read Customer in Non-SAP FI System
ISP_READ_KREDITOR IS-M/SD: Read Vendor in Non-SAP FI System
ISP_UPDATE_BANKDATEN IS-M/SD: Change Customer from IS-M/SD to Another ERP System
ISP_UPDATE_DEBITOR IS-M/SD: Change Customer from IS-M/SD to Another ERP System
ISP_UPDATE_DEBITOR_ADDRESS IS-M/SD: Change Customer from IS-M/SD to Another ERP System
ISP_UPDATE_KREDITOR IS-M/SD: Change Vendor from IS-M/SD to Another ERP System
ISP_UPDATE_KREDITOR_ADDRESS IS-M/SD: Change Vendor Address from IS-M/SD to Another ERP System
TABLEFRAME_JG21 Extended Table Maintenance: Upper Level
TABLEPROC_JG21 Extended Table Maintenance: Lower Level
IMPORTING Parameters details for EXIT_SAPLJG21_108
LFA1_IN -
Data type: LFA1Optional: No
Call by Reference: No ( called with pass by value option)
LFB1_IN -
Data type: LFB1Optional: No
Call by Reference: No ( called with pass by value option)
LFBK_IN -
Data type: LFBKOptional: No
Call by Reference: No ( called with pass by value option)
TXTUSR -
Data type: RJGF01-TXTUSROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLJG21_108
BDCDATA -
Data type: BDCDATAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLJG21_108 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: | ||||
| lt_bdcdata | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lv_lfa1_in | TYPE LFA1, " | |||
| lv_lfb1_in | TYPE LFB1, " | |||
| lv_lfbk_in | TYPE LFBK, " | |||
| lv_txtusr | TYPE RJGF01-TXTUSR. " |
|   CALL FUNCTION 'EXIT_SAPLJG21_108' "Synchronization of R/3 (IS-M) with R/3 (FI) External System via RFC |
| EXPORTING | ||
| LFA1_IN | = lv_lfa1_in | |
| LFB1_IN | = lv_lfb1_in | |
| LFBK_IN | = lv_lfbk_in | |
| TXTUSR | = lv_txtusr | |
| TABLES | ||
| BDCDATA | = lt_bdcdata | |
| . " EXIT_SAPLJG21_108 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJG21_108
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 TXTUSR FROM RJGF01 INTO @DATA(ld_txtusr). | ||||
Search for further information about these or an SAP related objects