ship confirmation

[smuck007]

We are on B7.3.3.2 - Citrix.
Randomly throughout the day, we are seeing orders where one line item on an order is NOT ship confirming. It happens on orders with any number of line items. It is always one line item that doesn't ship confirm. We call the vanilla JDE ship confirm program via some custom code. To fix the order, I manually ship confirm the line item through JDE with no error. Based on the code for P4205, we are wondering if it has something to do with caching. Anyone else seen this. No SARs or ESU's seem to apply from the KG.

Thanks,
007

 

[ame]

Is it a particular line number.... like line number 13 is always left off?


Randomly throughout the day, we are seeing orders where one line item on an
order is NOT ship confirming. It happens on orders with any number of line
items. It is always one line item that doesn't ship confirm. We call the
vanilla JDE ship confirm program via some custom code. To fix the order, I
manually ship confirm the line item through JDE with no error. Based on
the code for P4205, we are wondering if it has something to do with caching.
Anyone else seen this. No SARs or ESU's seem to apply from the KG.

Thanks,
007

 

[DSauve]

Jim,

Yes, I believe that JDE does cache SO updates. It uses a Begin Doc, Edit Line, and End Doc function calls when maintaining SO's. Does your custom code use these functions as well?

 

[smuck007]

Thanks for the reply.
Yes, our custom code is a modification of JDE. It uses the same function
calls.
I just discovered the missing line item is ALWAYS the first line item of the
order.
It could be we miss the first item in the ship confirm screen with our code
occasionally somehow??
007