SAP BAPI_KANBAN_GETLIST Function Module for Determination of Kanbans Matching Selection Criteria
BAPI_KANBAN_GETLIST is a standard bapi kanban getlist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determination of Kanbans Matching Selection Criteria 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 bapi kanban getlist FM, simply by entering the name BAPI_KANBAN_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: MPKW
Program Name: SAPLMPKW
Main Program: SAPLMPKW
Appliation area: M
Release date: 01-Dec-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_KANBAN_GETLIST 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 'BAPI_KANBAN_GETLIST'"Determination of Kanbans Matching Selection Criteria.
EXPORTING
* MAXROWS = 500 "Maximum Number of Data Records Read
IMPORTING
RETURN = "Message if Function not Possible
TABLES
* KANBANIDRANGE = "Selection Table for Kanban Identification Number
* KANBANCONTROLCYCLERANGE = "Selection Table for Control Cycle Number
* KANBANNUMBERRANGE = "Selection Table for Kanban Number
* STATUSRANGE = "Selection table for the Status of a Kanban
* STATUSDATERANGE = "Selection Table for Date of Status Change
* STATUSTIMERANGE = "Selection Table for the Time of Status Change
KANBANLIST = "List of Kanbans
IMPORTING Parameters details for BAPI_KANBAN_GETLIST
MAXROWS - Maximum Number of Data Records Read
Data type: BAPI1075_GENERAL-MAXROWSDefault: 500
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_KANBAN_GETLIST
RETURN - Message if Function not Possible
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_KANBAN_GETLIST
KANBANIDRANGE - Selection Table for Kanban Identification Number
Data type: BAPI1075_PKKEY_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
KANBANCONTROLCYCLERANGE - Selection Table for Control Cycle Number
Data type: BAPI1172_PKNUM_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
KANBANNUMBERRANGE - Selection Table for Kanban Number
Data type: BAPI1075_PKPOS_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUSRANGE - Selection table for the Status of a Kanban
Data type: BAPI1075_PKBST_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUSDATERANGE - Selection Table for Date of Status Change
Data type: BAPI1075_SAEDT_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUSTIMERANGE - Selection Table for the Time of Status Change
Data type: BAPI1075_SAEUZ_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
KANBANLIST - List of Kanbans
Data type: BAPI1075_LISTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_KANBAN_GETLIST 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_return | TYPE BAPIRET2, " | |||
| lv_maxrows | TYPE BAPI1075_GENERAL-MAXROWS, " 500 | |||
| lt_kanbanidrange | TYPE STANDARD TABLE OF BAPI1075_PKKEY_RANGE, " | |||
| lt_kanbancontrolcyclerange | TYPE STANDARD TABLE OF BAPI1172_PKNUM_RANGE, " | |||
| lt_kanbannumberrange | TYPE STANDARD TABLE OF BAPI1075_PKPOS_RANGE, " | |||
| lt_statusrange | TYPE STANDARD TABLE OF BAPI1075_PKBST_RANGE, " | |||
| lt_statusdaterange | TYPE STANDARD TABLE OF BAPI1075_SAEDT_RANGE, " | |||
| lt_statustimerange | TYPE STANDARD TABLE OF BAPI1075_SAEUZ_RANGE, " | |||
| lt_kanbanlist | TYPE STANDARD TABLE OF BAPI1075_LIST. " |
|   CALL FUNCTION 'BAPI_KANBAN_GETLIST' "Determination of Kanbans Matching Selection Criteria |
| EXPORTING | ||
| MAXROWS | = lv_maxrows | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| KANBANIDRANGE | = lt_kanbanidrange | |
| KANBANCONTROLCYCLERANGE | = lt_kanbancontrolcyclerange | |
| KANBANNUMBERRANGE | = lt_kanbannumberrange | |
| STATUSRANGE | = lt_statusrange | |
| STATUSDATERANGE | = lt_statusdaterange | |
| STATUSTIMERANGE | = lt_statustimerange | |
| KANBANLIST | = lt_kanbanlist | |
| . " BAPI_KANBAN_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_KANBAN_GETLIST
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 MAXROWS FROM BAPI1075_GENERAL INTO @DATA(ld_maxrows). | ||||
| DATA(ld_maxrows) | = 500. | |||
Search for further information about these or an SAP related objects