Migrating of Old Purchase Orders to new SUS system

[Former Member]

Dear Experts,

          Are there any specific restriction or concern over  transferring of old Purchase Orders of a vendor to the freshly implemented SUS system?

This is related to the (MM-SUS) scenario where the company has running SAP MM system and a new SUS system is installed and existing Vendors are transferred to SUS system. What happens to the old POs with Purchase Order history that are not there in SUS.

The below behavior is observed:

1. When existing PO with GR is changed a XML is triggered and PO is sent to SUS system. However the PO has no buttons for create ASN or SErvice entry sheet.

Any input on precautions to be taken in the above situation (Old SAP MM and new SUS) before Going Live is welcome.

Regards,

Vardhan

[zoltan_keller · Accepted solution]

Hi Vardhan,

old purchase order cannot be processed with SUS in this scenario. It is because only the PO can be replicated to SUS but none of the existing follow-on documents. So the whole purchase order history will not be available on SUS side, only on MM side, which will lead to inconsistent quantities and documents. If you use SUS to handle a PO, then all follow-on documents must be created in SUS to prevent such inconsistencies. This is not assured if you transfer an old PO to SUS.

regards

Zoltan

[Former Member]

Hi Vardhan,

The "Acknowledgement Required" flag needs to be set on the line item in order for the PO to get the "Process" button in SUS. When we SUS-ify an existing ECC vendor, I pull a list of all open PO line items for that vendor that have no GR or IR, and then do a mass update to add the confirmation control key and acknowledgement required flag.

As Zoltan mentioned, I don't do this for lines where there's a PO history. You can't add confirmation control key to these lines.

Regards,

Seth