F3111 Commitments dont look right...

SteveC

Member
I`ve got a couple of F3111 records which just don`t look right to me, and Im thinking that I need to write an integrity to fix them. But before I do, I`d like some clarification that my analysis is correct....

Take a look at the attachment. It shows the results of a query on the F3111 for a specific component/lot/location.

On the first line, you can see that the component line is unissued, but a lot is (hard) allocated - but WMQNTA is zero - shouldn`t it be the same value as WMUORG?

On the 2nd line, we have issued the full quantity required, but WMQNTA = original quantity required - shouldn`t it be zero??

As I understand it, R3190 WO Repost reads WMQNTA in order to repost the F41021 allocations, so thats never going to fix this issue - i need to somehow "repost" the F3111 quantities.

Could someone confirm my assumptions are correct, or otherwise? I`d also like to know what processes are responsible for populating / updating WMQNTA

Thanks in advance.


EDIT:: The above must be completeley wrong - because now 2 more WO`s have had this lot/location added to them and the commitment is correct (see 2nd attachment).
It feels like theres a business function or functions which are updating F41021 at the point of hard allocation (either through P3111 or R31410) and when the 2 new WO`s were allocated, they "reset" the allocation on F41021.

Now, you can see the 2 original F3111 records are unchanged, so what gives?
 

Attachments

  • 151254-Hard Allocations.jpg
    151254-Hard Allocations.jpg
    110.1 KB · Views: 135
Sometimes running R3190 will not clear any rogue commitments in F41021. Try raising a works order for the item, running R3190, and then cancelling the works order.

Another problem I have seen in our current setup (E811 SP1) a works order that had been scrapped remained at status 85 and showed as a commitment. Updating the works order to status 99, and running R3190 fixed the issue.

Hope this helps

Thanks
Aidy
 
Try this.
Update F3111
set WMUORG = WMTRQT, WMQNTA = WMTRQT, WMSOBK = 0
WHERE WMDOCO in ('389532', '389531')

Update F3111
set WMSOBK = '999999999999999'
WHERE WMDOCO in ('389532', '389531') AND WMTRQT = 0

Both the SQL can be embedded in sequence in a Batch application and run the report for Partial completed orders.

We have partial completed orders in a particular status and move to next status after running R31802A, Then run this new batch application to move to next status. Commitment is releived immediately after running this(SQL batch) or next R3190 is run or when the status is at 99.

Thanks.

Bala
E812 DB2 SQLServer WIN
 
Back
Top