We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!
This method is used to create or change interest spreads
The method decides itself whether the object entered is created or updated. In the context of the two dimensional version concept of the SDL, this has the following effect:
- If an object is to be created several times, no error is created, as is the case for the Create BAPI. Instead, a new version is created with the relevant system and business date.
- If an object is to be changed even though it does not exist yet, no error is created and the object is created. The corresponding Change BAPI would create an error.
The object key consists of the parameters MDCODE, REFRATE and SPRDTYPE.
The possible input values are either saved as fixed values in the system, or are checked against any Customizing settings.
Deletion in the system is by "logical deletion". This is controlled by the STATUS parameter. A new version is created, which is flagged as logically deleted in the system.
To finally transfer the data to the database, the user must trigger a CommitWork command explicity, for example, by calling up the BAPI_TRANSACTION_COMMIT function module.
The method only stores a new version if the market data value differs from the previous version.
This method is not relevant in Account Management (component FS-AM).