SAP META_ORDER_GETLIST Function Module for List of orders









META_ORDER_GETLIST is a standard meta 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 List of orders 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 meta order getlist FM, simply by entering the name META_ORDER_GETLIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_BD_META_BAPIS
Program Name: SAPLBBP_BD_META_BAPIS
Main Program: SAPLBBP_BD_META_BAPIS
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function META_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 'META_ORDER_GETLIST'"List of orders
EXPORTING
* CONTROLLING_AREA = "
* RESP_COST_CENTER = "
* ORDER_TYPE = "
* ORDER = "
* ORDER_TO = "
* ORDER_EXTERNAL_NO = "
* ORDER_EXTERNAL_NO_TO = "
* LOGICAL_SYSTEM = "

IMPORTING
RETURN = "Return code

TABLES
* ORDER_LIST = "
* CONTROL_RECORD = "Meta BAPI control record
.



IMPORTING Parameters details for META_ORDER_GETLIST

CONTROLLING_AREA -

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

RESP_COST_CENTER -

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

ORDER_TYPE -

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

ORDER -

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

ORDER_TO -

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

ORDER_EXTERNAL_NO -

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

ORDER_EXTERNAL_NO_TO -

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

LOGICAL_SYSTEM -

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

EXPORTING Parameters details for META_ORDER_GETLIST

RETURN - Return code

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

TABLES Parameters details for META_ORDER_GETLIST

ORDER_LIST -

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

CONTROL_RECORD - Meta BAPI control record

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

Copy and paste ABAP code example for META_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, "   
lt_control_record  TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, "   
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, "   
lv_logical_system  TYPE BBP_BACKEND_DEST-LOG_SYS. "   

  CALL FUNCTION 'META_ORDER_GETLIST'  "List of orders
    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
         LOGICAL_SYSTEM = lv_logical_system
    IMPORTING
         RETURN = lv_return
    TABLES
         ORDER_LIST = lt_order_list
         CONTROL_RECORD = lt_control_record
. " META_ORDER_GETLIST




ABAP code using 7.40 inline data declarations to call FM META_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).
 
"SELECT single LOG_SYS FROM BBP_BACKEND_DEST INTO @DATA(ld_logical_system).
 


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!