SAP BAPI_SETTREQSLIST_GETLIST Function Module for Agency Business: BAPI Determine Settlement Request List Detailed Data
BAPI_SETTREQSLIST_GETLIST is a standard bapi settreqslist 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 Agency Business: BAPI Determine Settlement Request List Detailed Data 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 settreqslist getlist FM, simply by entering the name BAPI_SETTREQSLIST_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2100
Program Name: SAPL2100
Main Program: SAPL2100
Appliation area: W
Release date: 14-Dec-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SETTREQSLIST_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_SETTREQSLIST_GETLIST'"Agency Business: BAPI Determine Settlement Request List Detailed Data.
EXPORTING
* MAXLINES = '500' "Max. no. of Lines
TABLES
* DOCUMENTNUMBERRANGE = "Document Number
* BILLTYPERANGE = "Billing Type
* DOCDATERANGE = "Document Date
* REFDOCNORANGE = "Reference
* REFDOCNOLONGRANGE = "Reference (Long)
* ALLOCNMBRRANGE = "Assignment
* PAYMTREFRANGE = "Payment Reference
* HEADDATAOUT = "Document Header Data (Output)
* LISTITEMDATAOUT = "Settlement Request List Item Data (Output)
* LISTHEADDATAOUT = "Settlement Request List Header Data (Output)
* ITEMDATAOUT = "Document Item Data (Output)
* VENDORRANGE = "Invoicing Party
* RETURN = "Messages
* EXTENSIONOUT = "Enhancements (Output)
* HEADTEXTOUT = "Header Texts (Output)
* ITEMTEXTOUT = "Item Texts (Output)
* LISTHEADTEXTOUT = "Header Texts of the Lists (Output)
* PURCHORGRANGE = "Purchasing Organization
* PURGROUPRANGE = "Purchasing Group
* COMPCODERANGE = "Company Code
* BILLDATERANGE = "Posting Date
* INVLISTDATERANGE = "Remuneration List Date
* ACCTSTATUSRANGE = "Posting Status
* PAYTYPERANGE = "Payment Type
IMPORTING Parameters details for BAPI_SETTREQSLIST_GETLIST
MAXLINES - Max. no. of Lines
Data type: BAPIACGL-MAX_LINESDefault: '500'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_SETTREQSLIST_GETLIST
DOCUMENTNUMBERRANGE - Document Number
Data type: BAPIACDOCRANOptional: Yes
Call by Reference: No ( called with pass by value option)
BILLTYPERANGE - Billing Type
Data type: BAPI_RANGESLFARTOptional: Yes
Call by Reference: No ( called with pass by value option)
DOCDATERANGE - Document Date
Data type: BAPI_RANGESBLDATOptional: Yes
Call by Reference: No ( called with pass by value option)
REFDOCNORANGE - Reference
Data type: BAPI_RANGESXBLNROptional: Yes
Call by Reference: No ( called with pass by value option)
REFDOCNOLONGRANGE - Reference (Long)
Data type: BAPI_RANGESXBLNR_LONGOptional: Yes
Call by Reference: No ( called with pass by value option)
ALLOCNMBRRANGE - Assignment
Data type: BAPI_RANGESZUONROptional: Yes
Call by Reference: No ( called with pass by value option)
PAYMTREFRANGE - Payment Reference
Data type: BAPI_RANGESKIDNOOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADDATAOUT - Document Header Data (Output)
Data type: BAPISRHEADOOptional: Yes
Call by Reference: No ( called with pass by value option)
LISTITEMDATAOUT - Settlement Request List Item Data (Output)
Data type: BAPISLITEMOOptional: Yes
Call by Reference: No ( called with pass by value option)
LISTHEADDATAOUT - Settlement Request List Header Data (Output)
Data type: BAPISLLISTOptional: Yes
Call by Reference: No ( called with pass by value option)
ITEMDATAOUT - Document Item Data (Output)
Data type: BAPISRITEMOOptional: Yes
Call by Reference: No ( called with pass by value option)
VENDORRANGE - Invoicing Party
Data type: BAPI_RANGESLIFNROptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN - Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONOUT - Enhancements (Output)
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADTEXTOUT - Header Texts (Output)
Data type: BAPIABHEADCTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
ITEMTEXTOUT - Item Texts (Output)
Data type: BAPIABITEMCTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
LISTHEADTEXTOUT - Header Texts of the Lists (Output)
Data type: BAPIABLISTTEXTOptional: Yes
Call by Reference: Yes
PURCHORGRANGE - Purchasing Organization
Data type: BAPI_RANGESEKORGOptional: Yes
Call by Reference: No ( called with pass by value option)
PURGROUPRANGE - Purchasing Group
Data type: BAPI_RANGESEKGRPOptional: Yes
Call by Reference: No ( called with pass by value option)
COMPCODERANGE - Company Code
Data type: BAPI_RANGESBUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
BILLDATERANGE - Posting Date
Data type: BAPI_RANGESWFDATOptional: Yes
Call by Reference: No ( called with pass by value option)
INVLISTDATERANGE - Remuneration List Date
Data type: BAPI_RANGESWFDAT_RLOptional: Yes
Call by Reference: Yes
ACCTSTATUSRANGE - Posting Status
Data type: BAPI_RANGESRFBSKOptional: Yes
Call by Reference: No ( called with pass by value option)
PAYTYPERANGE - Payment Type
Data type: BAPI_RANGESWRARTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_SETTREQSLIST_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_maxlines | TYPE BAPIACGL-MAX_LINES, " '500' | |||
| lt_documentnumberrange | TYPE STANDARD TABLE OF BAPIACDOCRAN, " | |||
| lt_billtyperange | TYPE STANDARD TABLE OF BAPI_RANGESLFART, " | |||
| lt_docdaterange | TYPE STANDARD TABLE OF BAPI_RANGESBLDAT, " | |||
| lt_refdocnorange | TYPE STANDARD TABLE OF BAPI_RANGESXBLNR, " | |||
| lt_refdocnolongrange | TYPE STANDARD TABLE OF BAPI_RANGESXBLNR_LONG, " | |||
| lt_allocnmbrrange | TYPE STANDARD TABLE OF BAPI_RANGESZUONR, " | |||
| lt_paymtrefrange | TYPE STANDARD TABLE OF BAPI_RANGESKIDNO, " | |||
| lt_headdataout | TYPE STANDARD TABLE OF BAPISRHEADO, " | |||
| lt_listitemdataout | TYPE STANDARD TABLE OF BAPISLITEMO, " | |||
| lt_listheaddataout | TYPE STANDARD TABLE OF BAPISLLIST, " | |||
| lt_itemdataout | TYPE STANDARD TABLE OF BAPISRITEMO, " | |||
| lt_vendorrange | TYPE STANDARD TABLE OF BAPI_RANGESLIFNR, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_headtextout | TYPE STANDARD TABLE OF BAPIABHEADCTEXT, " | |||
| lt_itemtextout | TYPE STANDARD TABLE OF BAPIABITEMCTEXT, " | |||
| lt_listheadtextout | TYPE STANDARD TABLE OF BAPIABLISTTEXT, " | |||
| lt_purchorgrange | TYPE STANDARD TABLE OF BAPI_RANGESEKORG, " | |||
| lt_purgrouprange | TYPE STANDARD TABLE OF BAPI_RANGESEKGRP, " | |||
| lt_compcoderange | TYPE STANDARD TABLE OF BAPI_RANGESBUKRS, " | |||
| lt_billdaterange | TYPE STANDARD TABLE OF BAPI_RANGESWFDAT, " | |||
| lt_invlistdaterange | TYPE STANDARD TABLE OF BAPI_RANGESWFDAT_RL, " | |||
| lt_acctstatusrange | TYPE STANDARD TABLE OF BAPI_RANGESRFBSK, " | |||
| lt_paytyperange | TYPE STANDARD TABLE OF BAPI_RANGESWRART. " |
|   CALL FUNCTION 'BAPI_SETTREQSLIST_GETLIST' "Agency Business: BAPI Determine Settlement Request List Detailed Data |
| EXPORTING | ||
| MAXLINES | = lv_maxlines | |
| TABLES | ||
| DOCUMENTNUMBERRANGE | = lt_documentnumberrange | |
| BILLTYPERANGE | = lt_billtyperange | |
| DOCDATERANGE | = lt_docdaterange | |
| REFDOCNORANGE | = lt_refdocnorange | |
| REFDOCNOLONGRANGE | = lt_refdocnolongrange | |
| ALLOCNMBRRANGE | = lt_allocnmbrrange | |
| PAYMTREFRANGE | = lt_paymtrefrange | |
| HEADDATAOUT | = lt_headdataout | |
| LISTITEMDATAOUT | = lt_listitemdataout | |
| LISTHEADDATAOUT | = lt_listheaddataout | |
| ITEMDATAOUT | = lt_itemdataout | |
| VENDORRANGE | = lt_vendorrange | |
| RETURN | = lt_return | |
| EXTENSIONOUT | = lt_extensionout | |
| HEADTEXTOUT | = lt_headtextout | |
| ITEMTEXTOUT | = lt_itemtextout | |
| LISTHEADTEXTOUT | = lt_listheadtextout | |
| PURCHORGRANGE | = lt_purchorgrange | |
| PURGROUPRANGE | = lt_purgrouprange | |
| COMPCODERANGE | = lt_compcoderange | |
| BILLDATERANGE | = lt_billdaterange | |
| INVLISTDATERANGE | = lt_invlistdaterange | |
| ACCTSTATUSRANGE | = lt_acctstatusrange | |
| PAYTYPERANGE | = lt_paytyperange | |
| . " BAPI_SETTREQSLIST_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_SETTREQSLIST_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 MAX_LINES FROM BAPIACGL INTO @DATA(ld_maxlines). | ||||
| DATA(ld_maxlines) | = '500'. | |||
Search for further information about these or an SAP related objects