CPP error Record with Batch(Version) for product does not exist

[Former Member]

Hi All,

Everyday we are getting CPP records with message Batch(Version for product does not exist for stock batches when we post process records those are getting transfered but we want to know root cause to avoid any stock inconsistency. Error is happening when Good recipt, then clearing from quality stock to unrestricted and few goods movement happen one after another without much time gap. I could see one OSS note with same message but it is not relevant for our release.

Anyone faced this issue and any solution or pointers to resolve this

Regards,

Santosh

[rupesh_brahmankar3 · Accepted solution]

Hello Santosh,

Version (batch) XXXXX does not exist.

The cause for this issue is that the stock is being processed before the batches are updated in APO.

In order to guarantee the correct sequencing, two solutions are possible:

1.  To separate the stocks and batches in different integration models, respecting the Batch -> Stock sequence in the activation.

2. When they are together in one integration model, DO NOT set the flag “Parallelize in APO” as active. The activation leads to simultaneous processing which may cause this issue.

Please refer the wiki and OSS notes 1447271 and note 492591 for FAQ stock forwarding.

SAP Community Network Wiki - Supply Chain Management - " Most Common CIF Errors".

Regards,

R.Brahmankar

[Former Member · Accepted solution]

Thanks for Response.  In our case stock and batch are part of same integration model and  we have not set flag parallelize in APO. Still problem occurs what we observed  it occurs when multiple goods movement are posted at almost same time for material and batch. I checked OSS note 1447271 but its not relevant for our release we are already with SCM 7.2.

Any other pointers. Will it help if we seperate stock and batch model. Is there any impact on transfer of shelf life data from ECC to APO

Regards,

Santosh

[rupesh_brahmankar3 · Accepted solution]

Hello Santosh,

You should try the separate the stocks and batches in different integration models, first Batch then Stock.

Also check OSS note    1776949 - Stock inconsistencies with stock update counters III.

Best Regards,

R.Brahmankar