SAP RKD_REPORT_EXPORT_C Function Module for









RKD_REPORT_EXPORT_C is a standard rkd report export c 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 rkd report export c FM, simply by entering the name RKD_REPORT_EXPORT_C into the relevant SAP transaction such as SE37 or SE38.

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



Function RKD_REPORT_EXPORT_C 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 'RKD_REPORT_EXPORT_C'"
EXPORTING
* I_CODE = 'EX' "Code
* I_COMMIT = ' ' "'Commit Work' should be executed
I_RKB1D = "
I_REPORT = "
.



IMPORTING Parameters details for RKD_REPORT_EXPORT_C

I_CODE - Code

Data type: CFCODES-M_EXPORT
Default: 'EX'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_COMMIT - 'Commit Work' should be executed

Data type: CCVALID-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_RKB1D -

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

I_REPORT -

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

Copy and paste ABAP code example for RKD_REPORT_EXPORT_C 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_code  TYPE CFCODES-M_EXPORT, "   'EX'
lv_i_commit  TYPE CCVALID-XFELD, "   SPACE
lv_i_rkb1d  TYPE RKB1D, "   
lv_i_report  TYPE RKD_SC_REPORT. "   

  CALL FUNCTION 'RKD_REPORT_EXPORT_C'  "
    EXPORTING
         I_CODE = lv_i_code
         I_COMMIT = lv_i_commit
         I_RKB1D = lv_i_rkb1d
         I_REPORT = lv_i_report
. " RKD_REPORT_EXPORT_C




ABAP code using 7.40 inline data declarations to call FM RKD_REPORT_EXPORT_C

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 M_EXPORT FROM CFCODES INTO @DATA(ld_i_code).
DATA(ld_i_code) = 'EX'.
 
"SELECT single XFELD FROM CCVALID INTO @DATA(ld_i_commit).
DATA(ld_i_commit) = ' '.
 
 
 


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!