SAP ISP_POST_LIST_READ Function Module for
ISP_POST_LIST_READ is a standard isp post list read 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 isp post list read FM, simply by entering the name ISP_POST_LIST_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: JS04
Program Name: SAPLJS04
Main Program: SAPLJS04
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_POST_LIST_READ 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 'ISP_POST_LIST_READ'".
EXPORTING
* AENDERUNGSNR = ' ' "
* ZIELZUORDTYP = CON_POSTHIE "
* STARTZUORDTYP = ' ' "
AUSGABE_KNOTENART = "
* GUELTIGAB = CON_TIME_ZERO "
* GUELTIGBIS = CON_TIME_INFINITY "
KNOTEN = "
KNOTENART = "
UMFAKT = "
XINKL_STRUKTUR = "
XSORT = "
TABLES
BEZEICH_TAB = "
ZEITSCHEIBE_TAB = "
EXCEPTIONS
NOT_FOUND = 1 NO_STRUCTURE = 2
IMPORTING Parameters details for ISP_POST_LIST_READ
AENDERUNGSNR -
Data type: JSTAENDERDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
ZIELZUORDTYP -
Data type: RJS0102-ZUORDTYPDefault: CON_POSTHIE
Optional: Yes
Call by Reference: No ( called with pass by value option)
STARTZUORDTYP -
Data type: RJS0102-ZUORDTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
AUSGABE_KNOTENART -
Data type: RJS0104-STRUKNOARTOptional: No
Call by Reference: No ( called with pass by value option)
GUELTIGAB -
Data type: RJS0102-GUELTIGABDefault: CON_TIME_ZERO
Optional: Yes
Call by Reference: No ( called with pass by value option)
GUELTIGBIS -
Data type: RJS0102-GUELTIGBISDefault: CON_TIME_INFINITY
Optional: Yes
Call by Reference: No ( called with pass by value option)
KNOTEN -
Data type: RJS0104-STRUKNOTENOptional: No
Call by Reference: No ( called with pass by value option)
KNOTENART -
Data type: RJS0104-STRUKNOARTOptional: No
Call by Reference: No ( called with pass by value option)
UMFAKT -
Data type: RJS0101-STRUUMFAKTOptional: No
Call by Reference: No ( called with pass by value option)
XINKL_STRUKTUR -
Data type: RJS0102-XSTRUAKTIVOptional: No
Call by Reference: No ( called with pass by value option)
XSORT -
Data type: RJS0102-XSTRUAKTIVOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_POST_LIST_READ
BEZEICH_TAB -
Data type: RJS0401Optional: No
Call by Reference: No ( called with pass by value option)
ZEITSCHEIBE_TAB -
Data type: RJS0802Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_STRUCTURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_POST_LIST_READ 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_not_found | TYPE STRING, " | |||
| lt_bezeich_tab | TYPE STANDARD TABLE OF RJS0401, " | |||
| lv_aenderungsnr | TYPE JSTAENDER, " ' ' | |||
| lv_zielzuordtyp | TYPE RJS0102-ZUORDTYP, " CON_POSTHIE | |||
| lv_startzuordtyp | TYPE RJS0102-ZUORDTYP, " SPACE | |||
| lv_no_structure | TYPE RJS0102, " | |||
| lt_zeitscheibe_tab | TYPE STANDARD TABLE OF RJS0802, " | |||
| lv_ausgabe_knotenart | TYPE RJS0104-STRUKNOART, " | |||
| lv_gueltigab | TYPE RJS0102-GUELTIGAB, " CON_TIME_ZERO | |||
| lv_gueltigbis | TYPE RJS0102-GUELTIGBIS, " CON_TIME_INFINITY | |||
| lv_knoten | TYPE RJS0104-STRUKNOTEN, " | |||
| lv_knotenart | TYPE RJS0104-STRUKNOART, " | |||
| lv_umfakt | TYPE RJS0101-STRUUMFAKT, " | |||
| lv_xinkl_struktur | TYPE RJS0102-XSTRUAKTIV, " | |||
| lv_xsort | TYPE RJS0102-XSTRUAKTIV. " |
|   CALL FUNCTION 'ISP_POST_LIST_READ' " |
| EXPORTING | ||
| AENDERUNGSNR | = lv_aenderungsnr | |
| ZIELZUORDTYP | = lv_zielzuordtyp | |
| STARTZUORDTYP | = lv_startzuordtyp | |
| AUSGABE_KNOTENART | = lv_ausgabe_knotenart | |
| GUELTIGAB | = lv_gueltigab | |
| GUELTIGBIS | = lv_gueltigbis | |
| KNOTEN | = lv_knoten | |
| KNOTENART | = lv_knotenart | |
| UMFAKT | = lv_umfakt | |
| XINKL_STRUKTUR | = lv_xinkl_struktur | |
| XSORT | = lv_xsort | |
| TABLES | ||
| BEZEICH_TAB | = lt_bezeich_tab | |
| ZEITSCHEIBE_TAB | = lt_zeitscheibe_tab | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NO_STRUCTURE = 2 | ||
| . " ISP_POST_LIST_READ | ||
ABAP code using 7.40 inline data declarations to call FM ISP_POST_LIST_READ
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.| DATA(ld_aenderungsnr) | = ' '. | |||
| "SELECT single ZUORDTYP FROM RJS0102 INTO @DATA(ld_zielzuordtyp). | ||||
| DATA(ld_zielzuordtyp) | = CON_POSTHIE. | |||
| "SELECT single ZUORDTYP FROM RJS0102 INTO @DATA(ld_startzuordtyp). | ||||
| DATA(ld_startzuordtyp) | = ' '. | |||
| "SELECT single STRUKNOART FROM RJS0104 INTO @DATA(ld_ausgabe_knotenart). | ||||
| "SELECT single GUELTIGAB FROM RJS0102 INTO @DATA(ld_gueltigab). | ||||
| DATA(ld_gueltigab) | = CON_TIME_ZERO. | |||
| "SELECT single GUELTIGBIS FROM RJS0102 INTO @DATA(ld_gueltigbis). | ||||
| DATA(ld_gueltigbis) | = CON_TIME_INFINITY. | |||
| "SELECT single STRUKNOTEN FROM RJS0104 INTO @DATA(ld_knoten). | ||||
| "SELECT single STRUKNOART FROM RJS0104 INTO @DATA(ld_knotenart). | ||||
| "SELECT single STRUUMFAKT FROM RJS0101 INTO @DATA(ld_umfakt). | ||||
| "SELECT single XSTRUAKTIV FROM RJS0102 INTO @DATA(ld_xinkl_struktur). | ||||
| "SELECT single XSTRUAKTIV FROM RJS0102 INTO @DATA(ld_xsort). | ||||
Search for further information about these or an SAP related objects