SAP FOPC_BTC_REPORT_UPDATE Function Module for









FOPC_BTC_REPORT_UPDATE is a standard fopc btc report update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fopc btc report update FM, simply by entering the name FOPC_BTC_REPORT_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FOPC_BTC_REPORT
Program Name: SAPLFOPC_BTC_REPORT
Main Program: SAPLFOPC_BTC_REPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FOPC_BTC_REPORT_UPDATE 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 'FOPC_BTC_REPORT_UPDATE'"
EXPORTING
I_GUID = "GUID in 'CHAR' Format in Uppercase
IS_REPORT = "Background Reports in System
* SEND_WORKFLOW = ABAP_FALSE "
* WRKFLW_RECIPIENT = ABAP_FALSE "

IMPORTING
E_UPDATED = "

EXCEPTIONS
LOCKED = 1 NOT_FOUND = 2 FAILED = 3 NOT_ALLOWED = 4
.



IMPORTING Parameters details for FOPC_BTC_REPORT_UPDATE

I_GUID - GUID in 'CHAR' Format in Uppercase

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

IS_REPORT - Background Reports in System

Data type: FOPC_BTC_REPORTS
Optional: No
Call by Reference: Yes

SEND_WORKFLOW -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

WRKFLW_RECIPIENT -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FOPC_BTC_REPORT_UPDATE

E_UPDATED -

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

EXCEPTIONS details

LOCKED -

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

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FAILED -

Data type:
Optional: No
Call by Reference: Yes

NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FOPC_BTC_REPORT_UPDATE 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_i_guid  TYPE GUID_32, "   
lv_locked  TYPE GUID_32, "   
lv_e_updated  TYPE ABAP_BOOL, "   
lv_is_report  TYPE FOPC_BTC_REPORTS, "   
lv_not_found  TYPE FOPC_BTC_REPORTS, "   
lv_failed  TYPE FOPC_BTC_REPORTS, "   
lv_send_workflow  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_not_allowed  TYPE ABAP_BOOL, "   
lv_wrkflw_recipient  TYPE ABAP_BOOL. "   ABAP_FALSE

  CALL FUNCTION 'FOPC_BTC_REPORT_UPDATE'  "
    EXPORTING
         I_GUID = lv_i_guid
         IS_REPORT = lv_is_report
         SEND_WORKFLOW = lv_send_workflow
         WRKFLW_RECIPIENT = lv_wrkflw_recipient
    IMPORTING
         E_UPDATED = lv_e_updated
    EXCEPTIONS
        LOCKED = 1
        NOT_FOUND = 2
        FAILED = 3
        NOT_ALLOWED = 4
. " FOPC_BTC_REPORT_UPDATE




ABAP code using 7.40 inline data declarations to call FM FOPC_BTC_REPORT_UPDATE

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.

 
 
 
 
 
 
DATA(ld_send_workflow) = ABAP_FALSE.
 
 
DATA(ld_wrkflw_recipient) = ABAP_FALSE.
 


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!