Delivery which is shipped back in 2011 still exists in APO.

[Former Member]

Hi ,

ZREP# 861389 was shipped back to 2011 June(Closed Order - Delivery) but still exists in APO, what could be the reason for it.I am trying to reproduce this issue, but not able to do it. What could be the reason for this issue?

due to which stocks are not assigned correctly when we do ATP check for other open orders.

I did CCR resolved the issue. but not sure on Root Cause?

Could you please help me out in reproducing it?

Best Regards

Sadeesh

[former_member209769 · Accepted solution]

Hi Sadeesh,

If you have already run CCR and issue is resolved, then it's not a good situation to do root cause analysis now.

There are various situations when inconsistencies happen between APO and R/3 or within APO or R/3. That's why SAP has given so many transactions which could correct these inconsistencies e.g. CCR, deletion of Sales Order in APO, etc.

You can only consider now that the inconsistency MAY have been due to any of the possible reasons (I am listing some reasons, there may be more):

1) GI against the delivery could not reach APO because someone deleted the queue or there was some issue with the queue.

It is also possible that temporarily there was issue in connectivity between R/3 and APO, and queue would have got stuck due to this, which someone would have deleted. The stuck queue could also be due to master data issues.

2) Delivery got closed/deleted in R/3 e.g. manually by someone, but this change could not reach APO due to some reason.

3) Sometimes data in APO could get corrupt, and needs manual action.

If you want to replicate the situation, then you need to reach the delivery stage (see that delivery exists in R/3 and also in APO). Next either block the data transfer between R/3 and APO by blocking the CIF queues, or remove the location-product corresponding to Sales Order from relevant integration model. Or interrupt the connectivity between APO and R/3 in some way. Then when you would do goods issue against the delivery, the change would not reach APO, and you could see an inconsistency. But I would say this is not worth the effort.

The next time when you face similar issue, just do the above kind of checks. Otherwise CCR would take care of issue, so just resolve the issue. This is a simple issue and SAP provides standard solution of CCR, so no need to dig further into it.

Thanks - Pawan

[michael_thinschmidt]

Hi,

You should check also for hanging TQAs. Goto TA /SAPAPO/AC06, leave userid and generation date blank and execute.

Check if you see the entry. If yes, you can delete it.

The standard way to delete old sales order data is report /SAPAPO/SDORDER_DEL. You can enter the delivery number on the second tab and delete it from livecache and database.

best regards,

Michael

PS: further information can be found in my note [1411359|https://service.sap.com/sap/support/notes/1411359]

[Former Member]

Hi,

1) If the order still exists in ECC , then delivery complete checkbox might not have been marked in the delivery document,

2) This is also possible due to CIF error or accidental deletion of LUW carrying the details of these delivery documents

If everything is good in ECC, then this may be an inconsistent order present in the livecache.You will have to delete this order from the livecache

/SAPAPO/OM_DELETE_INCON_ORDERS

Also try running /sapapo/om17 report to check database-livecache consistency.

Thanks

Amit