SAP ISU_DB_BWPROT_SELECT Function Module for Read BI Extraction Orders (DBESTA_BWPROT)
ISU_DB_BWPROT_SELECT is a standard isu db bwprot select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read BI Extraction Orders (DBESTA_BWPROT) 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 isu db bwprot select FM, simply by entering the name ISU_DB_BWPROT_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: E71ESTA02
Program Name: SAPLE71ESTA02
Main Program: SAPLE71ESTA02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_BWPROT_SELECT 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 'ISU_DB_BWPROT_SELECT'"Read BI Extraction Orders (DBESTA_BWPROT).
EXPORTING
* I_MAX_RECORDS = 0 "Restrict Length of List
* I_FIKEY_RANGES = "Ranges Table: Reconciliation Key
* I_BUDAT_RANGES = "Range Table: Posting Date
* I_CPUDT_RANGES = "Ranges Table: Entry Date of Accounting Document
* I_UPDMODE_RANGES = "Ranges Table: Data Update Mode
* I_OPBEL_RANGES = "Ranges Table: Print Document Number
IMPORTING
E_ISU_BWPROT_TAB = "Table Type for Transparent Table DBESTA_BWPROT
E_COUNT = "Processed Database Table Rows
EXCEPTIONS
NOT_FOUND = 1 GENERAL_FAULT = 2
IMPORTING Parameters details for ISU_DB_BWPROT_SELECT
I_MAX_RECORDS - Restrict Length of List
Data type: DDSHMAXRECOptional: Yes
Call by Reference: Yes
I_FIKEY_RANGES - Ranges Table: Reconciliation Key
Data type: ISU_RT_FIKEYOptional: Yes
Call by Reference: Yes
I_BUDAT_RANGES - Range Table: Posting Date
Data type: ISU_RT_BUDATOptional: Yes
Call by Reference: Yes
I_CPUDT_RANGES - Ranges Table: Entry Date of Accounting Document
Data type: ISU_RT_CPUDTOptional: Yes
Call by Reference: Yes
I_UPDMODE_RANGES - Ranges Table: Data Update Mode
Data type: ISU_RT_UPDMODEOptional: Yes
Call by Reference: Yes
I_OPBEL_RANGES - Ranges Table: Print Document Number
Data type: ISU_RT_PRINTDOCOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_DB_BWPROT_SELECT
E_ISU_BWPROT_TAB - Table Type for Transparent Table DBESTA_BWPROT
Data type: T_ISU_DBESTA_BWPROTOptional: No
Call by Reference: Yes
E_COUNT - Processed Database Table Rows
Data type: SYDBCNTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - No suitable entries were found
Data type:Optional: No
Call by Reference: Yes
GENERAL_FAULT - General Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_DB_BWPROT_SELECT 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_not_found | TYPE STRING, " | |||
| lv_i_max_records | TYPE DDSHMAXREC, " 0 | |||
| lv_e_isu_bwprot_tab | TYPE T_ISU_DBESTA_BWPROT, " | |||
| lv_e_count | TYPE SYDBCNT, " | |||
| lv_general_fault | TYPE SYDBCNT, " | |||
| lv_i_fikey_ranges | TYPE ISU_RT_FIKEY, " | |||
| lv_i_budat_ranges | TYPE ISU_RT_BUDAT, " | |||
| lv_i_cpudt_ranges | TYPE ISU_RT_CPUDT, " | |||
| lv_i_updmode_ranges | TYPE ISU_RT_UPDMODE, " | |||
| lv_i_opbel_ranges | TYPE ISU_RT_PRINTDOC. " |
|   CALL FUNCTION 'ISU_DB_BWPROT_SELECT' "Read BI Extraction Orders (DBESTA_BWPROT) |
| EXPORTING | ||
| I_MAX_RECORDS | = lv_i_max_records | |
| I_FIKEY_RANGES | = lv_i_fikey_ranges | |
| I_BUDAT_RANGES | = lv_i_budat_ranges | |
| I_CPUDT_RANGES | = lv_i_cpudt_ranges | |
| I_UPDMODE_RANGES | = lv_i_updmode_ranges | |
| I_OPBEL_RANGES | = lv_i_opbel_ranges | |
| IMPORTING | ||
| E_ISU_BWPROT_TAB | = lv_e_isu_bwprot_tab | |
| E_COUNT | = lv_e_count | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| GENERAL_FAULT = 2 | ||
| . " ISU_DB_BWPROT_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_BWPROT_SELECT
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