Functionality This method lets you create a forward volatility agreement. The transferred data corresponds to the data in the online transactionunder Structure and Underlying and to general business transaction data. Add to data entered in detail screens using the relevant methods. Thisapplies particularly to data for conditions, additional flows and mainflows. 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 are filled. If the data is not consistent or complete it is rejected. In this casethe RETURN> parameter contains corresponding messages and theCOMPANYCODE >and FINANCIALTRANSACTION parameters are initial. 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 TXDescription This import parameter contains the activity category to be reversed. See the relevant data element documentation in the ABAP dictionary forfurther information. Description An import parameter for transferring the special (for a specific productcategory) value of a forward volatility agreement. This parameter is only evaluated with the Create >method if theproduct category 780> (forward>) was assigned in Customizingfor the product type entered. There are three different types of transferring fields:
- Mandatory>: An entry is required and there are no system default
settings.
|