SAP ALE_FTR_EXERCISE_FXOPTIONS Function Module for BAPI -> IDoc: ALE_FTR_EXERCISE_FXOPTIONS









ALE_FTR_EXERCISE_FXOPTIONS is a standard ale ftr exercise fxoptions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_FTR_EXERCISE_FXOPTIONS 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 ale ftr exercise fxoptions FM, simply by entering the name ALE_FTR_EXERCISE_FXOPTIONS into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_FTR_EXERCISE_FXOPTIONS 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 'ALE_FTR_EXERCISE_FXOPTIONS'"BAPI -> IDoc: ALE_FTR_EXERCISE_FXOPTIONS
EXPORTING
COMPANYCODE = "Company Code
FINANCIALTRANSACTION = "Financial Transaction
* EXECUTIONDATE = "
* CASH = "Creating an FX Option with BAPI
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
* SERIAL_ID = '0' "

TABLES
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "

EXCEPTIONS
ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for ALE_FTR_EXERCISE_FXOPTIONS

COMPANYCODE - Company Code

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

FINANCIALTRANSACTION - Financial Transaction

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

EXECUTIONDATE -

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

CASH - Creating an FX Option with BAPI

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

TESTRUN - Switch to Simulation Mode for Write BAPIs

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

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_FTR_EXERCISE_FXOPTIONS

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

Copy and paste ABAP code example for ALE_FTR_EXERCISE_FXOPTIONS 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:
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_companycode  TYPE BAPI2042-COMPANY_CODE, "   
lv_error_creating_idocs  TYPE BAPI2042, "   
lv_financialtransaction  TYPE BAPI2042-TRANSACTION, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_executiondate  TYPE BAPI2042-END_TERM, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_cash  TYPE BAPI_FTR_EXITE_FXOPTION, "   
lv_testrun  TYPE BAPI2042-TESTRUN, "   SPACE
lv_serial_id  TYPE SERIAL-CHNUM. "   '0'

  CALL FUNCTION 'ALE_FTR_EXERCISE_FXOPTIONS'  "BAPI -> IDoc: ALE_FTR_EXERCISE_FXOPTIONS
    EXPORTING
         COMPANYCODE = lv_companycode
         FINANCIALTRANSACTION = lv_financialtransaction
         EXECUTIONDATE = lv_executiondate
         CASH = lv_cash
         TESTRUN = lv_testrun
         SERIAL_ID = lv_serial_id
    TABLES
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_FTR_EXERCISE_FXOPTIONS




ABAP code using 7.40 inline data declarations to call FM ALE_FTR_EXERCISE_FXOPTIONS

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 COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_companycode).
 
 
"SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransaction).
 
 
"SELECT single END_TERM FROM BAPI2042 INTO @DATA(ld_executiondate).
 
 
 
"SELECT single TESTRUN FROM BAPI2042 INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 


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!