SAP FOPC_BTC_REPORT_GET_FOR_USER Function Module for

Search SAP Function Modules

FOPC_BTC_REPORT_GET_FOR_USER is a standard fopc btc report get for user 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 get for user FM, simply by entering the name FOPC_BTC_REPORT_GET_FOR_USER 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_GET_FOR_USER 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_GET_FOR_USER'"
  EXPORTING
   I_REPORT_MIC_USER =  "
*  I_REPORT_ENDTIME_FROM = '10000101' "
*  I_REPORT_ENDTIME_TO = '99991231' "
   I_BTC_REPORT_KIND =  "
*  I_CHECK_REPORT_STATE = ABAP_TRUE "

 IMPORTING
   ET_REPORTS =  "

.

IMPORTING Parameters details for FOPC_BTC_REPORT_GET_FOR_USER

I_REPORT_MIC_USER -

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

I_REPORT_ENDTIME_FROM -

Data type: DATUM
Default: '10000101'
Optional: Yes
Call by Reference: Yes

I_REPORT_ENDTIME_TO -

Data type: DATUM
Default: '99991231'
Optional: Yes
Call by Reference: Yes

I_BTC_REPORT_KIND -

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

I_CHECK_REPORT_STATE -

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

EXPORTING Parameters details for FOPC_BTC_REPORT_GET_FOR_USER

ET_REPORTS -

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

Copy and paste ABAP code example for FOPC_BTC_REPORT_GET_FOR_USER 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.

ABAP code using 7.40 inline data declarations to call FM FOPC_BTC_REPORT_GET_FOR_USER

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