‎2013 Jul 02 3:38 PM
Hi,
I have a requirement where in I have to achieve some functionality in ME_PROCESS_PO_CUST~POST method whenever there is a change in version relevant fields of a PO. We have EKKO-REVNO to identify if there is a change in version but this will get updated only once before checking the version completion indicator - meaning REVNO will be incremented as soon as I change any version relevant field but will not increment again untill you check the version completion indicator and make any change after that. I have a list of version relevant fields in the table T166C but it has around 65 entries and it is cumbersome process to identify the changes by comparing each and every field. Are there any other ways to identify changes to version relevant fields of a PO like any counter or so? Or any other better approaches?
Thanks,
Hashim
‎2013 Jul 04 11:10 AM
There seems to be no other way than comparing the values of the version relevant fields. Standard SAP is working in similar ways. The include MM06EFDCM has method HAS_PO_RELEVANT_CHANGE that is used in the standard process to check whether there is any change to any of the version relevant fields. I copied and modified the standard code to fit in my requirement.
Thanks,
Hashim
‎2013 Jul 03 1:38 AM
hello,
did you consider CDHDR and CDPOS.
Consider time range also , take update time from CDHDR
for version changes u can get change document number using following condition
OBJECTCLAS = REVISION
OBJECTID = F(PO number)
changes before UDATE and UTIME for these entries belong to previous version
best regards,
swanand
‎2013 Jul 03 7:11 AM
The revision changes are available in EREV table. What is available in CDHDR and CDPOS under REVISION class is changes done to EREV fields.
I am looking for a way to track the changes in any of the version triggering fields of the PO.
‎2013 Jul 03 7:07 AM
Hi Hashim,
Pls refer below 3 tables for more information :
CDHDR - Header Change
CDPOS - Item Change
EREV - Version Change
Regds,
Nilesh
‎2013 Jul 04 11:10 AM
There seems to be no other way than comparing the values of the version relevant fields. Standard SAP is working in similar ways. The include MM06EFDCM has method HAS_PO_RELEVANT_CHANGE that is used in the standard process to check whether there is any change to any of the version relevant fields. I copied and modified the standard code to fit in my requirement.
Thanks,
Hashim