liveCache COM routine ended with own error code 40

[Former Member]

Hi Seniors,

While demand is getting released through program: /SAPAPO/RTSOUTPUT in back ground, getting the following error:

liveCache COM routine ended with own error code 40

We unable to recreate the same error in Quality System

In forum for error code 40, no post is available

Please help

[RahulHanda]

Hi Ramana,

Take a consistency check (DP time series) in /SAPAPO/OM17. Try to release the same thereafter. Did you already tried the same in foreground?

Regards

Rahul

[Former Member]

Hi,

consistency check is built into process chain as a previous step before demand release

[RahulHanda]

Hi

Did you try doing yourself to see any issue? In process chain you might have /SAPAPO/TS_LCM_CONS_CHECK but not sure whether it's repairing also. Also cross check in OM17. It's no harm in checking no matter you have in PC.

Regards

Rahul

[Former Member]

Hi,

The consistency check is calling - /SAPAPO/TS_LCM_CONS_CHECK in back ground

with following enabled:

Repair

Lock Planning Version

Check liveCache Anchor

Check SNP Master Data

Extended DP BOM Check

[RahulHanda]

Ramana

I get you that you have maintained job, but did you try doing the same? Not sure why are you hesitating in doing so. Did you check OM17?

These are the checks done by /SAPAPO/TS_LCM_CONS_CHECK

• Storage buckets profile check
• Key figure initialization horizon check
• Time series initialization horizon check
• liveCache anchor check and time series check
• Extended check of liveCache anchor

OM17 checks for DP time series:

• Superfluous check
• Technical check in liveCache
• Check objects which need to be updated

At least check so that you don't have any issue there.

Regards

Rahul

[Former Member]

hi,

We have tried all types of cons checks,as it is on real time solve, so that planning results are released to Business to meet SLA's

our team, on iteration, excluded products from /SAPAPO/RTSOUTPUT one by one,

and executed it manually from SE38, finally arrived at one

If we exclude this particular product, the demand gets released

However, with same products for a different solve which works on different version, not encountering any error

We compared the masters of this product with others, do not find any difference

Please help with any clues

[RahulHanda]

Hi Ramana,

Did you do product-location combination check in OM17 (though you already mentioned various checks have been done but still pointing out the same)?

While releasing are you using consumption group? Check if you maintained it correctly though logically it gives different message if it's not maintained. Also check if you multiple consumption groups with different PA's this might be an issue (if wrongly assigned).

Regards

Rahul