SAP ISM_SETTLEMENT_LIST Function Module for
ISM_SETTLEMENT_LIST is a standard ism settlement list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ism settlement list FM, simply by entering the name ISM_SETTLEMENT_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: JF20
Program Name: SAPLJF20
Main Program: SAPLJF20
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_SETTLEMENT_LIST 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 'ISM_SETTLEMENT_LIST'".
EXPORTING
I_VARIANT = "
* I_SAMMG = "
TABLES
I_JLRK_TAB = "
IMPORTING Parameters details for ISM_SETTLEMENT_LIST
I_VARIANT -
Data type: DISVARIANTOptional: No
Call by Reference: No ( called with pass by value option)
I_SAMMG -
Data type: JFSK-SAMMGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISM_SETTLEMENT_LIST
I_JLRK_TAB -
Data type: JF23_JLRK_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_SETTLEMENT_LIST 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_i_variant | TYPE DISVARIANT, " | |||
| lt_i_jlrk_tab | TYPE STANDARD TABLE OF JF23_JLRK_TAB, " | |||
| lv_i_sammg | TYPE JFSK-SAMMG. " |
|   CALL FUNCTION 'ISM_SETTLEMENT_LIST' " |
| EXPORTING | ||
| I_VARIANT | = lv_i_variant | |
| I_SAMMG | = lv_i_sammg | |
| TABLES | ||
| I_JLRK_TAB | = lt_i_jlrk_tab | |
| . " ISM_SETTLEMENT_LIST | ||
ABAP code using 7.40 inline data declarations to call FM ISM_SETTLEMENT_LIST
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 SAMMG FROM JFSK INTO @DATA(ld_i_sammg). | ||||
Search for further information about these or an SAP related objects