SAP EXIT_SAPLJF80_300 Function Module for IS-M/SD: User Fields for Screen 300 - Revenue Dist. IS-M/SD -> FI









EXIT_SAPLJF80_300 is a standard exit sapljf80 300 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 Fields for Screen 300 - Revenue Dist. IS-M/SD -> FI 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 sapljf80 300 FM, simply by entering the name EXIT_SAPLJF80_300 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XJF3
Program Name: SAPLXJF3
Main Program: SAPLXJF3
Appliation area: J
Release date: 01-Aug-1995
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EXIT_SAPLJF80_300 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_SAPLJF80_300'"IS-M/SD: User Fields for Screen 300 - Revenue Dist. IS-M/SD -> FI
EXPORTING
*XBPOS = "Posting data current line + 1
MWSKZ = "VAT registration number
XBPOS = "Posting data current line

TABLES
BDC = "Batch input table
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISP_FI_CLEARING_DOCUMENT
ISP_FI_DOCUMENT_ADD_BTCI
ISP_FI_DOCUMENT_ADD_CALL
ISP_FI_JOURNAL
ISP_RECURRING_ENTRY_FUTUR_BDC
ISP_RECURRING_ENTRY_FUTUR_CAL
ISP_REVENUE_POSTING_PAST_BDC
ISP_REVENUE_POSTING_PAST_CAL

IMPORTING Parameters details for EXIT_SAPLJF80_300

*XBPOS - Posting data current line + 1

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

MWSKZ - VAT registration number

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

XBPOS - Posting data current line

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

TABLES Parameters details for EXIT_SAPLJF80_300

BDC - Batch input table

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

Copy and paste ABAP code example for EXIT_SAPLJF80_300 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_bdc  TYPE STANDARD TABLE OF BDCDATA, "   
lv_*xbpos  TYPE JYPSDFI, "   
lv_mwskz  TYPE BSEG-MWSKZ, "   
lv_xbpos  TYPE JYPSDFI. "   

  CALL FUNCTION 'EXIT_SAPLJF80_300'  "IS-M/SD: User Fields for Screen 300 - Revenue Dist. IS-M/SD -> FI
    EXPORTING
         XBPOS = lv_ xbpos
         MWSKZ = lv_mwskz
         XBPOS = lv_xbpos
    TABLES
         BDC = lt_bdc
. " EXIT_SAPLJF80_300




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJF80_300

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 MWSKZ FROM BSEG INTO @DATA(ld_mwskz).
 
 


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!