My finance team found some Periodic Posting Process credits/debits that are hitting a division that is mostly defunct now, and they very much did not expect coming from Jobs in a completely different division / state. When looking at the details in the posting (Inventory WIP reconciliation report, I assume?) they are seeing the below transactions, and asking me how to figure out who/what did this? Related question (maybe): what does “BFVariance” stand for? Best Friend Variance?
I tried opening up the job in question in Job Adjustments, thinking maybe someone did something in there (we normally don’t touch that as nobody fully understands it at this point), but it didn’t see any records in there for this job (maybe I’m expecting something that will never be there?).
Any pointers would be greatly appreciated - even if you just tell me which technical reference guide I should go read and what to look for in there.
Can you pull the part trans records for the job materials? We’ve had funny variances that turned out to be related to how the methods roll up subassembly operations, in such a. way that the final operation of a subassembly somehow got done in the wrong order, allowing candidate=true to occur prematurely. Once candidate=true any further material issued to the job goes into variance, and by going through the parttrans logs we were able to find exactly when it happened.
Don’t know. what BF is though, or how a. different div gets involved, unless the bins or part warehouses for the affected part is in a wrong site?
@Noffie look in PTHT for records related to that job. I would assume BF is backflush and someone/something changed a quantity somewhere and the previously backflushed value had to change, but the job is completed/closed so the delta had to go to a variance account. The posting rule that did this is either custom or has a flaw that crosses divisions improperly.
Thanks @gpayne - that sounds like a good suggestion. I’m going to pass that info along to the finance team and see what they can find looking into it that way.
I the transaction has not been captured -
Go to GL Transaction Type and pull in COSandWIP posting rule.
Check the box to log the transactions (temporary for this test)
Run the inventory wip reconciliation report filtered for the specific job(s)
Go back and right click on the COSandWIP field to launch the posting rule log.
I found it is easier to copy the log to excel to review but you can search through the text.
In the search box, key in the value of the transactions (no commas)
It should tell you what is driving the division segment.
Out of the box, if you have a division GL control assigned to a warehouse that would be one way that it would flex to the division.
To eliminate any posting to the closed division, go into the General Ledger Account list and inactivate all of the account numbers with that division segment.
The Job Cost Adjustments screen will only show adjustments entered in the current session (in the tree at the left), it won’t bring up past adjustment transactions after the window is closed.
