SAP BAPI_BUSPROCESSND_GETLIST Function Module for Get list of One Order transactions
BAPI_BUSPROCESSND_GETLIST is a standard bapi busprocessnd 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 Get list of One Order transactions 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 busprocessnd getlist FM, simply by entering the name BAPI_BUSPROCESSND_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_BUSPROCESSND_BAPI
Program Name: SAPLCRM_BUSPROCESSND_BAPI
Main Program: SAPLCRM_BUSPROCESSND_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_BUSPROCESSND_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 'BAPI_BUSPROCESSND_GETLIST'"Get list of One Order transactions.
TABLES
* GUID = "BO BusProcessND: GUID in BAPI Format Display ()
* OBJECT_ID_SEL = "Range Table Line for OBJECT_ID
* PROCESS_TYPE_SEL = "Range Table Line for TYPE
* OBJECT_TYPE_SEL = "Range Table Line for OBJECT_TYPE
* POSTING_DATE_SEL = "Range Table Line for POSTING_DATE
* DATE_OF_CONTACT_SEL = "Range Table Line for POSTING_DATE
* SERVICE_ORG_SEL = "BAPI Selection Structure: Sales Organization
* RETURN = "Return Parameter
* ORDERACT_DATE_SEL = "date range for date1
* PARTNER_NO_SEL = "BAPI Selection Structure: Business Partner
* PARTNER_FCT_SEL = "BAPI Selection Structure: Partner Function
* CATEGORY_SEL = "BAPI Selection Structure: Category
* SALES_ORG_SEL = "BAPI Selection Structure: Sales Organization
* DIS_CHANNEL_SEL = "BAPI Selection Structure: Distribution Channel
* DIVISION_SEL = "BAPI Selection Structure: Division
* SALES_OFFICE_SEL = "BAPI Selection Structure: Sales Office
* SALES_GROUP_SEL = "BAPI Selection Structure: Sales Group
TABLES Parameters details for BAPI_BUSPROCESSND_GETLIST
GUID - BO BusProcessND: GUID in BAPI Format Display ()
Data type: BAPIBUS20001_GUID_DISOptional: Yes
Call by Reference: Yes
OBJECT_ID_SEL - Range Table Line for OBJECT_ID
Data type: BAPIBUS20001_OBJECT_ID_RNGOptional: Yes
Call by Reference: Yes
PROCESS_TYPE_SEL - Range Table Line for TYPE
Data type: BAPIBUS20001_PROCESS_TYPE_RNGOptional: Yes
Call by Reference: Yes
OBJECT_TYPE_SEL - Range Table Line for OBJECT_TYPE
Data type: BAPIBUS20001_OBJECT_TYPE_RNGOptional: Yes
Call by Reference: Yes
POSTING_DATE_SEL - Range Table Line for POSTING_DATE
Data type: BAPIBUS20001_POSTING_DATE_RNGOptional: Yes
Call by Reference: Yes
DATE_OF_CONTACT_SEL - Range Table Line for POSTING_DATE
Data type: BAPIBUS20001_DATE_CONTACT_RNGOptional: Yes
Call by Reference: Yes
SERVICE_ORG_SEL - BAPI Selection Structure: Sales Organization
Data type: BAPIBUS20001_SERVICE_ORG_RNGOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
ORDERACT_DATE_SEL - date range for date1
Data type: BAPIBUS20001_DATE1_DATE_RNGOptional: Yes
Call by Reference: Yes
PARTNER_NO_SEL - BAPI Selection Structure: Business Partner
Data type: BAPIBUS20001_PARTNER_RNGOptional: Yes
Call by Reference: Yes
PARTNER_FCT_SEL - BAPI Selection Structure: Partner Function
Data type: BAPIBUS20001_PARTNER_FCT_RNGOptional: Yes
Call by Reference: Yes
CATEGORY_SEL - BAPI Selection Structure: Category
Data type: BAPIBUS2000110_CATEGORY_RNGOptional: Yes
Call by Reference: Yes
SALES_ORG_SEL - BAPI Selection Structure: Sales Organization
Data type: BAPIBUS20001_SALES_ORG_RNGOptional: Yes
Call by Reference: Yes
DIS_CHANNEL_SEL - BAPI Selection Structure: Distribution Channel
Data type: BAPIBUS20001_DIS_CHANNEL_RNGOptional: Yes
Call by Reference: Yes
DIVISION_SEL - BAPI Selection Structure: Division
Data type: BAPIBUS20001_DIVISION_RNGOptional: Yes
Call by Reference: Yes
SALES_OFFICE_SEL - BAPI Selection Structure: Sales Office
Data type: BAPIBUS20001_SALES_OFFICE_RNGOptional: Yes
Call by Reference: Yes
SALES_GROUP_SEL - BAPI Selection Structure: Sales Group
Data type: BAPIBUS20001_SALES_GROUP_RNGOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_BUSPROCESSND_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: | ||||
| lt_guid | TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS, " | |||
| lt_object_id_sel | TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID_RNG, " | |||
| lt_process_type_sel | TYPE STANDARD TABLE OF BAPIBUS20001_PROCESS_TYPE_RNG, " | |||
| lt_object_type_sel | TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_TYPE_RNG, " | |||
| lt_posting_date_sel | TYPE STANDARD TABLE OF BAPIBUS20001_POSTING_DATE_RNG, " | |||
| lt_date_of_contact_sel | TYPE STANDARD TABLE OF BAPIBUS20001_DATE_CONTACT_RNG, " | |||
| lt_service_org_sel | TYPE STANDARD TABLE OF BAPIBUS20001_SERVICE_ORG_RNG, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_orderact_date_sel | TYPE STANDARD TABLE OF BAPIBUS20001_DATE1_DATE_RNG, " | |||
| lt_partner_no_sel | TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_RNG, " | |||
| lt_partner_fct_sel | TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_FCT_RNG, " | |||
| lt_category_sel | TYPE STANDARD TABLE OF BAPIBUS2000110_CATEGORY_RNG, " | |||
| lt_sales_org_sel | TYPE STANDARD TABLE OF BAPIBUS20001_SALES_ORG_RNG, " | |||
| lt_dis_channel_sel | TYPE STANDARD TABLE OF BAPIBUS20001_DIS_CHANNEL_RNG, " | |||
| lt_division_sel | TYPE STANDARD TABLE OF BAPIBUS20001_DIVISION_RNG, " | |||
| lt_sales_office_sel | TYPE STANDARD TABLE OF BAPIBUS20001_SALES_OFFICE_RNG, " | |||
| lt_sales_group_sel | TYPE STANDARD TABLE OF BAPIBUS20001_SALES_GROUP_RNG. " |
|   CALL FUNCTION 'BAPI_BUSPROCESSND_GETLIST' "Get list of One Order transactions |
| TABLES | ||
| GUID | = lt_guid | |
| OBJECT_ID_SEL | = lt_object_id_sel | |
| PROCESS_TYPE_SEL | = lt_process_type_sel | |
| OBJECT_TYPE_SEL | = lt_object_type_sel | |
| POSTING_DATE_SEL | = lt_posting_date_sel | |
| DATE_OF_CONTACT_SEL | = lt_date_of_contact_sel | |
| SERVICE_ORG_SEL | = lt_service_org_sel | |
| RETURN | = lt_return | |
| ORDERACT_DATE_SEL | = lt_orderact_date_sel | |
| PARTNER_NO_SEL | = lt_partner_no_sel | |
| PARTNER_FCT_SEL | = lt_partner_fct_sel | |
| CATEGORY_SEL | = lt_category_sel | |
| SALES_ORG_SEL | = lt_sales_org_sel | |
| DIS_CHANNEL_SEL | = lt_dis_channel_sel | |
| DIVISION_SEL | = lt_division_sel | |
| SALES_OFFICE_SEL | = lt_sales_office_sel | |
| SALES_GROUP_SEL | = lt_sales_group_sel | |
| . " BAPI_BUSPROCESSND_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_BUSPROCESSND_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.Search for further information about these or an SAP related objects