How to change the message value in COGI entry

Question

Hi All,
I have two COGI records on a material for a plant and while creating those entries those were locked by another user.  So it is getting message number as 897 and so it is not displaying in the report COGI.
Could anybody tell me, how to remove that message.
Thanks,
sreenivas.

Answer 1

Sreenivas,
You need to Implement the corrections mentioned in SAP Notes #325105.
Solution as given in note
Both incorrect goods movements and future change records for background processing of goods movements are stored in table AFFW. Error records differ from future change records by the fact that fields AFFW-MSGID and AFFW-MSGNO are filled (error ID and error number). Process requests can only be updated via reports CORUAFW0, CORUAFWP, CORUPROC or Transaction CO1P. Error records can be updated in Transaction COGI. They are also transferred to the update, provided you executed reports CORUAFWP or CORUPROC with the "Incl. incorrect goods movement" indicator set.
In table TAFWD, you can enter specific error messages which should not be treated as an error record but as process requests.Useful candidates for such error messages are, for example, locking errors such as M3897:"The plant data of the material <XXX> is locked by the user <YYY>." You can maintain TAFWD entries by using Transaction SM31.
AFFW records with errors which are entered in table TAFWD are no longer displayed in Transaction COGI (because they have been defined as a future change record) and can only be edited for the background processing by the programs and transactions.
You can limit the error records to specific error messages in Transaction COGI by adding certain error messages to table TAFWD.
Technically, the conversion of error records into process requests decreases the time and effort spent on lock management because only the respective process (background updating of goods issues and/or goods receipts) is locked during the update of process requests.However, error records are locked separately in order to prevent other users from affecting a record which is just being updated/processed.
The following applies to postprocessing records from the repetitive manufacturing:
As of Release 4.5B, these records can also be posted via transaction COGI (in addition to the repetitive manufacturing programs for postprocessing backlogs: Transaction MF47, report RMSERI13). However, basically they should NOT be posted using reports CORUAFWP and CORUPROC, including not with the "with incorrect goods movements" indicator set.
Therefore, the definition of phantom errors in table TAFWDfor postprocessing records from the repetitive manufacturing has no effect. These records can not be redefined for future change records and must still be able to be postprocessed explicitly via transaction COGI.
Regards,
Prasobh