How to execute report by using object class for changes in the PR and PO documents
I would like to share my knowledge, to find the changes history for Multiple Po’s and PR’s.
Generally when we need to check any changes happends in Po or PR, we approach the transaction code go display(ex: ME23N for Po) the purchasing document and menu bar environment —-> header changes and item changes. Here we find the changes for only one PO.
If you want to check in table level, CDHDR for header level changes and CDPOS for item level changes. But for some users they don’t have access to check table and some of user they don’t have idea about the Table’s.
In that case they mostly approach the standard reports.Standard SAP they provided report for changes document display with complete information.
Transaction code for changes document display for PO’s and PR’s and other documents also is RSSCD100
T-code : RSSCD100
Object class for PO : EINKBELEG
Object class for PR : BANF
Object class for SES : ENTRYSHEET
Object class for Info record : INFOSATZ
Object class for out bound delivery : LIEFERUNG
Object class for incoming invoice : INCOMINGINVOICE
Object class for Quota arrangements : QUOTEN
Object class for Versions for purchasing document : REVISION
Based on your requirement you can see changes by using object class. if you know Document number you can enter as object ID.
If you want to check item level changes
In out put table key field, displays with item number and if you changes done schedule line then it will show with schedule line. see below screen, in table key field line some of the values showing only client and Po number and some of values showing client and Po number with item number and some of fields showing client and PO number with item number with schedule line number example( 1004500000000000100001).
If you know you can provide from date and To date also. In out put it displays with transaction code.
Hope it is helpful to all.
Dear Moderator,
I know the rules in SDN. I am not seen any where like this document or blog. Some of the people they explained in table level display but i am not seen any where in report form. Please share the document or blog link if it is already exist in the SDN.
If it is already exist extremely sorry, i am not seen like this document before.
Thanks
it is not only that already a blog exists on the same :
http://scn.sap.com/community/erp/blog/2012/02/13/change-documents-for-sap-objects
It is as well that there are 548 discussions from which people could take this info.
Your document is just basic SAP knowledge, nothing new at all.
Share something new, something sophisticated, even something that wraps up complex issues that are frequently asked to stop these endless questions.
But a document that just adds screen shots to an answer that is already given > 500 times in SCN and usually does not need more than 2 sentences does not add any value. And it does not matter if you write it for purchasing documents while the other blog is for material documents. if that would be allowed we would have some thousand similar documents, just one per object.
Write a document or blog about price schema, how to add new conditions, explain the details, tell about condition record, accesses with fields that are not in the fields catalog , how values are flowing into the PO, how the pricing schema is determined. All this together in one document could really add a large value.
Dear Jurgen,
First i am to say very sorry, Really i am not seen this before. I am extremely sorry about this. I know this document is known well for experienced, but I thinking it is helpful to freshers who ever coming to SAP. As my part in MM i explained. And also i am thinking every time to share some beautiful documents to all, i always looking for sharing my knowledge and also i can say strongly, i am not looking for points. I am thinking always Whatever i am sharing my knowledge is helpful to others , and i am not looking for points. Because of i am learner and guider and publisher to share my knowledge.
Sorry for this document. Thank u for your greatest advise.
thanks for understanding.