SAP TRANSACTIONS_INITIALIZE Function Module for Initialization of reporting transactions (EC-EIS/CO-PA)









TRANSACTIONS_INITIALIZE is a standard transactions initialize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialization of reporting transactions (EC-EIS/CO-PA) processing and below is the pattern details for this FM, 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 transactions initialize FM, simply by entering the name TRANSACTIONS_INITIALIZE into the relevant SAP transaction such as SE37 or SE38.

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



Function TRANSACTIONS_INITIALIZE 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 'TRANSACTIONS_INITIALIZE'"Initialization of reporting transactions (EC-EIS/CO-PA)
EXPORTING
* APPLCLASS = ' ' "Application class
* I_GET_APPLICATION = ' ' "
* I_RAISE_USER_ABEND = "

IMPORTING
E_APPLCLASS = "Application class
E_SMODUS = "
E_SUBCLASS = "
TRANSACTIONS = "Names of transactions

EXCEPTIONS
USER_ABEND = 1
.



IMPORTING Parameters details for TRANSACTIONS_INITIALIZE

APPLCLASS - Application class

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

I_GET_APPLICATION -

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

I_RAISE_USER_ABEND -

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

EXPORTING Parameters details for TRANSACTIONS_INITIALIZE

E_APPLCLASS - Application class

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

E_SMODUS -

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

E_SUBCLASS -

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

TRANSACTIONS - Names of transactions

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

EXCEPTIONS details

USER_ABEND -

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

Copy and paste ABAP code example for TRANSACTIONS_INITIALIZE 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_applclass  TYPE TKEB1-APPLCLASS, "   SPACE
lv_user_abend  TYPE TKEB1, "   
lv_e_applclass  TYPE TKEB1-APPLCLASS, "   
lv_e_smodus  TYPE RKB1D-SMODUS, "   
lv_i_get_application  TYPE CCVALID-XFELD, "   SPACE
lv_e_subclass  TYPE RKB1D-SUBCLASS, "   
lv_i_raise_user_abend  TYPE RKD_FLAG, "   
lv_transactions  TYPE CFBTC01. "   

  CALL FUNCTION 'TRANSACTIONS_INITIALIZE'  "Initialization of reporting transactions (EC-EIS/CO-PA)
    EXPORTING
         APPLCLASS = lv_applclass
         I_GET_APPLICATION = lv_i_get_application
         I_RAISE_USER_ABEND = lv_i_raise_user_abend
    IMPORTING
         E_APPLCLASS = lv_e_applclass
         E_SMODUS = lv_e_smodus
         E_SUBCLASS = lv_e_subclass
         TRANSACTIONS = lv_transactions
    EXCEPTIONS
        USER_ABEND = 1
. " TRANSACTIONS_INITIALIZE




ABAP code using 7.40 inline data declarations to call FM TRANSACTIONS_INITIALIZE

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 APPLCLASS FROM TKEB1 INTO @DATA(ld_applclass).
DATA(ld_applclass) = ' '.
 
 
"SELECT single APPLCLASS FROM TKEB1 INTO @DATA(ld_e_applclass).
 
"SELECT single SMODUS FROM RKB1D INTO @DATA(ld_e_smodus).
 
"SELECT single XFELD FROM CCVALID INTO @DATA(ld_i_get_application).
DATA(ld_i_get_application) = ' '.
 
"SELECT single SUBCLASS FROM RKB1D INTO @DATA(ld_e_subclass).
 
 
 


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!