Entry only in Live cache OM17

[AA3]

we run /SAPAPO/OM17 for Product locations combination, shipments , deliveris and stock  every week for consistency check. Each week we get some inconsistencies for product locations with the message " Entry only in livecache" showing returncode 0.

message error -

Message Number: /SAPAPO/OM_SYNC002

in the details it shows some system generated IDs in the Pegging area column. we tried to look the Pegging IDs in the table /SAPAPO/PEGKEY in column pegging area,  these ID that were detected during the OM17 run are not found even to trace the product -location combinations.

the inconsistencies are then removed by the change option. These inconsistencies return back again.

we tried running all the other consistency check programs but of no use.

Can any one please let us know what could be the source of these inconsistencies , how to track the materials -locations with issues.

[Former Member]

I would be interested if there is any update for this issue.  We are having the exact same issue.  After correcting inconsistencies, the same 500 records show up in the report again the next day.

[former_member229109]

Hello William,

- I recommend to create the new thread for your case.

  And post with liveCache/LCA versions, SCM version, SCM SP on the system.

- Also post what kind of inconsistencies do you have.

- There is 500 limitation on the inconsistencies to be displayed with you could increased.

  Also be careful with the corrections of the inconsistencies reported in //om17.

  Some inconsistencies could be due the parallel running liveCache appl., which changed the liveCache data.

- You have option to open SAP message & get SAP support.

Regards, Natalia Khlopina

[former_member229109]

Hi Ashfaq,

1. Inconsistencies listed as " Entry only in livecache" after run consistencies check will be deleted after you mark them and run correction.

As the pegareas entry existed only in liveCache you will not find them in the table /SAPAPO/PEGKEY of the SCM database.

2. The question on what application created those. I recommend to run the check in //om17 after the job or application/CIF run, which change the product, and see if the inconsistencies reported.

3. Create the SAP message to SCM-APO-MD-PR component and get SAP support/hints to resolve the case.

Thank you and regards, Natalia Khlopina

[tiago_furlanetto]

Hi Ashfaq,

In general, the pegging area is generated in the livecache when orders are first created and saved for a given Location-Product (e.g. via heuristic or manually in an interactive transaction).

Are you using non-standard functions to create orders in SCM? Are you creating some SNP orders with macros in the background?

If yes, including a call to FM /SAPAPO/DM_PEGID_COMMIT as a last step may help as this FM is responsible for saving new pegging areas into the database (so they would exist both in the database and in the liveCache).

Regards,

Tiago

[former_member188883]

Hi Ashfaq,

Could you check SAP note

1357939

OM17: Correction creates inconsistencies in /SAPAPO/VSCC

Hope this helps.

Regards,

Deepak Kori

[AA3]

i did check this note earlier , it is for a lower release compared to our  current (701).

we are getting this error for product-location combination option in OM17.

[former_member188883]

Hi Ashfaq,

Suggestion would be to raise OSS message and keep SCN thread posted with the solution.

Regards,

Deepak Kori