SAP BAPI_BROKERREP_CHANGE Function Module for Change a Broker Report









BAPI_BROKERREP_CHANGE is a standard bapi brokerrep change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change a Broker Report 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 change FM, simply by entering the name BAPI_BROKERREP_CHANGE 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_CHANGE 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_CHANGE'"Change a Broker Report
EXPORTING
REPORTID = "Broker Report Identification
BROKERREPORTHEADER = "Broker Report - BAPI Structure Broker Report Header
BROKERREPORTHEADERX = "Broker Report - BAPI Structure Broker Report Header
* TESTRUN = "Switch to Simulation Mode for Write BAPIs
* NO_AUTH_CHECK = "Do Not Execute Authorization Checks for User Data

TABLES
* BROKERREPORTDEFAULT = "Broker Report - BAPI Structure Proposal Data
* BROKERREPORTDEFAULTX = "Broker Report: BAPI Structure Proposal Data Changes
* 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_CHANGE

REPORTID - Broker Report Identification

Data type: BAPIBROKREPHEADER-REPORT
Optional: No
Call by Reference: No ( called with pass by value option)

BROKERREPORTHEADER - Broker Report - BAPI Structure Broker Report Header

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

BROKERREPORTHEADERX - Broker Report - BAPI Structure Broker Report Header

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

TESTRUN - Switch to Simulation Mode for Write BAPIs

Data type: BAPIBROKREPCTRL-TESTRUN
Optional: Yes
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_CHECK
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_BROKERREP_CHANGE

BROKERREPORTDEFAULT - Broker Report - BAPI Structure Proposal Data

Data type: BAPIBROKREPDEFAULT
Optional: Yes
Call by Reference: Yes

BROKERREPORTDEFAULTX - Broker Report: BAPI Structure Proposal Data Changes

Data type: BAPIBROKREPDEFAULTX
Optional: Yes
Call by Reference: Yes

EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameters

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_BROKERREP_CHANGE 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, "   
lt_brokerreportdefault  TYPE STANDARD TABLE OF BAPIBROKREPDEFAULT, "   
lv_brokerreportheader  TYPE BAPIBROKREPHEADER, "   
lt_brokerreportdefaultx  TYPE STANDARD TABLE OF BAPIBROKREPDEFAULTX, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_brokerreportheaderx  TYPE BAPIBROKREPHEADERX, "   
lv_testrun  TYPE BAPIBROKREPCTRL-TESTRUN, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_no_auth_check  TYPE BAPIBROKREPCTRL-NO_AUTH_CHECK. "   

  CALL FUNCTION 'BAPI_BROKERREP_CHANGE'  "Change a Broker Report
    EXPORTING
         REPORTID = lv_reportid
         BROKERREPORTHEADER = lv_brokerreportheader
         BROKERREPORTHEADERX = lv_brokerreportheaderx
         TESTRUN = lv_testrun
         NO_AUTH_CHECK = lv_no_auth_check
    TABLES
         BROKERREPORTDEFAULT = lt_brokerreportdefault
         BROKERREPORTDEFAULTX = lt_brokerreportdefaultx
         EXTENSIONIN = lt_extensionin
         EXTENSIONOUT = lt_extensionout
         RETURN = lt_return
. " BAPI_BROKERREP_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_BROKERREP_CHANGE

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 TESTRUN FROM BAPIBROKREPCTRL INTO @DATA(ld_testrun).
 
 
 
"SELECT single NO_AUTH_CHECK FROM BAPIBROKREPCTRL INTO @DATA(ld_no_auth_check).
 


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!