SAP EXIT_SAPLJ1AT_002 Function Module for User exit of report J_1AF105 at GET BSEG

Search SAP Function Modules

EXIT_SAPLJ1AT_002 is a standard exit saplj1at 002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User exit of report J_1AF105 at GET BSEG 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 saplj1at 002 FM, simply by entering the name EXIT_SAPLJ1AT_002 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XJ1A
Program Name: SAPLXJ1A
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLJ1AT_002 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_SAPLJ1AT_002'"User exit of report J_1AF105 at GET BSEG
  EXPORTING
   I_BKPF =  "
   I_BSEG =  "

 IMPORTING
   E_RCODE =  "

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
F4_TAXCODE_USER_EXIT NOTRANSL: F4 auf MWSKZ: Exit zur Ausgabe der Steuerkategoriedaten für Arge
FI_TAX_INPUT_CHECK NOTRANSL: Erweiterte Hilfe zur Bestimmung von Steuerkennzeichen (nutze Ste
FI_TAX_MINIMUM_CHECK NOTRANSL: Final checks on document level - minimum and GI (MM- and FI-invo
J_1A_CHANGES_KNAT_MF02D NOTRANSL: Check, if something changed in table KNAT
J_1A_CHANGES_LFAT_MF02K NOTRANSL: Check, if something changed in table LFAT
J_1A_COMPARE_KNAT_MF02D NOTRANSL: Indicate the new, old and deleted entries of table KNAT
J_1A_COMPARE_LFAT_MF02K NOTRANSL: Indicate the new, old and deleted entries of table LFAT
J_1A_EXIT_J_1AF105 NOTRANSL: User-Exit für Report J_1AF105
J_1A_EXIT_J_1AF106 NOTRANSL: User-Exit für Report J_1AF106
J_1A_EXIT_J_1AF217 NOTRANSL: User exit for J_1AF217
J_1A_GET_OLD_STATUS_LFAT_MF02K NOTRANSL: Nachlesen Originalzustand Tabelle LFAT vor Änderung
J_1A_HELP_KTOSL NOTRANSL: Help on the tax processing key (restricted list in popup with te
J_1A_HELP_REGION NOTRANSL: Help on the tax processing key (restricted list in popup with te
J_1A_PUT_DASHES_TO_STCD2 NOTRANSL: Put the dashes to the tax number field STCD2 (Gross Income no.)
J_1A_PUT_DASHES_TO_STCD3 NOTRANSL: Put the dashes to the tax number field STCD3 (Gross Income no.)
J_1A_READ_KNAT NOTRANSL: Reading the customer master tax categories for one customer
J_1A_READ_LFAT NOTRANSL: Reading the vendor master tax categories for one vendor
J_1A_READ_PERCEPTION NOTRANSL: Read data for calculation of VAT or GI Perceptions
J_1A_READ_T001TC NOTRANSL: Reading the company master tax categories per cc and account typ
J_1A_READ_T007C NOTRANSL: Reading the tax category definition
J_1A_READ_TXMIN NOTRANSL: Reading the minimums for the coutry of the cc by a certain date
J_1A_RESET_TAX_CHECK NOTRANSL: Reseting of global field for displaying final warnings on docume
J_1A_TAX_PROCESSING NOTRANSL: Tax-processing, creating warnings on tax-groups

IMPORTING Parameters details for EXIT_SAPLJ1AT_002

I_BKPF -

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

I_BSEG -

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

EXPORTING Parameters details for EXIT_SAPLJ1AT_002

E_RCODE -

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

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

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