SAP BAPI_SALESADDIREQ_GET_PUR_LIST Function Module for Additionals Purchase Orders for an Additionals Vendor
BAPI_SALESADDIREQ_GET_PUR_LIST is a standard bapi salesaddireq get pur 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 Additionals Purchase Orders for an Additionals Vendor 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 salesaddireq get pur list FM, simply by entering the name BAPI_SALESADDIREQ_GET_PUR_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2106
Program Name: SAPL2106
Main Program: SAPL2106
Appliation area: W
Release date: 12-Apr-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SALESADDIREQ_GET_PUR_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_SALESADDIREQ_GET_PUR_LIST'"Additionals Purchase Orders for an Additionals Vendor.
EXPORTING
ADDIVENDOR = "Additionals Vendor
DATEFROM = "Start Date for Purchase Order Run
DATETO = "End Date for Purchase Order Run
IMPORTING
RETURN = "Message about Processing Status
TABLES
ADDIORDERINFO = "Information about Purchase Orders
IMPORTING Parameters details for BAPI_SALESADDIREQ_GET_PUR_LIST
ADDIVENDOR - Additionals Vendor
Data type: BAPI2106POL-ADDI_SUPPLIEROptional: No
Call by Reference: No ( called with pass by value option)
DATEFROM - Start Date for Purchase Order Run
Data type: BAPI2106POL-DATEFROMOptional: No
Call by Reference: No ( called with pass by value option)
DATETO - End Date for Purchase Order Run
Data type: BAPI2106POL-DATEUNTILOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_SALESADDIREQ_GET_PUR_LIST
RETURN - Message about Processing Status
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_SALESADDIREQ_GET_PUR_LIST
ADDIORDERINFO - Information about Purchase Orders
Data type: BAPI2106COptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_SALESADDIREQ_GET_PUR_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_return | TYPE BAPIRET2, " | |||
| lv_addivendor | TYPE BAPI2106POL-ADDI_SUPPLIER, " | |||
| lt_addiorderinfo | TYPE STANDARD TABLE OF BAPI2106C, " | |||
| lv_datefrom | TYPE BAPI2106POL-DATEFROM, " | |||
| lv_dateto | TYPE BAPI2106POL-DATEUNTIL. " |
|   CALL FUNCTION 'BAPI_SALESADDIREQ_GET_PUR_LIST' "Additionals Purchase Orders for an Additionals Vendor |
| EXPORTING | ||
| ADDIVENDOR | = lv_addivendor | |
| DATEFROM | = lv_datefrom | |
| DATETO | = lv_dateto | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| ADDIORDERINFO | = lt_addiorderinfo | |
| . " BAPI_SALESADDIREQ_GET_PUR_LIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_SALESADDIREQ_GET_PUR_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 ADDI_SUPPLIER FROM BAPI2106POL INTO @DATA(ld_addivendor). | ||||
| "SELECT single DATEFROM FROM BAPI2106POL INTO @DATA(ld_datefrom). | ||||
| "SELECT single DATEUNTIL FROM BAPI2106POL INTO @DATA(ld_dateto). | ||||
Search for further information about these or an SAP related objects