kjjdelist
Well Known Member
I'm using Adv. Whse and I am using the Subsystems (R46171, R46471, R46472,
R46473). From time to time with no apparent cause the subsystem will hang on
a Line in a Task. It can happen on Putaways, Picks, or Replenishments. The
result is that one of the lines on the Task will have 100 instances in the
F4611 table and some screwy things happen with the commitments.
In F41021, the LIPCOM value is reduced by the correct amounts for the task,
but the LIHCOM for the picking location and the LIQTRI for the S.. Location
are not always updated. It's really hit and miss on the task that loops.
However, all tasks released AFTER the one that loops have NO commitments
moved. Anyone seen this before?
-KJ-
B7332, SP17.1_E1, MSSQL 7.0, NT 4.0
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
R46473). From time to time with no apparent cause the subsystem will hang on
a Line in a Task. It can happen on Putaways, Picks, or Replenishments. The
result is that one of the lines on the Task will have 100 instances in the
F4611 table and some screwy things happen with the commitments.
In F41021, the LIPCOM value is reduced by the correct amounts for the task,
but the LIHCOM for the picking location and the LIQTRI for the S.. Location
are not always updated. It's really hit and miss on the task that loops.
However, all tasks released AFTER the one that loops have NO commitments
moved. Anyone seen this before?
-KJ-
B7332, SP17.1_E1, MSSQL 7.0, NT 4.0
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
