SAP Function Modules

FUT_INT_SAVE_FOR_BAPI SAP Function module - Save in BAPI Mode







FUT_INT_SAVE_FOR_BAPI 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 FUT_INT_SAVE_FOR_BAPI into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FWTR_FUTURES
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FUT_INT_SAVE_FOR_BAPI - FUT INT SAVE FOR BAPI





CALL FUNCTION 'FUT_INT_SAVE_FOR_BAPI' "Save in BAPI Mode
  IMPORTING
    e_company_code =            " bukrs         Company Code
    e_transaction_number =      " tb_rfha       Financial Transaction
  EXCEPTIONS
    INVALID = 1                 "               Error Occurred
    .  "  FUT_INT_SAVE_FOR_BAPI

ABAP code example for Function Module FUT_INT_SAVE_FOR_BAPI





The ABAP code below is a full code listing to execute function module FUT_INT_SAVE_FOR_BAPI 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_e_company_code  TYPE BUKRS ,
ld_e_transaction_number  TYPE TB_RFHA .
. CALL FUNCTION 'FUT_INT_SAVE_FOR_BAPI' IMPORTING e_company_code = ld_e_company_code e_transaction_number = ld_e_transaction_number EXCEPTIONS INVALID = 1 . " FUT_INT_SAVE_FOR_BAPI
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_e_company_code  TYPE BUKRS ,
ld_e_transaction_number  TYPE TB_RFHA .

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FUT_INT_SAVE_FOR_BAPI or its description.