Reply from Typewriter on May 26 at 9:41 PM Stephan,
Thank you for your interesting post!
Stephan, Devinder,
When changes are done in a sales order (any kind of change e.g. pricing or non pricing), it can be seen in CDHDR and CDPOS via the sales order number (and OBJECTCLAS VERKBELEG), then why go to COND_A and then come all the way back to the sales document (sales order)?
Also a change done in a condition record may or may not be "used" in a sales order.
| | | ---------------Original Message---------------
From: Stephan Thomas
Sent: Friday, May 25, 2012 7:35 AM
Subject: Sales Order Change History Report from CDHDR Table
Hi Devinder,
Suggest you could try following:
Search CDPOS with OBJECTCLAS = "COND_A" to get pricing changes
Join CDPOS to CDHDR and select against user, date etc for CDHDR to narrow down the changes of pricing conditions only to the selected user and date range.
Join CDPOS-OBJECTID to KONP-KNUMH which finds the pricing record(s) changed via the internal number KONP-KNUMH.
You then join KONP to KONV via KONP-KNUMH = KONV-KNUMH. This will give you all the document condition numbers to which the changed pricing records have been applied.
KONV can then be joined to VBAK (or VBRK) to give you the document numbers by joining using KONV-KNUMV = VBAK-KNUMV.
But worth looking at AUT10 - it's a very useful report for change tracking, and for one-off reporting you can often use AUT10 to find the records, export to Excel, then do second stage lookup in SE16N with the excel entries.
Stephan |
| Reply to this email to post your response. __.____._ |   _.____.__ |
No comments:
Post a Comment