SAP EXIT_SAPMJ59A_001 Function Module for IS-M/SD: User Exit for Settlement
EXIT_SAPMJ59A_001 is a standard exit sapmj59a 001 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 Settlement 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 sapmj59a 001 FM, simply by entering the name EXIT_SAPMJ59A_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJL1
Program Name: SAPLXJL1
Main Program: SAPLXJL1
Appliation area: J
Release date: 02-Jun-1995
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMJ59A_001 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_SAPMJ59A_001'"IS-M/SD: User Exit for Settlement.
EXPORTING
XJLRK = "
XJLRP = "
XRJ59A = "
CHANGING
XLOOP2 = "
IMPORTING Parameters details for EXIT_SAPMJ59A_001
XJLRK -
Data type: JLRKVBOptional: No
Call by Reference: No ( called with pass by value option)
XJLRP -
Data type: JLRPVBOptional: No
Call by Reference: No ( called with pass by value option)
XRJ59A -
Data type: RJ59AOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPMJ59A_001
XLOOP2 -
Data type: RJ59A-LOOP2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMJ59A_001 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_xjlrk | TYPE JLRKVB, " | |||
lv_xloop2 | TYPE RJ59A-LOOP2, " | |||
lv_xjlrp | TYPE JLRPVB, " | |||
lv_xrj59a | TYPE RJ59A. " |
  CALL FUNCTION 'EXIT_SAPMJ59A_001' "IS-M/SD: User Exit for Settlement |
EXPORTING | ||
XJLRK | = lv_xjlrk | |
XJLRP | = lv_xjlrp | |
XRJ59A | = lv_xrj59a | |
CHANGING | ||
XLOOP2 | = lv_xloop2 | |
. " EXIT_SAPMJ59A_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMJ59A_001
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 LOOP2 FROM RJ59A INTO @DATA(ld_xloop2). | ||||
Search for further information about these or an SAP related objects