COM error 40134

[Former Member]

Anyone come across COM error 40134 in Interactive Planning ?

[error message /sapapo/om102]

SCM version 5.0 hotpack SAPKY50007

[Former Member · Accepted solution]

IIRC this error occurred after we refreshed the UAT environment from production, because the UAT system was still trying to update the Production livecache !!

[despite the relevant config in transaction LC10 pointing to the UAT livecache.. ]

Bounced the UAT livecache server, problem went away .....

[Former Member]

Hi Collin,

You can check your error in Tcode ST22, here you have a more explained cause of the error.

I hope this helps you.

Regards.

Marín.

[Former Member]

Hello Colin -

Take a look at the following OSS note: it might be related to your error message.

564360 or 389891.

Hope this will be of help. These above mentioned OSS notes are talking about

"Implement the program corrections."

Regards,

Suresh Garg

[Former Member]

Hello Colin,

We also have the error for COM routine using application program (return code 40.134) in Interactive Planning, during load selected data into Planning Book.

SCM version 5.0 Support Package SAPKY50006

Do you have already a solution for this problem?

Regards,

Diane Bonhomme

[Former Member]

Please do the Consistency check for Planning Object as well as Time series level

For Planning Object structure Consistency check use program - <b>/SAPAPO/TS_PSRU_CONS_CHECK</b>

For Time series use Program <b>/SAPAPO/TS_LCM_CONS_CHECK</b>

Or you can use menu path

Advanced Planning and Optimization --> APO Administration --> Consistency Checks --> Demand Planning

/SAPAPO/PSTRUCONS - Consistency Check for Planning Object Structure

/SAPAPO/TSCONS - Consistency Check for Time Series Network

Please run this transaction in the same series, i.e 1) /SAPAPO/PSTRUCONS - Consistency Check for Planning Object Structure

2) /SAPAPO/TSCONS - Consistency Check for Time Series Network

I hope after the Upgrade you have activated your Infocubes/infoobjects and the PA

Check these are properly activated or not.

I hope these will solve your error.