SAP EXIT_SAPLJG20_003 Function Module for IS-M/SD: User Exit for BP Transfer R/3 -> R/2 for Additional Field









EXIT_SAPLJG20_003 is a standard exit sapljg20 003 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: User Exit for BP Transfer R/3 -> R/2 for Additional Field 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 sapljg20 003 FM, simply by entering the name EXIT_SAPLJG20_003 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XJG1
Program Name: SAPLXJG1
Main Program: SAPLXJG1
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EXIT_SAPLJG20_003 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_SAPLJG20_003'"IS-M/SD: User Exit for BP Transfer R/3 -> R/2 for Additional Field
  EXPORTING
   JGTSADR_IN =  "Address
   JGTGPNR_IN =  "Business Partner
   LFA1_IN =  "Vendor A Segment
   LFB1_IN =  "Vendor B Segment

 IMPORTING
   TXTUSR_OUT =  "50 Character Text Field
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISP_BANK_FSYS_PREPARE_DEBITOR IS-M/SD: Prepare Synchronization of Customer Bank Data
ISP_BANK_FSYS_PREPARE_KREDITOR IS-M/SD: Prepare Synchronization of Vendor Bank Data
ISP_BANK_FSYS_SYNCHRONISATION IS-M/SD: Synchronize Bank Data
ISP_DEBITOR_FSYS_INSERT_TABLE IS-M: Synchronization of Non-SAP System: Customer Tables
ISP_DEBITOR_FSYS_MAINTAIN IS-M: Synchronization of Non-SAP System: Customer
ISP_DEBITOR_SYSTEM_CHECK IS-M: Determine Customer Number for Specific System
ISP_KREDITOR_FSYS_INSERT_TABLE IS-M: Synchronization for Non-SAP System: Vendor Tables
ISP_KREDITOR_FSYS_MAINTAIN IS-M: Synchronization for Non-SAP System: Vendor
ISP_KREDITOR_SYSTEM_CHECK IS-M: Determine Vendor Number According to System
ISP_MAHNDATEN_AUFBAU IS-M: Generate Dunning Data (KNB5) from Non-SAP FI System to IS-M

IMPORTING Parameters details for EXIT_SAPLJG20_003

JGTSADR_IN - Address

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

JGTGPNR_IN - Business Partner

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

LFA1_IN - Vendor A Segment

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

LFB1_IN - Vendor B Segment

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

EXPORTING Parameters details for EXIT_SAPLJG20_003

TXTUSR_OUT - 50 Character Text Field

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

Copy and paste ABAP code example for EXIT_SAPLJG20_003 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_jgtsadr_in  TYPE JGTSADR, "   
lv_txtusr_out  TYPE RJGF01-TXTUSR, "   
lv_jgtgpnr_in  TYPE JGTGPNR, "   
lv_lfa1_in  TYPE LFA1, "   
lv_lfb1_in  TYPE LFB1. "   

  CALL FUNCTION 'EXIT_SAPLJG20_003'  "IS-M/SD: User Exit for BP Transfer R/3 -> R/2 for Additional Field
    EXPORTING
         JGTSADR_IN = lv_jgtsadr_in
         JGTGPNR_IN = lv_jgtgpnr_in
         LFA1_IN = lv_lfa1_in
         LFB1_IN = lv_lfb1_in
    IMPORTING
         TXTUSR_OUT = lv_txtusr_out
. " EXIT_SAPLJG20_003




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJG20_003

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_out).
 
 
 
 


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!