Multiple Ship Confirm Problem

[jdetechie07]

Hi All ,

=20

We are facing a problem in which while ship confirming the SO line is =
getting ship confirmed multiple times. This is causing negative on hand =
inventory .In the Item Ledger there are 2 entries for ship confirming =
the same item With same SO number while the transaction was done only =
once.The SO detail table F42199 shows that this SO has gone twice Under =
ship confirm. This is not happening regulary but once or twice a week.

Anybody faced this problem before .Any SAR for this ?

Any help would be greatly appreciated.

Thanks

JdeTechie

ERP8 , Oracle 8i




This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law. If you are not the intended recipient, you should =
delete this message. Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly =
prohibited.



OneWorldXE,ERP 8 , SQL Server , Oracle

 

[jdesmm]

Yes, we have periodically faced the same issue and have never been able to debug it or prevent it. We are going from XE update 6, SP20 to XE update 7, SP22, and hope that the change might make a positive impact. In the meantime, when it occurs, we update the inventory balances in the F41021 via SQL. The process is documented and signed off by management, so while we aren't happy that we have to do it, we are able to fix the problem and keep the balances from getting out of synch.

 

[vbojan]

We found so far 3 different ways to make double Cardex/Sales History entry form P4205:
1) If N4200790 – ShipConfirmEndDoc works asynchronously it is possible to ship confirm the same sales order detail line twice if user re-run ship confirmation fast enough (before ShipConfirmEndDoc finish). It’s easy to change call to ShipConfirmEndDoc in P4205 from asynchronous to synchronous to prevent this.
2) If the same user open two shipment confirm screens (W4205K) for the same order and makes records go to cache (update ‘Sel = 1’ for example) each instance of W4205K is able to ship confirm. This should be solved in 8.9. We changed P4205 to get custom unique id (we are using custom DB2 stored procedures based solution but UKID from F00022 should be OK) in W4205K “Dialog is Initialized” event, transform that number to string10 report variable and replace standard PID in N0000602 – F00095 Reserve Object (W4205K Write Grid Line – After) with new string10 variable (P4205 is in UDC 00/RR). This will force N0000602 to issue error if one user tries to open the same sales order in more than one W4205K instances. N0000602 – F00095 Remove Business Object Reservation call in Cancel and OK – Post Button Clicked have to be changed accordingly too.
3) In Xe XU1, if the same user open existing sales order in P4210, keep P4210 open, run ship confirmation for the same sales order, ship confirm that order and finally click on OK in P4210; original B4200311 cache will be written into F4211 and it will overwrite ship confirmation data (status next, status last, pick slip #..) in F4211. After this user can make new ship confirmation. This problem might be fixed in later releases. We changed P4210 call to N0000620 using custom unique number instead of PID. Because B4200310 – F4211 End Document is really slow we moved N0000602 – F00095 Remove Business Object Reservation from P4210 OK – Post Button Clicked into B4200310. Also we changed R42520 – Pick Slip to use the same N0000602 reservations as P4210 and P4205.

Those changes were made recently but it looks like they fix our double Cardex/Sales History entry problem. Unfortunately, if user get disconnected somebody needs to release reservation using P00095.

Hope this helps,

Bojan.

PS

If somebody knows another way to make multiple ship confirmation, please let us know.

 

[jdetechie07]

Bojan ,
Thanks for the reply.
We've also contacted JDE and we're waiting for their response as well.
Will look into your options and keep you posted.
=20
=20



OneWorldXE,ERP 8 , SQL Server , Oracle