Ansicht
Dokumentation

/BA1/BAPI_F4_SEV_MODIFY - BAPI for Creating or Changing Securities Volatility

/BA1/BAPI_F4_SEV_MODIFY - BAPI for Creating or Changing Securities Volatility

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

You use this method to create or change security price volatilities.

This method will decide itself if the object in question needs to be created, or updated. This method makes use of the two-dimensional versioning concept, which means that:

- If you want to create an object several times, the system will not issue any error messages (unlike the Create BAPI in the same situation, for example). Instead, a new version is created each time, each with the relevant system date and business date.

- If you go to change an object, but this object does not exist, the system will not issue any error messages, but will instead create an original instance of the object. Compare this to the relevant Change BAPI, which would issue an error message in the same situation.

The object key contains the parameters MDCODE, VOLTYPE, EXTNOUNDERLYING and EXTPRODTYPEUNDERLYING. If the volatility is an implied volatility, the option, which was calculated using the implied volatility, can be specified as well (parameters EXTNOOPTION, EXTPRODTYPEOPTION).

Possible input values are either stored as fixed values in the system, or are checked again the appropriate Customizing settings. Exceptions: For parameters EXTNOOPTION and EXTNOUNDERLYING , the function module checks whether the input values identify financial instruments or financial transactions.

Data is deleted in the system by using a "logical deletion". This is controlled by the STATUS parameter. A new version, which the system flags as logically deleted, is created.

In order to definitively post the data to the database, the user must explicitly execute the CommitWork command (by calling the BAPI_TRANSACTION_COMMIT function module, for example).

The method stores a new version only if the market data value is different from that in the previous version.

Example

Notes

Further information





Parameters

CORRECTIONSERVERACTIV
CUSTOMIZINGSETTINGS
EXTENSIONIN
EXTENSIONOUT
EXTNOOPTION
EXTNOUNDERLYING
EXTPRODTYPEOPTION
EXTPRODTYPEUNDERLYING
MDCODE
PROCESSEXTENSION
RETURN
STATUS
TESTRUN
VALIDDATE
VOLATILITYVALUES
VOLTYPE

Exceptions

Function Group

/SAPLF4_VOLA_BAPI

General Material Data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3902 Date: 20240523 Time: 082925     sap01-206 ( 53 ms )