JohnDanter2
VIP Member
Hi folks
I asked this on the developers section but I feel this maybe more of a functional question
We have a problem in that if we have a WO for 400 and one of the components has a suggestion for 400 and we complete this WO 100 units at a time (4 pallets) then we see the intial suggestion getting split from it's intial QTY of 400 and updated to 100 (line 1.000) and then split to a remainder 300 (line1.001), but the LOTN LOCN is the same, so there is no need for the split. Plus theF4611 suggestions are at 399.
I have traced the split to these 2 BSFNs
BSFN EndDocWOIssuesLocnSelection (N4600700) calls F4611SplitSuggestions (B4600650) If the following is true...which it is everytime.....!
SELECT * FROM UTDTA.F4611 WHERE ( R2TYFL = '2' AND R2MCU = ' 245' AND R2KCOO = '00245' AND R2DOCO = 3708318.000000 AND R2DCTO = 'WO' AND R2CLID = 0.000000 AND R2ITM = 5386301.000000 AND R2TLOC = 'LI01IN ' AND R2TLOT = '202206240328 ' AND R2PSTB >= '398' AND R2PHAS <> '1' )
I have tracked this bug
And also noticed we've had this occuring for some time but the SQL checking PSTB was revesed
In 9.0 thats a LESS THAN OR EQUAL
In 9.2 thats a GREATER THAN OR EQUAL
We do have bug 27266591 installed in 9.2
00012 // 03/21/2018 RV9056609 27266591 MATERIAL ISSUES P31113 IS CAUSING
00013 // PARTIALLY CONFIRMED WMS SUGGESTIONS TO SPLIT
00033 // Bug 27266591 - Revoke fix provided under bug 22242579.
00034 // Select F4611 records at status greater than 398 and with CLID = 0 as they
00035 // denote confirmed suggestions that are yet to be processed for material
00036 // issue
So I would say this 'fix' is whats causing 9.2 to do what it is
But co,ming back a step....Is there anyway to stop this from happening at all? Is there a PO on P31114 for example that might stop this?
Thanks
John
I asked this on the developers section but I feel this maybe more of a functional question
We have a problem in that if we have a WO for 400 and one of the components has a suggestion for 400 and we complete this WO 100 units at a time (4 pallets) then we see the intial suggestion getting split from it's intial QTY of 400 and updated to 100 (line 1.000) and then split to a remainder 300 (line1.001), but the LOTN LOCN is the same, so there is no need for the split. Plus theF4611 suggestions are at 399.
I have traced the split to these 2 BSFNs
BSFN EndDocWOIssuesLocnSelection (N4600700) calls F4611SplitSuggestions (B4600650) If the following is true...which it is everytime.....!
SELECT * FROM UTDTA.F4611 WHERE ( R2TYFL = '2' AND R2MCU = ' 245' AND R2KCOO = '00245' AND R2DOCO = 3708318.000000 AND R2DCTO = 'WO' AND R2CLID = 0.000000 AND R2ITM = 5386301.000000 AND R2TLOC = 'LI01IN ' AND R2TLOT = '202206240328 ' AND R2PSTB >= '398' AND R2PHAS <> '1' )
I have tracked this bug
And also noticed we've had this occuring for some time but the SQL checking PSTB was revesed
- 9.0 SQL
In 9.0 thats a LESS THAN OR EQUAL
- 9.2 SQL
In 9.2 thats a GREATER THAN OR EQUAL
We do have bug 27266591 installed in 9.2
00012 // 03/21/2018 RV9056609 27266591 MATERIAL ISSUES P31113 IS CAUSING
00013 // PARTIALLY CONFIRMED WMS SUGGESTIONS TO SPLIT
00033 // Bug 27266591 - Revoke fix provided under bug 22242579.
00034 // Select F4611 records at status greater than 398 and with CLID = 0 as they
00035 // denote confirmed suggestions that are yet to be processed for material
00036 // issue
So I would say this 'fix' is whats causing 9.2 to do what it is
But co,ming back a step....Is there anyway to stop this from happening at all? Is there a PO on P31114 for example that might stop this?
Thanks
John