SAP BBP_ORDER_GETLIST Function Module for NOTRANSL: Liste aller Aufträgen
BBP_ORDER_GETLIST is a standard bbp order 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 NOTRANSL: Liste aller Aufträgen 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 bbp order getlist FM, simply by entering the name BBP_ORDER_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBPC
Program Name: SAPLBBPC
Main Program: SAPLBBPC
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_ORDER_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 'BBP_ORDER_GETLIST'"NOTRANSL: Liste aller Aufträgen.
EXPORTING
* CONTROLLING_AREA = "Controlling Area
* RESP_COST_CENTER = "Responsible Cost Center
* ORDER_TYPE = "Order Type
* ORDER = "Order Number (Single Value or Lower Limit)
* ORDER_TO = "Order Number (Upper Limit)
* ORDER_EXTERNAL_NO = "External Order Number (Single Value or Lower Limit)
* ORDER_EXTERNAL_NO_TO = "External Order Number (Upper Limit)
IMPORTING
RETURN = "Structure with Return Information
TABLES
* ORDER_LIST = "List of Selected Orders
IMPORTING Parameters details for BBP_ORDER_GETLIST
CONTROLLING_AREA - Controlling Area
Data type: BAPI2075_2-CO_AREAOptional: Yes
Call by Reference: No ( called with pass by value option)
RESP_COST_CENTER - Responsible Cost Center
Data type: BAPI2075_2-RESPCCTROptional: Yes
Call by Reference: No ( called with pass by value option)
ORDER_TYPE - Order Type
Data type: BAPI2075_2-ORDER_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
ORDER - Order Number (Single Value or Lower Limit)
Data type: BAPI2075_2-ORDEROptional: Yes
Call by Reference: No ( called with pass by value option)
ORDER_TO - Order Number (Upper Limit)
Data type: BAPI2075_2-ORDEROptional: Yes
Call by Reference: No ( called with pass by value option)
ORDER_EXTERNAL_NO - External Order Number (Single Value or Lower Limit)
Data type: BAPI2075_2-EXT_ORD_NOOptional: Yes
Call by Reference: No ( called with pass by value option)
ORDER_EXTERNAL_NO_TO - External Order Number (Upper Limit)
Data type: BAPI2075_2-EXT_ORD_NOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_ORDER_GETLIST
RETURN - Structure with Return Information
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_ORDER_GETLIST
ORDER_LIST - List of Selected Orders
Data type: BAPI2075_1Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_ORDER_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 BAPIRETURN, " | |||
| lt_order_list | TYPE STANDARD TABLE OF BAPI2075_1, " | |||
| lv_controlling_area | TYPE BAPI2075_2-CO_AREA, " | |||
| lv_resp_cost_center | TYPE BAPI2075_2-RESPCCTR, " | |||
| lv_order_type | TYPE BAPI2075_2-ORDER_TYPE, " | |||
| lv_order | TYPE BAPI2075_2-ORDER, " | |||
| lv_order_to | TYPE BAPI2075_2-ORDER, " | |||
| lv_order_external_no | TYPE BAPI2075_2-EXT_ORD_NO, " | |||
| lv_order_external_no_to | TYPE BAPI2075_2-EXT_ORD_NO. " |
|   CALL FUNCTION 'BBP_ORDER_GETLIST' "NOTRANSL: Liste aller Aufträgen |
| EXPORTING | ||
| CONTROLLING_AREA | = lv_controlling_area | |
| RESP_COST_CENTER | = lv_resp_cost_center | |
| ORDER_TYPE | = lv_order_type | |
| ORDER | = lv_order | |
| ORDER_TO | = lv_order_to | |
| ORDER_EXTERNAL_NO | = lv_order_external_no | |
| ORDER_EXTERNAL_NO_TO | = lv_order_external_no_to | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| ORDER_LIST | = lt_order_list | |
| . " BBP_ORDER_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM BBP_ORDER_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 CO_AREA FROM BAPI2075_2 INTO @DATA(ld_controlling_area). | ||||
| "SELECT single RESPCCTR FROM BAPI2075_2 INTO @DATA(ld_resp_cost_center). | ||||
| "SELECT single ORDER_TYPE FROM BAPI2075_2 INTO @DATA(ld_order_type). | ||||
| "SELECT single ORDER FROM BAPI2075_2 INTO @DATA(ld_order). | ||||
| "SELECT single ORDER FROM BAPI2075_2 INTO @DATA(ld_order_to). | ||||
| "SELECT single EXT_ORD_NO FROM BAPI2075_2 INTO @DATA(ld_order_external_no). | ||||
| "SELECT single EXT_ORD_NO FROM BAPI2075_2 INTO @DATA(ld_order_external_no_to). | ||||
Search for further information about these or an SAP related objects