Issue MM PO Archiving

[Former Member]

Hello all,

we had an issue in archiving Purchase Orders.

Frist of all, we have a large number of open purchase orders. Means that the "delivery complete" flag is missing and the "final invoice" flag is missing.

These PO´s cant be deleted.

So these flags have to be set. We created a report which uses ME22N and sets those flags. After this, our issue appeared.

Unfortenally many purchase orders created new messages and send them directly to the vendor. Had a lot of trouble with this.

How can this happen? Why is this flag a indicator for message determination?

How can i prevent this?

I coud set the flags directly on the DB, but our company doesn´t want to make updates direclty on db.

Any ideas?

thanks for help

[Former Member · Accepted solution]

Did you check MN05, if you have any maintained for your PO document type? If so, delete the condition records to automatically trigger the output.

[eduardo_hinojosa]

Hi Christian,

Other idea. If you don't want to change any customizing, you can create your own Outputs routine numbers in VOFM to rule this requirement. In SPRO/ Mat.managament / purchasing / messages / output control / accesses sequence, you can set it and avoid to create the message. See SAP Note 39462 - Expand field catalog in message determination for purchasing to create a new field (for instance, date of PO). You can set a condition to set SY-SUBRC = 4 (ie: output not created) if the difference in days is greater than n days.

I hope this helps you

Regards

Eduardo

[JL23]

any change to a PO will create a message record, if condition records are present (which is usually the case as you want this for a regular change).

However, this message is not outputted, if the change is not print relevant.

What is print relevant is to be defined by you in IMG > MM > Purchasing > Messages > Fields Relevant to Printouts of Changes

[Former Member]

Thanks for your ideas.

I looked for the fields relevant for change message.

ELIKZ and EREKZ are only relevant with MM schedules. The purchase orders which had issue were standard POs.

I don´t find the rootcause. Any further ideas?