cancel
Showing results for 
Search instead for 
Did you mean: 

BOP overconfirms in case of partially delivered sales orders

Former Member
0 Kudos

The backorder processing ignores the quantity delivered, that is, it checks and confirms the entire order quantity thus having total confirmed quantity greater than ordered quantity.


How to reproduce:


Initially a sales order was created for quantity 10 and confirmed quantity 0. There was no stock.


EWM team added stock of 5 quantity and BOP ran and 5 was confirmed and same was replicated in ECC. It created delivery for this 5 quantity.


Again stock was added of 10 quantity in EWM and BOP ran and this time instead of confirming remaining 5, it just looked at ordered quantity

and confirmed entire 10 making total confirmed quantity of 15 (which is greater than ordered quantity 10)

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Disha,

I assume that this is a new implementation.

Such issues are almost always due to connectivity issues. Check your queues.

A second reason would be self-made enhancements, which are a little harder to troubleshoot.

Please show a screenshot of the original BOP result for this material.  Then, show a screenshot of the second BOP.

Best Regards,

DB49

Former Member
0 Kudos

Hi DB,

Thank you for the reply.

My queues are cleared. PFA the screenshot for BOP that is same before/after.

Regards,

Disha

Former Member
0 Kudos

PFB the overconfirmations screenshots.

Former Member
0 Kudos

Disha,

The first screenshot tells the tale.  The "Update" status is 'Sent'.  This means that BOP analyzed the situation, determined the change to be made, sent the data to ECC, but ECC never reported back to BOP that it made the change.  Assuming that your BOP Execution mode is set to 'Update Changes', you normally would like to see in this field set to "Updated" by BOP.
 

"Sent" status is often due to a data replication error, or to an enhancement that has been improperly written.

There are a number of things that can lead to data replication problems. Usually a good start for any problems like this is to run all the standard consistency checks.  Also check for and remove any unnecessary Temporary Quantity Assignments and unnecessary ATP trees.  Check system logs, ST22 entries, and SLG1 logs in both systems.  If detailed ATP logging is not turned on, turn it on until you find the answers you need.

Assure yourself that when you make any manual ATP changes on the ECC side, they move seamlessly over to the SCM side.  Likewise do the same thing in SCM.  Make a manual change using BOPI and assure yourself that it moves seamlessly over to the ECC side.

If the above does not yield any clues, then the next most likely culprit is an enhancement. You will probably have to speak to the developers that specialize in this area in your system.

Best Regards,

DB49

Answers (0)