This method enables you to change data in a transaction that has already been created.
In principle, you can change all structure characteristics that you canspecify when you create a transaction. However, this does not apply tothe company code and transaction number key fields, or the product
type. Neither does it apply to the transaction activity category and transaction type fields in the 'Structure: Money market' and'Structure: Foreign exchange' parameters.
Note the following when you use BAPIs:
To make sure changes are consistent, you must transfer both the new,
changed status as well as the old status of the transaction read by GetDetail when you call it up. You can usea parameter with the same name as the parameter for the old status by adding an 'X' to it.
The system checks whether the last status read using GetDetail is the same as the current status in the database.
If the person calling up this BAPI uses an old status, this changerequest must be rejected. This is possible since you must not blockrequests via several BAPI calls and you cannot prevent another user inthe meantime from changing the status of the database. If this is the case, the only option is to reread the database using
GetDetail and regenerate the change request.
If the status of the database has not changed since the last time it was read, you can post the change request.
The system carries out, however, the usual plausibility checks first.
Messages are returned in the parameter Return. This parameterdocumentation contains the return codes and their meanings.
For more information, see the R/3 Library underProcessing Fixed-Term DepositProcessing Deposit at NoticeProcessing Commercial PaperProcessing a Spot/Forward Transaction
TR Treasury-->Treasury Management (TR-TM) -->Money Market-->Trading and
TR Treasury-->Treasury Management (TR-TM) -->Foreign Exchange -->Trading
in the following sections:
Editing Standard OptionsEditing an Exotic OptionOrder