idoc not Updating for message type ORDRCHG for PO changes

[Former Member]

Hi everyone,

I am currently facing an issue of idoc not updating for message type ORDRCHG when there are any changes in the Purchase Orders in SAP ECC (RP2) system. I am sending PO from ECC to SRM system.

Although the schedule gets updated in the Scheduling Agreement (SA) when DELINS message type is triggered from ECC system and the same gets update on SRM system. Where as if there is any change in PO (eg PO price ammendment / deletion block / release block ) these are not getting updated on SRM system.

[Former Member]

Hi Vaibhav,

Have you able to creating the outbound IDOC for your changes?

If not go to the BD50  check the message type is added for change pointers

check in BD52 - ORDCHG is added the change pointers for required fileds!

I think you have to be defined which fields the change pointers needs to be triggered to create the IDOC!

Finally check the BDCP2 table is writing the change log or not?

[vinita_kasliwal]

Hi Vaibhav

just for my understanding I wanted to know How is the information flowing through IDOC is it not supposed to flow through XML ?

[Former Member]

Hi Vinita,

Yes the information will flow through XML. But any changes in the PO are not trigetting the IDOC.

No IDoc is generated with the EDI outbound processing of the respective purchase order and in the log of the message output, the system generates error message ME760: "No IDoc items belonging to purchasing document found".

[vinita_kasliwal]

Hi Vaibhav

Can you please check the notes below and see if it works well for you?

Note 202667

Note 641505 - EDI ORDCHG: No IDoc created; message ME760

[Former Member]

Check following path in SPRO.

Materials Management -> Purchasing -> Messages -> Fields Relevant to Printouts of Changes

Documentation says

In this step, you define:

Whether and in which purchasing documents a field is relevant to change notices.

The customizing made here is stored in t166c.

check function module IDOC_OUTPUT_ORDCHG PERFORM lesen_beleg.

It reads PO changes using FUNCTION 'ME_CHANGES_READ' and then evaluates if they are relevant for triggering IDoc. This program is comparing table entries in t166c and changes from CDHDR.

I think this is how application finds out if fields are relevant for changes.   

So the summary is check if you have configured the change relevant fields for PO and are those fields getting changed in PO.

P.S: I haven't gone through the notes mentioned by Vinita.