Delete entries in POSMAPN with SDORDER_DEL

Delete entries in POSMAPN with SDORDER_DEL
------------------------------------------

GATP -unable to delete Old deliveries in APO

Surprising /SAPAPO/OM_DELETE_INCON_ORDERS is not helping with your issue.

It is a program to delete hanging Sales Orders and Deliveries in APO. The input is the GUID and you have to check all 3 check boxes.

I suggest please try below reports again. I had faced similar issue and was able to resolve it.

1. Report /SAPAPO/SDRQCR21 (using transaction SE38)
Run the report for the material & plan with the option "Build Requirements from Document Flow" and the indicator "Check SD Order Tables" and correct any errors found.

2. Try /sapapo/sdorder_del
"Reconcile Available-to-Promise (ATP) tables with /SAPAPO/POSMAPN"
"Delete obsolete records in the /SAPAPO/POSMAPN table"
Take into account that runtime can be long running the report this way.
also check note "SAP Note 894294 - /sapapo/sdorder_del: Performance and advice (as of SCM 4.0) ".

3. Report /SAPAPO/CIF_DELTAREPORT3 (using transaction SE38)
Run the report with the indicators "Sales Orders" and "Check Table VBBE" and correct any errors found.

4. In addition, don't forget to clean out all temporary qty assignments, too (/SAPAPO/AC06, 'Product availability' block, all four types).

https://archive.sap.com/discussions/thread/3404527

--

/SAPAPO/SDORDER_DEL program long runtime issue

We are experiencing long runtime with program /SAPAPO/SDORDER_DEL when we run with below options ticked

- Adjust ATP Tables with /SAPAPO/POSMAPN

- Delete Obsolete Records in the /SAPAPO/POSMAPN Table

A single instance of this job runs weekly for all locations. The runtime is typically 8 to 10 hours.

In order to reduce the runtime, we want to split the job into multiple instances and run it parallely for blocks of locations. i.e. I have 50 locations in my system and I want to run 5 instances of this program in parallel each with 10 of the locations.

Do I need to have the below two ticks only in one of these variants or I can have them in all 5 variants?

- Adjust ATP Tables with /SAPAPO/POSMAPN

- Delete Obsolete Records in the /SAPAPO/POSMAPN Table

I was referring to the note

Note 894294 - /sapapo/sdorder_del: Performance and advice (as of SCM 4.0)

This note says below:

At least for the first time you run the report, we recommend that you run it several times in succession using the following parameters:

1) "Selective deletion" with a corresponding selection of product, location and so on, it may also be necessary to run it in blocks according to product and/or location.

2) Use /SAPAPO/POSMAPN to compare ATP tables

3) Delete obsolete records in the /SAPAPO/POSMAPN table

If, however, you split the 'Selective deletion' option into selection blocks of products and/or locations, note that the other options (2 and 3) are independent of this split. Ensure that these options (2 and 3) are processed only once in each case.

Can somebody help me to understand how to use the options (2 and 3) in multiple parallel instances of the program /SAPAPO/SDORDER_DEL?

--

1) We have created a background job with 3 steps in it.

2) Step (1) has a variant that has all the plants entered in the tab "Delete on Database" and none of the check boxes were selected except the last one "Log deleted items".

3) Step (2) has a variant that has all the plants entered in the tab "Delete on Database" and select the check box "Delete Obsolete Records in the /SAPAPO/POSMAPN table and the last check box "Log deleted items".

4) Step (3) has a variant that has all the plants entered in the tab "Delete on Database" and select the check box "Adjust ATP tables with /SAPAPO/POSMAPN" and the last check box "Log deleted items".

Most importantly in all the steps, enter Last changed before date "3 months or 4 months old" depending on your project requirement.

https://archive.sap.com/discussions/thread/3422967

--

Delete entries in /SAPAPO/POSMAPN with /SAPAPO/SDORDER_DEL

we´re having many orders in table //POSMAPN that are not existing in liveCache.

We assume that these are obsolete orders that can be deleted with report //SDORDER_DEL.

My question:

What is the prerequisite for orders being deleted from //POSMAPN with //SDORDER_DEL?

Or in other words: Which entries in //POSMAPN are considered as "obsolete" by //SDORDER_DEL?

When you run the /SAPAPO/SDORDER_DEL program, you should run the program to delete the orders from both Live Cache and Database ( see the 2nd tab on the selection screen of this program). This way you can ensure that it is deleted properly. Otherwise, when you run //CCR or //SDRQCR21 it only checks the livecache. Since, it has already been deleted in your case, you can give it a try to see if you can delete the orders from DB using option "Delete from DB" ( see the 1st tab).

Also, usually the order gets disappeared from LC once the order is PGIed, however a bit of information is still available on APO side and thats where this program would delete it to counter that. The reason why the order line info is still stored in APO is due to the fact that the order lines can always be reverse PGIed and the delivery can also be deleted. So, it is a wise option to run this program by providing the Period in the selection screen which is usually the MBDAT and as a regular practice you can provide a date range that is less than 90 days or so.

https://archive.sap.com/discussions/thread/3537123

--