In APO what does the OM17 Transcation code

[former_member790046]

Hi all

could you please explain in APO what does the

Transaction code /n/SAPAPO/OM17,at what purpus it will be used,

Thanks & Regard

R.Suresh Kumar

[Former Member · Accepted solution]

Hi Suresh,

OM17 transaction is specially meant for live cache consistency check.

Mostly used for checkiing & rectifying the inconsistency present in the APO

in SNP we get master data from R/3 and some times there is inconsistency seen, master data in R3 not matching with that of APO.

In such cases Om17 is run to check the inconsistency in stock, times series, planning versions, master data etc.

There are options vailable where iin you need to select what all should be checked.

Link: http://scmgmt.blogspot.com/2010/06/note-425825-consistency-checks.html

Through above link you will get details on various consistency checks that can be done.

Hope this information helps.

Regards,

Chetana

[former_member790046 · Accepted solution]

Hi chantan

thanks yaar for your help,it will understanding

regards

suresh

[Former Member]

Hi Suresh,

OM17 is the transaction which is monitored and controlled by

internal BASIS team for livecache performance.

In general, if we have typical movement of data between

livecache and database, there are normally inconsistencies

tend to happen.

This transaction is the systematic way of locking all users and

queue systems and carrying out the consistency of data

and corrections.

This can be performed by BASIS team at regular intervals as

desired.

Hope it is clear now.

Regards

R. Senthil Mareeswaran.

[former_member790046]

Hi senthil

thanks yaar for your help,it will understanding

regards

suresh

[Former Member]

Hi Suresh,

Consistency refers to the consistency between the liveCache data and the APO database.

Inconsistencies may occur if the APO database data or the liveCache data can no longer be completely restored due to system crashes and inappropriate backup strategies.Since there is currently no logging for Demand Planning data, inconsistencies can still occur in this area following a recovery.To check the external consistency between the APO database and the liveCache and to set it up again, if necessary, use transaction /SAPAPO/OM17.

The following data is checked in particular:

Pegging areas, stocks, campaigns and planning versions are checked.

Master data:This data is saved redundantly in the APO database and in the liveCache, this means that data which is only on the APO DB, can be generated in the liveCache.If data still only exists in the liveCache, you can select this for deletion.

No resources are checked.The 'Resources' option is provided in older versions of the /SAPAPO/OM17 report.

Regards,

MJ

[former_member790046]

Hi joshi

thanks yaar for your help,it will understanding

regards

suresh