SAP TTM_FX_BAPI_INIT_APPL Function Module for TTM FX: Get Appl
TTM_FX_BAPI_INIT_APPL is a standard ttm fx bapi init appl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TTM FX: Get Appl 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 ttm fx bapi init appl FM, simply by entering the name TTM_FX_BAPI_INIT_APPL into the relevant SAP transaction such as SE37 or SE38.
Function Group: TTM_FX_UI
Program Name: SAPLTTM_FX_UI
Main Program: SAPLTTM_FX_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TTM_FX_BAPI_INIT_APPL 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 'TTM_FX_BAPI_INIT_APPL'"TTM FX: Get Appl.
EXPORTING
IV_EDITMODE = "
IV_TRANSACTIONCODE = "ABAP System Field: Current Transaction Code
* IV_DIALOG = "Boolean Variable (X=True, -=False, Space=Unknown)
* IV_CRUSER = "Entered by
IMPORTING
EO_APPL_CTRL = "TR Transaction Management: Application Control
EI_BAPI_PLUGIN = "TRTM BAPI Application Interface Forex Transactions Level 2
EI_BAPI_PLUGIN_SWAP = "TRTM BAPI Application Interface Swap Transactions Level 2
EXCEPTIONS
INIT_FAILED = 1
IMPORTING Parameters details for TTM_FX_BAPI_INIT_APPL
IV_EDITMODE -
Data type: FTRG_CHAROptional: No
Call by Reference: No ( called with pass by value option)
IV_TRANSACTIONCODE - ABAP System Field: Current Transaction Code
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_DIALOG - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CRUSER - Entered by
Data type: TB_CRUSEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TTM_FX_BAPI_INIT_APPL
EO_APPL_CTRL - TR Transaction Management: Application Control
Data type: CL_FTR_APPL_CTRLOptional: No
Call by Reference: Yes
EI_BAPI_PLUGIN - TRTM BAPI Application Interface Forex Transactions Level 2
Data type: IF_FTR_BAPI_TRTM_600_NGOptional: No
Call by Reference: Yes
EI_BAPI_PLUGIN_SWAP - TRTM BAPI Application Interface Swap Transactions Level 2
Data type: IF_FTR_BAPI_TRTM_600SWAP_NGOptional: No
Call by Reference: Yes
EXCEPTIONS details
INIT_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TTM_FX_BAPI_INIT_APPL 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_init_failed | TYPE STRING, " | |||
| lv_iv_editmode | TYPE FTRG_CHAR, " | |||
| lv_eo_appl_ctrl | TYPE CL_FTR_APPL_CTRL, " | |||
| lv_ei_bapi_plugin | TYPE IF_FTR_BAPI_TRTM_600_NG, " | |||
| lv_iv_transactioncode | TYPE SY-TCODE, " | |||
| lv_iv_dialog | TYPE BOOLEAN, " | |||
| lv_ei_bapi_plugin_swap | TYPE IF_FTR_BAPI_TRTM_600SWAP_NG, " | |||
| lv_iv_cruser | TYPE TB_CRUSER. " |
|   CALL FUNCTION 'TTM_FX_BAPI_INIT_APPL' "TTM FX: Get Appl |
| EXPORTING | ||
| IV_EDITMODE | = lv_iv_editmode | |
| IV_TRANSACTIONCODE | = lv_iv_transactioncode | |
| IV_DIALOG | = lv_iv_dialog | |
| IV_CRUSER | = lv_iv_cruser | |
| IMPORTING | ||
| EO_APPL_CTRL | = lv_eo_appl_ctrl | |
| EI_BAPI_PLUGIN | = lv_ei_bapi_plugin | |
| EI_BAPI_PLUGIN_SWAP | = lv_ei_bapi_plugin_swap | |
| EXCEPTIONS | ||
| INIT_FAILED = 1 | ||
| . " TTM_FX_BAPI_INIT_APPL | ||
ABAP code using 7.40 inline data declarations to call FM TTM_FX_BAPI_INIT_APPL
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 TCODE FROM SY INTO @DATA(ld_iv_transactioncode). | ||||
Search for further information about these or an SAP related objects