SAP BAPI_REQUIREMENT_CREATE Function Module for Create Requirement Coverage Request









BAPI_REQUIREMENT_CREATE is a standard bapi requirement create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Requirement Coverage Request 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 create FM, simply by entering the name BAPI_REQUIREMENT_CREATE 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_CREATE 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_CREATE'"Create Requirement Coverage Request
 IMPORTING
   NUMBER =  "Number of Requirement Coverage Request
   ITEM =  "Item Number

TABLES
   REQUIREMENT_ITEMS =  "Item Data of Requirement Coverage Request
*  REQUIREMENT_ACCOUNT_ASSIGNMENT =  "Account Assignment Data of Requirement Coverage Request
*  REQUIREMENT_ITEM_TEXT =  "Text Lines for Requirement Coverage Request
   RETURN =  "Error Log

EXCEPTIONS
   NO_OBJECT_ID = 1
.




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

EXPORTING Parameters details for BAPI_REQUIREMENT_CREATE

NUMBER - Number of Requirement Coverage Request

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

ITEM - Item Number

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

TABLES Parameters details for BAPI_REQUIREMENT_CREATE

REQUIREMENT_ITEMS - Item Data of Requirement Coverage Request

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

REQUIREMENT_ACCOUNT_ASSIGNMENT - Account Assignment Data of Requirement Coverage Request

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

REQUIREMENT_ITEM_TEXT - Text Lines for Requirement Coverage Request

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

RETURN - Error Log

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

EXCEPTIONS details

NO_OBJECT_ID - Not Possible to Assign a Number

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

Copy and paste ABAP code example for BAPI_REQUIREMENT_CREATE 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_number  TYPE BAPIEBAN-PREQ_NO, "   
lv_no_object_id  TYPE BAPIEBAN, "   
lt_requirement_items  TYPE STANDARD TABLE OF BAPIEBAN, "   
lv_item  TYPE BAPIEBAN-PREQ_ITEM, "   
lt_requirement_account_assignment  TYPE STANDARD TABLE OF BAPIEBKN, "   
lt_requirement_item_text  TYPE STANDARD TABLE OF BAPIEBANTX, "   
lt_return  TYPE STANDARD TABLE OF BAPIERRORS. "   

  CALL FUNCTION 'BAPI_REQUIREMENT_CREATE'  "Create Requirement Coverage Request
    IMPORTING
         NUMBER = lv_number
         ITEM = lv_item
    TABLES
         REQUIREMENT_ITEMS = lt_requirement_items
         REQUIREMENT_ACCOUNT_ASSIGNMENT = lt_requirement_account_assignment
         REQUIREMENT_ITEM_TEXT = lt_requirement_item_text
         RETURN = lt_return
    EXCEPTIONS
        NO_OBJECT_ID = 1
. " BAPI_REQUIREMENT_CREATE




ABAP code using 7.40 inline data declarations to call FM BAPI_REQUIREMENT_CREATE

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_NO FROM BAPIEBAN INTO @DATA(ld_number).
 
 
 
"SELECT single PREQ_ITEM FROM BAPIEBAN INTO @DATA(ld_item).
 
 
 
 


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!