Functionality
This method lets you create a future.
The transferred data corresponds to the data in the online transactionunder Structure and to general business transaction data.
The corresponding methods must be used to complete the data entered withdetail screens. This applies particularly to additional flows andpayment details.

Example
Creating a future transaction with BAPIs.
First of all create the transaction by calling Future.Create. Tocreate the additional flow, call FTRAdditionalFlow.Create.Afterwards, call FTRPaymentDetail.Create to create an additionalflow.

Notes
If you set the TESTRUN parameter this calls the BAPI insimulation mode.
To write the data to the database after running a BAPI call in an updaterun (TESTRUN initial), a commit work must be triggered,for example with BapiService.TransactionCommit.
Messages are returned in the RETURN parameter.
A transaction can only be created successfully if the transferred datameets the online transaction consistency conditions. In this case theCOMPANYCODE and FINANCIALTRANSACTION parameters arefilled.
If the data is not consistent or complete it is rejected. In this casethe RETURN parameter contains corresponding messages and theCOMPANYCODE and FINANCIALTRANSACTION parameters areinitial.
Refer to the interface parameter documentation for information about thedata, what is mandatory, optional or depends on the settings inCustomizing, and what default settings exist.
INCLUDE FTR_BAPI_BUKRS_CREATE OBJECT DOKU ID TX
INCLUDE FTR_BAPI_RFHA_CREATE OBJECT DOKU ID TX

Description
An import parameter for transferring the special (for a specific productcategory) value of a future.
This parameter is only evaluated with the Create method if productcategory 700 (future) or 750 (listed option)was assigned in Customizing for the product type entered.
There are three different types of transferring fields:

• Mandatory: An entry is required and there are no system default
settings.

• Optional: An entry is not absolutely necessary. A value is either
not absolutely necessary or there are system default settings.

• Customizable: In Customizing you can define whether the field is
mandatory, optional or not applicable (no entry possible).
For further information about the individual parameter fields, see therelevant data element documentation in the ABAP dictionary.

Default
The fields are defined as follows:
Field Name ,,Field Type ,,Default Value ,,Meaning
SECURITY_ID,,Mandatory,,-,,ID number of future or option
POSITION_ACCOUNT,,Mandatory,,-,,Futures account
POSITION_VALUE_DATE,,Mandatory,,-,,Position date of the transaction
NUMBER_UNITS,,Mandatory,,-,,Number of traded contracts
PRICE,,Mandatory,,-,,Price per contract
PRICE_UNIT,,Optional,,Issue currency,,Price unit
PAYMENT_CURRENCY_ISO ,,Optional,,Issue currency,,Currency of paymentamount as ISO code
PAYMENT_CURRENCY,,Optional,,Issue currency,,Currency of payment amount
PAYMENT_DATE,,Mandatory,,-,,Payment date
PAYMENT_AMOUNT,,Mandatory,,-,,Payment amount
EXCHANGE,,Optional,,-,,Exchange
ORDER_DATE,,Optional,,-,,Order date
BEWEG_ART,,Optional,,According to Cust. ,,Flow type for purchase/sale
LOCAL_AMOUNT,,Optional,,-,,Payment amount in local currency
INCLUDE FTR_BAPI_GEN_CREATE OBJECT DOKU ID TX
INCLUDE FTR_BAPI_TEST_CREATE OBJECT DOKU ID TX
INCLUDE FTR_BAPI_TEST_CREATE_R OBJECT DOKU ID TX
INCLUDE FTR_BAPI_RETURN_TAB OBJECT DOKU ID TX