SAP READ_KPEP_WL_S Function Module for Access to Table KPEP_WL_S
READ_KPEP_WL_S is a standard read kpep wl s SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Access to Table KPEP_WL_S 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 read kpep wl s FM, simply by entering the name READ_KPEP_WL_S into the relevant SAP transaction such as SE37 or SE38.
Function Group: KPEP_WL_DB_ACCESS
Program Name: SAPLKPEP_WL_DB_ACCESS
Main Program: SAPLKPEP_WL_DB_ACCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function READ_KPEP_WL_S 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 'READ_KPEP_WL_S'"Access to Table KPEP_WL_S.
EXPORTING
WORKLIST = "
IMPORTING
KPEP_WL_S = "
EXCEPTIONS
WORKLIST_NOT_FOUND = 1
IMPORTING Parameters details for READ_KPEP_WL_S
WORKLIST -
Data type: KPEP_WL_WORKLISTIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for READ_KPEP_WL_S
KPEP_WL_S -
Data type: KPEP_WL_S_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
WORKLIST_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for READ_KPEP_WL_S 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_worklist | TYPE KPEP_WL_WORKLISTID, " | |||
| lv_kpep_wl_s | TYPE KPEP_WL_S_TAB, " | |||
| lv_worklist_not_found | TYPE KPEP_WL_S_TAB. " |
|   CALL FUNCTION 'READ_KPEP_WL_S' "Access to Table KPEP_WL_S |
| EXPORTING | ||
| WORKLIST | = lv_worklist | |
| IMPORTING | ||
| KPEP_WL_S | = lv_kpep_wl_s | |
| EXCEPTIONS | ||
| WORKLIST_NOT_FOUND = 1 | ||
| . " READ_KPEP_WL_S | ||
ABAP code using 7.40 inline data declarations to call FM READ_KPEP_WL_S
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