SAP BAPI_REQUIREMENT_GET_LIST Function Module for List Requirement Coverage Requests/Requisitions









BAPI_REQUIREMENT_GET_LIST is a standard bapi requirement get list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for List Requirement Coverage Requests/Requisitions 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 requirement get list FM, simply by entering the name BAPI_REQUIREMENT_GET_LIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: MEWR
Program Name: SAPLMEWR
Main Program: SAPLMEWR
Appliation area: M
Release date: 17-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_REQUIREMENT_GET_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 'BAPI_REQUIREMENT_GET_LIST'"List Requirement Coverage Requests/Requisitions
  EXPORTING
*  PREQ_NAME =  "Name of Requisitioner (Requester)/Entering User
*  PREQ_DATE =  "Requisition/Request Date
*  OPEN_ITEMS =  "Indicator: Open Requirement Coverage Requests Only
*  CLOSED_ITEMS =  "Indicator: Closed Requirement Coverage Requests Only
*  REL_GROUP =  "Release Group for Collective Release
*  REL_CODE =  "Release Code for Collective Release
*  ITEMS_FOR_RELEASE = 'X' "Indicator: Purchase Requisitions Awaiting Release Only

TABLES
   REQUIREMENT_ITEMS =  "Table of Requirement Coverage Requests/Purchase Requisitions

EXCEPTIONS
   PREQ_NAME_MISSING = 1    STATUS_MISSING = 2    REL_CODE_MISSING = 3    REL_AUTH_CHECK_FAILED = 4
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMEWR_001 User Exit for Data of Requirement

IMPORTING Parameters details for BAPI_REQUIREMENT_GET_LIST

PREQ_NAME - Name of Requisitioner (Requester)/Entering User

Data type: BAPIMMPARA-PREQ_NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

PREQ_DATE - Requisition/Request Date

Data type: BAPIMMPARA-PREQ_DATE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OPEN_ITEMS - Indicator: Open Requirement Coverage Requests Only

Data type: BAPIMMPARA-SELECTION
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLOSED_ITEMS - Indicator: Closed Requirement Coverage Requests Only

Data type: BAPIMMPARA-SELECTION
Optional: Yes
Call by Reference: No ( called with pass by value option)

REL_GROUP - Release Group for Collective Release

Data type: BAPIMMPARA-REL_GROUP
Optional: Yes
Call by Reference: No ( called with pass by value option)

REL_CODE - Release Code for Collective Release

Data type: BAPIMMPARA-REL_CODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ITEMS_FOR_RELEASE - Indicator: Purchase Requisitions Awaiting Release Only

Data type: BAPIMMPARA-SELECTION
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_REQUIREMENT_GET_LIST

REQUIREMENT_ITEMS - Table of Requirement Coverage Requests/Purchase Requisitions

Data type: BAPIEBAN
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

PREQ_NAME_MISSING - Requester Missing from Status Display

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

STATUS_MISSING - Open/Closed Indicator Missing from Status Display

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

REL_CODE_MISSING - Release Code Missing

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

REL_AUTH_CHECK_FAILED - No Release Authorization

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_REQUIREMENT_GET_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_preq_name  TYPE BAPIMMPARA-PREQ_NAME, "   
lv_preq_name_missing  TYPE BAPIMMPARA, "   
lt_requirement_items  TYPE STANDARD TABLE OF BAPIEBAN, "   
lv_preq_date  TYPE BAPIMMPARA-PREQ_DATE, "   
lv_status_missing  TYPE BAPIMMPARA, "   
lv_open_items  TYPE BAPIMMPARA-SELECTION, "   
lv_rel_code_missing  TYPE BAPIMMPARA, "   
lv_closed_items  TYPE BAPIMMPARA-SELECTION, "   
lv_rel_auth_check_failed  TYPE BAPIMMPARA, "   
lv_rel_group  TYPE BAPIMMPARA-REL_GROUP, "   
lv_rel_code  TYPE BAPIMMPARA-REL_CODE, "   
lv_items_for_release  TYPE BAPIMMPARA-SELECTION. "   'X'

  CALL FUNCTION 'BAPI_REQUIREMENT_GET_LIST'  "List Requirement Coverage Requests/Requisitions
    EXPORTING
         PREQ_NAME = lv_preq_name
         PREQ_DATE = lv_preq_date
         OPEN_ITEMS = lv_open_items
         CLOSED_ITEMS = lv_closed_items
         REL_GROUP = lv_rel_group
         REL_CODE = lv_rel_code
         ITEMS_FOR_RELEASE = lv_items_for_release
    TABLES
         REQUIREMENT_ITEMS = lt_requirement_items
    EXCEPTIONS
        PREQ_NAME_MISSING = 1
        STATUS_MISSING = 2
        REL_CODE_MISSING = 3
        REL_AUTH_CHECK_FAILED = 4
. " BAPI_REQUIREMENT_GET_LIST




ABAP code using 7.40 inline data declarations to call FM BAPI_REQUIREMENT_GET_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 PREQ_NAME FROM BAPIMMPARA INTO @DATA(ld_preq_name).
 
 
 
"SELECT single PREQ_DATE FROM BAPIMMPARA INTO @DATA(ld_preq_date).
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_open_items).
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_closed_items).
 
 
"SELECT single REL_GROUP FROM BAPIMMPARA INTO @DATA(ld_rel_group).
 
"SELECT single REL_CODE FROM BAPIMMPARA INTO @DATA(ld_rel_code).
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_items_for_release).
DATA(ld_items_for_release) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!