SAP FWTR_SEC_UNDERLYING_INIT Function Module for Create Security Transaction as Underlying









FWTR_SEC_UNDERLYING_INIT is a standard fwtr sec underlying init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Security Transaction as Underlying 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 fwtr sec underlying init FM, simply by entering the name FWTR_SEC_UNDERLYING_INIT into the relevant SAP transaction such as SE37 or SE38.

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



Function FWTR_SEC_UNDERLYING_INIT 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 'FWTR_SEC_UNDERLYING_INIT'"Create Security Transaction as Underlying
  EXPORTING
   I_MODUS =  "Edit Mode
   I_BUKRS =  "Company Code
   I_VTI_MEMOUL =  "Daten zum Anlegen
   I_VTIFHA =  "Transaction
   I_VTIFHAZU =  "Activity
   I_TAB_VTIFHAPO =  "Flows
*  I_OREF_APPL_CTRL =  "TR Transaction Management: Application Control
*  I_IREF_GUI_FOREIGN =  "TR Transaction Management: Appl <--> Foreign GUI

 IMPORTING
   E_OKCODE =  "Letzter Okcode in Geschäftsverwaltung

EXCEPTIONS
   INVALID = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLFWTR_01_001 Customer Function Order Management - Menu Enhancement +001
EXIT_SAPLFWTR_01_002 Customer Function Order Management - Menu Enhancement +002

IMPORTING Parameters details for FWTR_SEC_UNDERLYING_INIT

I_MODUS - Edit Mode

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

I_BUKRS - Company Code

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

I_VTI_MEMOUL - Daten zum Anlegen

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

I_VTIFHA - Transaction

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

I_VTIFHAZU - Activity

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

I_TAB_VTIFHAPO - Flows

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

I_OREF_APPL_CTRL - TR Transaction Management: Application Control

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

I_IREF_GUI_FOREIGN - TR Transaction Management: Appl <--> Foreign GUI

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

EXPORTING Parameters details for FWTR_SEC_UNDERLYING_INIT

E_OKCODE - Letzter Okcode in Geschäftsverwaltung

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

EXCEPTIONS details

INVALID - Error Occurred

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FWTR_SEC_UNDERLYING_INIT 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_invalid  TYPE STRING, "   
lv_i_modus  TYPE C, "   
lv_e_okcode  TYPE TCODE, "   
lv_i_bukrs  TYPE BUKRS, "   
lv_i_vti_memoul  TYPE VTI_MEMOUL, "   
lv_i_vtifha  TYPE TRDE_STR_IFHA, "   
lv_i_vtifhazu  TYPE TRDE_STR_IFHAZU, "   
lv_i_tab_vtifhapo  TYPE TRDE_TAB_IFHAPO, "   
lv_i_oref_appl_ctrl  TYPE CL_FTR_APPL_CTRL, "   
lv_i_iref_gui_foreign  TYPE IF_FTR_GUI_FOREIGN_APPL. "   

  CALL FUNCTION 'FWTR_SEC_UNDERLYING_INIT'  "Create Security Transaction as Underlying
    EXPORTING
         I_MODUS = lv_i_modus
         I_BUKRS = lv_i_bukrs
         I_VTI_MEMOUL = lv_i_vti_memoul
         I_VTIFHA = lv_i_vtifha
         I_VTIFHAZU = lv_i_vtifhazu
         I_TAB_VTIFHAPO = lv_i_tab_vtifhapo
         I_OREF_APPL_CTRL = lv_i_oref_appl_ctrl
         I_IREF_GUI_FOREIGN = lv_i_iref_gui_foreign
    IMPORTING
         E_OKCODE = lv_e_okcode
    EXCEPTIONS
        INVALID = 1
. " FWTR_SEC_UNDERLYING_INIT




ABAP code using 7.40 inline data declarations to call FM FWTR_SEC_UNDERLYING_INIT

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



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!