cancel
Showing results for 
Search instead for 
Did you mean: 

"Error for COM routine using application program (return code 1028514-)"

Former Member
0 Kudos

Hello Experts,

We have one issue in SAP SAP SCM 5.10.

When we are accessing the SNP Planing book, Now a days every often we are getting kicked out of the Planning book

with the error message "Error for COM routine using application program (return code 1028514-)"

How to rectify this,..Please advice /suggest

Regards,

Ramesh

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ramesh,

Always give it a try to run consistency check when you are facing any error in planning. Try the following programs-

/SAPAPO/TS_LCM_CONS_CHECK

/SAPAPO/TS_LCM_REORG

/SAPAPO/TS_LCM_PLOB_DELTA_SYNC

/SAPAPO/ADMIN_MVIEW_CONS_CHECK

/SAPAPO/MCPSH_GEN_SETLAB_CHECK

Regards

Manotosh

Former Member
0 Kudos

Hello,

We have performed all the below mentioned actions to rectify the COM Error

/SAPAPO/OM17

/SAPAPO/CONSCHK

/SAPAPO/TS_LCM_CONS_CHECK

/SAPAPO/TS_LCM_REORG

/SAPAPO/TS_LCM_PLOB_DELTA_SYNC

But still error is appearing ...

Thanks

Ramesh

Former Member
0 Kudos

Hi,

We had a similar experience.

The reason was SQL error in the program. We came to know this after debugging.

I would suggest to take the help of an ABAP resource to understand if it is caused due to an SQL error or not.

Regards

Manotosh

former_member187488
Active Contributor
0 Kudos

Hello,

Please refer to the blow page for liveCache error -28514.

https://wiki.wdf.sap.corp/wiki/display/lcapps/Error+-28514

You can first try to restart the liveCache if possible.

Please try to avoid staying in /sapapo/sdp much too long, and loading too much data.

Best Regards,

Ada

Former Member
0 Kudos

Hi Ada,

Given link https://wiki.wdf.sap.corp/wiki/display/lcapps/Error+-28514 - is not working. could u pls provide it

Thanks,

Ramesh

former_member187488
Active Contributor
0 Kudos

Sorry, I copy the content as below:

Error -28514

Version Not Found

You attempted to access an OMS version, the liveCache infrastructure to store a Simulation Version, which does not exist (any longer).

On a productive system this error should only occur in exceptional situations because liveCache checks whether the simulation exists beforehand and returns an Error 17831 if this is not the case.

Reasons (=exceptional situation) for an error -28514 are:

a transactional simulation (Simulation Version) is older than liveCache parameter MaxRetentionTime (default: 8 hours). In this case, the OMS version (more precisely: the corresponding consistent view) can be deleted (asynchronously) by liveCache and an error -28514 will occur if the application tries to use the transactional simulation again.

a transactional simulation (Simulation Version) is older than liveCache parameter MinRetentionTime (default: 1 hour) and the data area usage exceeds 90%. In this case, the OMS version (more precisely: the corresponding consistent view) can be deleted (asynchronously) by liveCache and an error -28514 will occur if the application tries to use the simulation again.

If liveCache deletes an OMS version due to one of the reasons above, a corresponding notice can be found in liveCache's knlmsg file (cyclically overwritten!).

Error -28833

Error -28833 ("Consistent view has been cancelled") occurs instead of an error -28514, if the an OMS version is deleted while a parallel liveCache call is still using this OMS version.

Malfunction Test

If this error occurs during LCAPPS internal malfunction tests, it indicates that the preceeding provoked exception has not been handled correctly. During the handling of the provoked exception the OMS version is dropped automatically. As the malfunction test program catches the exception which would normally lead to a shortdump, it either has to recreate the current simulation in liveCache or to ensure that it is not used any more.

Error 17831 does not occur in this situation, because the keyed object representing the simulation (OMS version) is not deleted along with the version and can therefore still be accessed.

Best Regards,

Ada