SAP BAPI_BROKERREP_GETDETAIL Function Module for Reading Broker Report Information
BAPI_BROKERREP_GETDETAIL is a standard bapi brokerrep getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reading Broker Report Information 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 brokerrep getdetail FM, simply by entering the name BAPI_BROKERREP_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBRBAPI
Program Name: SAPLIBRBAPI
Main Program: SAPLIBRBAPI
Appliation area:
Release date: 21-Aug-2007
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_BROKERREP_GETDETAIL 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_BROKERREP_GETDETAIL'"Reading Broker Report Information.
EXPORTING
REPORTID = "Broker Report Identification
* NO_AUTH_CHECK = "Do Not Execute Authorization Checks for User Data
IMPORTING
BROKERREPORTHEADER = "Broker Report - BAPI Structure Broker Report Header
TABLES
* BROKERREPORTDEFAULT = "Broker Report - BAPI Structure Proposal Data
* BROKERREPORTITEM = "Broker Report: BAPI Structure Item Data
* BROKERREPORTSELITEM = "Broker Report: BAPI Structure Selected Open Items
* BROKERREPORTITEMDOC = "Broker Report: BAPI Structure for Additional Documents
* BROKERREPORTCLARCASES = "Broker Report: BAPI Structure Clarification Cases
* EXTENSIONIN = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* EXTENSIONOUT = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_BROKERREP_GETDETAIL
REPORTID - Broker Report Identification
Data type: BAPIBROKREPHEADER-REPORTOptional: No
Call by Reference: No ( called with pass by value option)
NO_AUTH_CHECK - Do Not Execute Authorization Checks for User Data
Data type: BAPIBROKREPCTRL-NO_AUTH_CHECKOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_BROKERREP_GETDETAIL
BROKERREPORTHEADER - Broker Report - BAPI Structure Broker Report Header
Data type: BAPIBROKREPHEADER_DETAILOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_BROKERREP_GETDETAIL
BROKERREPORTDEFAULT - Broker Report - BAPI Structure Proposal Data
Data type: BAPIBROKREPDEFAULT_DETAILOptional: Yes
Call by Reference: Yes
BROKERREPORTITEM - Broker Report: BAPI Structure Item Data
Data type: BAPIBROKREPITEM_DETAILOptional: Yes
Call by Reference: Yes
BROKERREPORTSELITEM - Broker Report: BAPI Structure Selected Open Items
Data type: BAPIBROKREPSELITEMOptional: Yes
Call by Reference: Yes
BROKERREPORTITEMDOC - Broker Report: BAPI Structure for Additional Documents
Data type: BAPIBROKREPITEM_DOCSOptional: Yes
Call by Reference: Yes
BROKERREPORTCLARCASES - Broker Report: BAPI Structure Clarification Cases
Data type: BAPIBROKREPCLARCASESOptional: Yes
Call by Reference: Yes
EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_BROKERREP_GETDETAIL 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_reportid | TYPE BAPIBROKREPHEADER-REPORT, " | |||
| lv_brokerreportheader | TYPE BAPIBROKREPHEADER_DETAIL, " | |||
| lt_brokerreportdefault | TYPE STANDARD TABLE OF BAPIBROKREPDEFAULT_DETAIL, " | |||
| lv_no_auth_check | TYPE BAPIBROKREPCTRL-NO_AUTH_CHECK, " | |||
| lt_brokerreportitem | TYPE STANDARD TABLE OF BAPIBROKREPITEM_DETAIL, " | |||
| lt_brokerreportselitem | TYPE STANDARD TABLE OF BAPIBROKREPSELITEM, " | |||
| lt_brokerreportitemdoc | TYPE STANDARD TABLE OF BAPIBROKREPITEM_DOCS, " | |||
| lt_brokerreportclarcases | TYPE STANDARD TABLE OF BAPIBROKREPCLARCASES, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_BROKERREP_GETDETAIL' "Reading Broker Report Information |
| EXPORTING | ||
| REPORTID | = lv_reportid | |
| NO_AUTH_CHECK | = lv_no_auth_check | |
| IMPORTING | ||
| BROKERREPORTHEADER | = lv_brokerreportheader | |
| TABLES | ||
| BROKERREPORTDEFAULT | = lt_brokerreportdefault | |
| BROKERREPORTITEM | = lt_brokerreportitem | |
| BROKERREPORTSELITEM | = lt_brokerreportselitem | |
| BROKERREPORTITEMDOC | = lt_brokerreportitemdoc | |
| BROKERREPORTCLARCASES | = lt_brokerreportclarcases | |
| EXTENSIONIN | = lt_extensionin | |
| EXTENSIONOUT | = lt_extensionout | |
| RETURN | = lt_return | |
| . " BAPI_BROKERREP_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_BROKERREP_GETDETAIL
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 REPORT FROM BAPIBROKREPHEADER INTO @DATA(ld_reportid). | ||||
| "SELECT single NO_AUTH_CHECK FROM BAPIBROKREPCTRL INTO @DATA(ld_no_auth_check). | ||||
Search for further information about these or an SAP related objects