You can use this BAPI to change data in a security that has already been created. In principle, you can change all structurecharacteristics, as well as secondary indexes, references, exchange assignments and conditions.
When you use this BAPI, note the following:
To ensure changes are consistent, you have to transfer both the new,changed status as well as the old status of the security 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. The status can be old because you are not
allowed to block requests over several BAPI calls and you cannotprevent another user in the meantime from changing the status of thedatabase. If this happens, the only option is to reread the database using GetDetail and to 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 the usual plausibility checks first.
If you only want to change the conditions of a stock, you simplytransfer the import parameters SecurityNumber, ProductCategory, Stock, StockX and the table parameters Conditions and ConditionsX.
Messages are returned in the parameter return. The parameterdocumentation shows the return codes and their meanings.
For more information, see the R/3 Library under Treasury-->Treasury Management-->Securities-->Master Data-->Class.