topic Re: CHANGEDOCUMENT_READ in Application Development and Automation Discussions

CHANGEDOCUMENT_READ

Former Member — Tue, 15 Sep 2009 05:38:44 GMT

Req:

While creating condition records through VK11, if we maintain scale prices as well, the entries that get stored in CDHDR and CDPOS are wrt to new entry only and not reflecting KONM table with scale prices.

However, when we change scale prices in condition records through VK12, the changes are captured as old value and new value in CDPOS table.

Now the requirement is that user wants to report scale prices data even when they are creating the new condition records. And using FM u2018CHANGEDOCUMENT_READu2019

Or u2018CHANGEDOCUMENT_READ_HEADERSu2019 is not capturing the scale prices data as explained above.

Any pointers for this are appreciated.

Probable Solution:

Do the coding after CHANGEDOCUMENT_READ and read the table (structure CDRED) with tcode VK11 and read the data from KONM table.

Modify internal table accordingly and let the rest of processing go on.

If you find any solution better than this usual brute-force method, please advise.

Thanks in advance !

Re: CHANGEDOCUMENT_READ

Former Member — Tue, 15 Sep 2009 07:49:08 GMT

Hi,


if we maintain scale prices as well, the entries that get stored in CDHDR and CDPOS are wrt to new entry only and not reflecting KONM table with scale prices.

is it the new condition records maintained are not getting updated in KONM table

Can u specify which condition type u r using ..

if u r able to retreive the new records maintained from KONM ,thn the probable solution u specified wud work..

Regards,

Mdi.Deeba

Re: CHANGEDOCUMENT_READ

Former Member — Tue, 15 Sep 2009 09:06:00 GMT

Yea it is the new condition record scale prices that are not reflected in Cdhdr and cdpos tables.

This is not condition type dependent. It is occuring for any condition.

Regards,

Shreya

Re: CHANGEDOCUMENT_READ

Former Member — Fri, 25 Sep 2009 05:13:35 GMT

There was no work around possible for this issue.

So the only solution is to add the required entries programmatically in desired internal table of type CDRED.

This only has solved the problem.

Thanks,

Shreya