FTR_OTC_FX_BAPI_INIT SAP Function module - Initialization

FTR_OTC_FX_BAPI_INIT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FTR_OTC_FX_BAPI_INIT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FTR_OTC
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FTR_OTC_FX_BAPI_INIT - FTR OTC FX BAPI INIT

CALL FUNCTION 'FTR_OTC_FX_BAPI_INIT' "Initialization
  EXPORTING
    i_bukrs =                   " bukrs         Company Code
    i_rfha =                    " tb_rfha       Financial Transaction
  EXCEPTIONS
    DEAL_NOT_FOUND = 1          "               Transaction Is Not Available
    NO_AUTHORITY = 2            "               No Authorization
    ACTIVITY_NOT_POSSIBLE = 3   "               No Processing Possible
    DATA_INCOMPLETE = 4         "               Data Is Incomplete
    WRONG_PRODUCTTYPE = 5       "
    WRONG_TRANSACTIONTYPE = 6   "
    WRONG_FLOWTYPE = 7          "
    ERROR_MESSAGE = 8           "
    WRONG_PRODUCTTYPE_UNDERLYING = 9  "         Producttype of underlying is wrong
    .  "  FTR_OTC_FX_BAPI_INIT

ABAP code example for Function Module FTR_OTC_FX_BAPI_INIT

The ABAP code below is a full code listing to execute function module FTR_OTC_FX_BAPI_INIT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_i_bukrs) = 'Check type of data required'.

DATA(ld_i_rfha) = 'Check type of data required'.
.

CALL FUNCTION 'FTR_OTC_FX_BAPI_INIT'
  EXPORTING
    i_bukrs =                    ld_i_bukrs
    i_rfha =                     ld_i_rfha
  EXCEPTIONS
    DEAL_NOT_FOUND =             1
    NO_AUTHORITY =               2
    ACTIVITY_NOT_POSSIBLE =      3
    DATA_INCOMPLETE =            4
    WRONG_PRODUCTTYPE =          5
    WRONG_TRANSACTIONTYPE =      6
    WRONG_FLOWTYPE =             7
    ERROR_MESSAGE =              8
    WRONG_PRODUCTTYPE_UNDERLYING =    9
    .  "  FTR_OTC_FX_BAPI_INIT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 7. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 8. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 9. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_i_bukrs
 
 TYPE BUKRS ,
ld_i_rfha
 
 TYPE TB_RFHA .


ld_i_bukrs = 'Check type of data required'.
ld_i_rfha = 'Check type of data required'.