Release PO created more than target value in contract

[sankaralingam_maharajan]

System at times creates release PO even though the accumulated value of released Purchase orders is greater than contract target value.  We have the config settings in place to stop this.  And it works OK all the time but fails sometimes !.  We have batch job in place that runs every 20 minutes to create release POs.  We are able to see in the job log (at 2:00 pm run) that system has stopped release PO creation.  In the next run (at 2:20 pm), it has created the PO strangely!  We checked if there is any change (config, variant, PR, contract) in this 20 minutes time gap between batch job runs but there is not any.

This issue is not replicable.  It does not happen often.  But couple of weeks back it happened once.  And it has happened today.  Any pointers would be helpful.

Below is the screenshot of 2:00 pm run

Below is the screenshot of 2:20 pm run

[sankaralingam_maharajan]

Updating the thread for records.

We could not find the exact issue yet.  SAP support does not help because the issue is non-replicable.  Stuck .

Thanks,

Sankar

[Prasoon]

Hi,

   It seems the message 06 042 was not issued in 2.20 job run. Hope the issue can be resolved by the KBA: 1929354 - Message 06 042 'Target value of contract & exceeded by & &' or the note:  1590695 - 06042 - target value check in release order fails

   Please refer the KBA and revert back.

Regards,

AKPT

[sankaralingam_maharajan]

Apologies for the late reply.  But pre-requisites of these KBA are not met in my case.  Item is not marked with Delivery Completion Indicator.  Item is not deleted.  Same issue has happened again on a different contract today.

[sankaralingam_maharajan]

Just saw this recent OSS Notes 2038808.  Need to check if it would really help.

2038808  - Error 06042 does not occur when target value exceeded for a contract

[Former Member]

Hi,

You need to analysis for your PO whether there was any changes in PO which where the price was set correctly or there might be any other changes such as qty and the PO was released.

Also check whether there was any change in contract also.

Only this might be the reason which caused the PO to set release.