Subcontract operations not completing

[TerryR (Terry Raymond)]

We have completed subcontract operations not getting marked complete sometimes.
We’re receiving the full qty, but the qty isn’t always showing up on the job for some reason… not consistent, as sometimes they do get the qty right and show as complete.

Any ideas on where else I can look to track down what is going on?

Example:

These posts show others with similar issues, but not much help on the cause.

Manually Closing Subcontract Operation

Here is the situation. Sometimes, not always, when we receive something complete, and it makes it through inspection, the outside processed parts are received complete yet the job doesn't get the green checkmark indicating the op is closed. The run qty for example will be 50 and the completed qty will be 50, but the op is not complete. Is there any way to manually close the op out so it doesn't appear open? Any help is appreciated. Thanks! Ben

Subcontract Operations - Complete

Can someone tell me how many different ways a Subcontract Op can close, whether automatically or manually? We have an issue where some of the outside subcontract ops are closing prematurely, before the Run Qty is met. I checked to make sure we were not marking the receipts as “Issued Complete” so that is not the issue. I saw another post that mentions they can be marked complete on the Resource Scheduling Board, which does not seem to be the issue either, but is it possible we have something che…

Thanks much for any help fellas.

[dcamlin (David Camlin)]

Based on your receipt snip, the parts should have gone into inspection. Was the inspection process completed?

[TerryR (Terry Raymond)]

Oh great eye! Thanks for the lead. Got 10,000 steps in chasing that down…

Turns out that is the 2% problem, as we don’t use the inspection function. And I’m still stumped…

• 2 held up ops had the inspection flag on PO entry/tracker (looks like this was accidentally set on the job op, then unchecked later)
• 4 held up ops had the Inspection flag on receipt entry, 2 from above PO setting, and 2 more from manually ticking the box over all the years. I just hid the checkbox on their screen now.
• But I’m seeing 211 operations, with completed qty or received qty greater than run qty, that are still shown as incomplete (OpComplete = 0).

Any other ideas on what else I could look into…?

Update…

So I dug into the labor transactions, the completed qty is the full qty, but maybe they are manually unchecking the Complete box on the End Activity screen for some reason…

[dcamlin (David Camlin)]

So, if you look at the RECEIPT for one of the remaining trouble operations… may be under the job tab. There should be a checkbox labeled “Issued Complete”. Is that checked?

I just ran a quick test in my pilot DB.

Created a job w/ a subcontract op.
Created a PO for that op.
Did NOT create a subcontract shipment (I was testing the theory whether this was “required” or not).
Created the Receipt.

… op showed as completed on my job.

BUT, then I noticed that “Issued Complete” checkbox was checked by default (and should if the quantities match up). BUT I then unchecked that checkbox and now the operation on my job no longer shows as complete.

Can you verify that? Sorry, I’m looking at Kinetic screens and not Classic, but I would assume it would be in here:

[TerryR (Terry Raymond)]

Well I’ll be damned, that looks to be the culprit. Now I need to figure out why that is happening. Thanks so much!!

[dcamlin (David Camlin)]

Hooray! Have fun fixing all those

… and figuring out why that box isn’t getting (or staying) checked!

[TerryR (Terry Raymond)]

I have some of this sorted, sharing for others…

Most of the completed but Not-Issued-Complete operations are from having 2 different receipt entries for the same release. Thanks to @dcamlin for pointing us to KB0137803. I’m going to add a fix for this with a BPM, to mark it Issued Complete if the full received quantity meets or exceeds the job demand.

A few of the other instances look to come from the job operation quantity/parent being later lowered to match the received qty. There are posts here suggesting to add an IssuedComplete / OpCompete checkbox to the screen customization, but I don’t really like that. And a BPM doesn’t seem right either. Maybe a note to tell them to fix the reciept to be IssuedComplete if they have to do this again.

There are some where RcvDtl.IssuedComplete shows as 0 in the database, but when viewing in receipt tracker, IssuedComplete it is Checked! So maybe it is checking vs the job… though on the job there are some of these that show OpComplete = true and others show it False… baffling.

And then there are others that are both 0 in database and unchecked in Receipt Tracker, where I can’t tell why IssuedComplete wasn’t checked… with that, we’ve got every possible permutation of how it could be screwed up.

I might go through our backups and see if I can recreate the receipts in our test environment to try to replicate…

Other thoughts/input welcome!