/SAPAPO/OM11 Transaction

[Former Member]

When a consistency check is run using the /sapapo/om11 transaction, where would the output go other than to the screen? Is it stored on the file system? Our application team would like to schedule a weekly consistency check and we may need to do a cleanup if it writes to a file system.

Thanks

And Please Advise

[Former Member]

Thanks for the help.

[former_member229109]

Hello John,

• You could run the internal inconsistencies checks using TA /n/sapapo/om17 on SCM/APO system.

• Using the TA /n/sapapo/om11 you could display LCA logging log, where the

the important liveCache applications events will be listed. One of the events is

"Cons Check"; you will see when it was running, for which objects & more …

It will not give you more details as in //om17 screen.

• In general there should be no inconsistencies on your APO system.

You could schedule a weekly consistency check in //om17 in background & then review the

background job's logs in //om17.

All inconsistencies, which are found on your system, have to be reviewed

manually in order to determine whether they are inoffensive or not. If

you are not sure what to do with an inconsistency reported by transaction

/SAPAPO/OM17 or why they occurred, please open an OSS message

concerning this.

• Please review the document at

service.sap.com/liveCache -> Best Practices for Solution Management: mySAP SCM

-> Data Consistency for SAP APO (3.x) / mySAP SCM (4.x/5.0) (PDF)

Thank you and best regards, Natalia Khlopina

[Former Member]

Natalia,

I forwarded your message to our developers. There response is as follows:

What we don't know how to do is to clean up the resulting log file / output from the OM11 transaction. We want to do this so we don't end up with tons and tons of entries.

How do we claen that up?

Thanks

[former_member229109]

Hello John,

-> First of all you should not have "tons and tons of entries" in //om11. If you have to many events, please create the OSS message to check your system.

-> And on the DEV/QA system you could clean the too old entries using TA //om12. Please be careful to give "Delete to Date" value.

I recommend to keep the LCA log's events on the PROD system for the longer period of time.

If you will clean the LCA log's events it will be difficult to do the analysis of some reported LCA problems. And in some cases like to find the reason of the lost data in liveCache may be not possible, if you will delete the LCA log's events.

Thank you and best regards, Natalia Khlopina

[Former Member]

Natalia,

You refer to LCA log's event? Not quite sure what you mean by that. Is it stored on a file system. This maybe what we are trying to track down as far as the cleanup is concerned.

Please Advise as to where the location of the LCA logs are located.

Thanks

[former_member229109]

Hello John,

You asked ::

"What we don't know how to do is to clean up the resulting

log file / output from the OM11 transaction. We want to

do this so we don't end up with tons and tons of entries."

You wrote about TA::

/SAPAPO/OM11 to display liveCache Application Loging

&& I wrote about TA::

/SAPAPO/OM12 to delete liveCache Application Loging

?? "with tons and tons of entries"

Do you have them in TA //om11?

Recommended: Don't delete the needed entries in //om12 on the PROD system.

That's all.

Thank you and best regards, Natalia Khlopina