SAP FOPC_BTC_REPORT_CREATE_ATTACH Function Module for

Search SAP Function Modules

FOPC_BTC_REPORT_CREATE_ATTACH is a standard fopc btc report create attach 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 create attach FM, simply by entering the name FOPC_BTC_REPORT_CREATE_ATTACH 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_CREATE_ATTACH 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_CREATE_ATTACH'"
  EXPORTING
   I_REPORT_GUID =  "GUID in 'CHAR' Format in Uppercase
   I_REPORT_OUTPUT =  "GUID in 'CHAR' Format in Uppercase
   I_ATTACHMENT_TYPE =  "

 IMPORTING
   E_ATTACHMENT_IOTY =  "KW Framework: IO type
   E_ATTACHMENT_CLASS =  "Document Class
   E_ATTACHMENT_ID =  "ID for documents and relations

EXCEPTIONS
   FAILED = 1 

.

IMPORTING Parameters details for FOPC_BTC_REPORT_CREATE_ATTACH

I_REPORT_GUID - GUID in 'CHAR' Format in Uppercase

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

I_REPORT_OUTPUT - GUID in 'CHAR' Format in Uppercase

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

I_ATTACHMENT_TYPE -

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

EXPORTING Parameters details for FOPC_BTC_REPORT_CREATE_ATTACH

E_ATTACHMENT_IOTY - KW Framework: IO type

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

E_ATTACHMENT_CLASS - Document Class

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

E_ATTACHMENT_ID - ID for documents and relations

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

EXCEPTIONS details

FAILED -

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

Copy and paste ABAP code example for FOPC_BTC_REPORT_CREATE_ATTACH 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_CREATE_ATTACH

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