GOA Contract log wrong

Question

Hi
For eg i change GOA one piece of data now change version created.
now the log says display change document says.
buyer1 :- changed the target value old value 100 new value 200
approver1 :- changed the target value old value 100 new value 200.
really buyer1 only changed the GOA.
why SRM logs shows both are changed the data.i.e Approver1 also changed that data. it is wrong. really purchaser1 has changed the data. Why SRM log shows as Approver1 also changed the data. srm should shows only approver1 approved the GOA.
can any one confirm this in your system ? are you facing the sae problem.
Steps to recreate the problem
(1) Create A GOA , release the GOA and approve the GOA and make ensure that it reached ECC system.
(2) now change the same goa with some data,   and release the GOA and approve the GOA .
now you can see the change log .
Is your system also behaves the same?
========================
Note 1294143 - Wrong approval data displayed
Summary
Symptom
You archived a Purchase Order, Contract or Bid Invitation, and later archived the related approval work items.
When you display the approval data of the archived document, the first approval is shown, but in the case of documents that have a change version, the approval of the latest released change version should be shown.
Other terms
archiving, versioning, approve, work item, approval preview, bid, PO, BBP_POR, BBP_CTR_MAIN, BBP_BID_INV
Reason and Prerequisites
Reason - the workflow linked to the active version is saved with the archived document.
Solution
Please implement this note or the relevant Support Package.
With this note, the workflow for the last closed change version is saved to the archive, and used if the archived document is displayed.
Header Data
Release Status: Released for Customer
Released on: 08.05.2009  10:05:19
Master Language: English
Priority: Correction with high priority
Category: Program error
Primary Component: SRM-EBP-ARV Archiving
Secondary Components: SRM-EBP-BID Bid Invitation
SRM-EBP-POR Local Purchase Order
SRM-EBP-CON Contract Management
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
SRM_SERVER 550 550 550
WILL THIS NOTE  FOR ME? I AM SRM 550..
BR
Muthu

Answer 1

Maybe I could take a stab at explaining the situation you encountered.
The "change history" is based purely on the DB table entry changes defined at DDIC level. (The base of it is not part of SRM but part of BASIS). So the change log you see is SRM's presentation of the change document tables, such as CDHDR, etc. My guess to your case is that the purchaser is changing the "Change Version" of the document (version type C) during change and save/release while the approver is changing the "Active version" of the document, which is a different table entry from DB's point of view entirely (version type <space>) during approval, even though with the same change content. You should not have seen the exact same change content by two different persons in the same document version. But with different versions of the document, it is possible and your case.