COM error 3 when deleting stock transfer order

[Private_Member_738444]

Hi folks,

The issue is like this:

We do weekly planning run on every fri-sat-sun. It consists of SNP Network Heurisic planning followed by SNP Optimizer.

All SNP engines (HeuristicsOptimizerDeployment Heuristics) are mapped to the entire location-products-versions in 22 nos of jobs having specifications inside their variants.

One of the Optimizer jobs (one particular one out of the 22 nos) has been failing within 200 seconds of its run last 2 weeks. When it is then forced started within 1/2hr, it completes successfully in 8 hrs of run time, which is perfectly ok.

However the question is, why does it fail in the first ocassion? This particular JOB is failing last 2 weeks with the same error message.

I have studied the JOB LOG as well as OPTIMIZATION RUN log, which says the following: (for last 3 weekly failures)

JOB LOG

Job started

Step 001 started ( program /SAPAPO/RMSNPOPT.. variant blah blah....)

Optimization server started

Session number....

User name....

Start time....

Start date...

Component = SNP

COM error 3 when deleting stock transfer order

Job cancelled after system exception ERROR_MESSAGE

Optimization Log

In addition to the above message it also mentions:

Optimizer Internal Error 602 occured

Could you please suggest, whats the reason for this failure?? I had googled & found no relevant solution.

MMTIA

Kumar

Edited by: Blue Lotus on Mar 14, 2011 1:29 PM

[Former Member]

Hi Kumar,

COM error 3 occurs when, LiveCache tries to access an object that has been changed by a different transaction since the start of the current transaction. This usually happens during highly parallel operation on real data.

They can occur when jobs that process the same planning area and planning version are run in parallel, even if the data selection is different. So first please avoid other processing when running the job.

You can also increase the number of reprocesses that will be done with the user parameter /SAPAPO/MAP_REPROCES coming from the note 1311785. The parameter /SAPAPO/MAP_WAIT_SEC should also be set(note 1340205).

Kindly check if the parameters can help you.

Best Regards,

Nithin.