on 10-31-2012 5:50 PM
All:
We have noticed our ORDKEY table (structure /SAPAPO/OM_ORDERKEY_TAB) is steadily growing and all of the growth seems to be confined to Order Type 23 (Safety Stock). This doesn't impact the safety stock values used in the planning books, but it is causing the table to perform poorly. The table itself is not very helpful in terms of identifying what or when an order is for.
Is there a way to delete the unused entries for the ORDKEY table without impacting the ones we need? Shouldn't something in liveCache be doing this automatically or is there a setting we are missing?
Jeff
Did you try running //SDORDER_DEL program in APO to help delete the obsolete orders ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
are you using both SNP and PP/DS?
regards,
J.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are creating safety stock liveCache orders with the relevant PP/DS heuristic (I imagine in a daily or weekly basis), aren't you using the option of deleting previous SS orders before creating new ones? Or you are seeing the ORDKEY table grow but it is not related to existing liveCache orders (PP/DS).
regards,
J.
James,
I think you're onto something. We are using SAP_PP_018 heuristic, with the radio button set to "Create and Adjust Safety Stock Requirements" rather than "Delete Existing Safety Stock Requirements."
Is there a way to have the heuristic do both, or do I need to copy SAP_PP_018 and have it delete the requirements immediately before it generates new ones?
Jeff
Hi,
did you already tried report /SAPAPO/OM_ORDKEY_ORDMAP_CHECK?
Please read post http://scn.sap.com/thread/1396829, may be it will help you clarify your issue. Check also OSS notes regarding that report, just in case.
thanks,
J.
James,
Sorry about the delay in responding -- I have been going back and forth with SAP on this since October. They could not tell me where these orders were coming from, but finally gave us code to delete them. Currently, we are running a regularly scheduled job that deletes all safety stock orders older than 90 days from liveCache. This controls the size of the table without impacting the users.
Since these old orders are not visible in any books/views/boards, deleting them seems to be an acceptable answer. We are still reviewing every job that runs in out system overnight to try to identify what creates these orders.
I'll post if I find the root cause.
Jeff
Hi James,
The OSS Note they gave us is 1807155. We used that as a basis for code we wrote ourselves to add some checks and also to limit the deletions by number of packets. (We had too many orders to delete them all at once.)
Of the 30+MM records, we were able to delete > 27MM in less than two days. We have seen performance on the table improve since then.
Jeff
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.