SAP GRPC_BTC_REPORT_CREATE_ATTACH Function Module for









GRPC_BTC_REPORT_CREATE_ATTACH is a standard grpc 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 grpc btc report create attach FM, simply by entering the name GRPC_BTC_REPORT_CREATE_ATTACH into the relevant SAP transaction such as SE37 or SE38.

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



Function GRPC_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 'GRPC_BTC_REPORT_CREATE_ATTACH'"
EXPORTING
I_REPORT_GUID = "
I_REPORT_OUTPUT = "
I_ATTACHMENT_TYPE = "

IMPORTING
E_ATTACHMENT_IOTY = "
E_ATTACHMENT_CLASS = "
E_ATTACHMENT_ID = "

EXCEPTIONS
FAILED = 1
.



IMPORTING Parameters details for GRPC_BTC_REPORT_CREATE_ATTACH

I_REPORT_GUID -

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

I_REPORT_OUTPUT -

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

I_ATTACHMENT_TYPE -

Data type:
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for GRPC_BTC_REPORT_CREATE_ATTACH

E_ATTACHMENT_IOTY -

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

E_ATTACHMENT_CLASS -

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

E_ATTACHMENT_ID -

Data type: GRPC_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 GRPC_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.

DATA:
lv_failed  TYPE STRING, "   
lv_i_report_guid  TYPE GRPC_BTC_REPORTS-REPORT_GUID, "   
lv_e_attachment_ioty  TYPE GRPC_BTC_REPORTS-ATTACHMENT_IOTY, "   
lv_i_report_output  TYPE XSTRING, "   
lv_e_attachment_class  TYPE GRPC_BTC_REPORTS-ATTACHMENT_CLASS, "   
lv_e_attachment_id  TYPE GRPC_BTC_REPORTS-ATTACHMENT_ID, "   
lv_i_attachment_type  TYPE GRPC_BTC_REPORTS. "   

  CALL FUNCTION 'GRPC_BTC_REPORT_CREATE_ATTACH'  "
    EXPORTING
         I_REPORT_GUID = lv_i_report_guid
         I_REPORT_OUTPUT = lv_i_report_output
         I_ATTACHMENT_TYPE = lv_i_attachment_type
    IMPORTING
         E_ATTACHMENT_IOTY = lv_e_attachment_ioty
         E_ATTACHMENT_CLASS = lv_e_attachment_class
         E_ATTACHMENT_ID = lv_e_attachment_id
    EXCEPTIONS
        FAILED = 1
. " GRPC_BTC_REPORT_CREATE_ATTACH




ABAP code using 7.40 inline data declarations to call FM GRPC_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.

 
"SELECT single REPORT_GUID FROM GRPC_BTC_REPORTS INTO @DATA(ld_i_report_guid).
 
"SELECT single ATTACHMENT_IOTY FROM GRPC_BTC_REPORTS INTO @DATA(ld_e_attachment_ioty).
 
 
"SELECT single ATTACHMENT_CLASS FROM GRPC_BTC_REPORTS INTO @DATA(ld_e_attachment_class).
 
"SELECT single ATTACHMENT_ID FROM GRPC_BTC_REPORTS INTO @DATA(ld_e_attachment_id).
 
 


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!