Well this was a swift kick in the pants today. It’s fully documented, but wow I did not expect this at all. Ready?
So, general rule in any kind of transaction is:
- If there is a GL on the Part, use that first
- Otherwise look for a GL on the Part Class
- Then look other places
All normal so far, right? OK great.
I have a part (920457) that
- Is non-quantity-bearing
- Has a GL control on the Part itself
- Has a GL control on the Part Class also
Here is what actually happens with these transactions:
Ship 920457 to a customer (UKN-CUS): Part GL if any, then Class GL
Issue 920457 to a job (STK-MTL): Part GL if any, then Class GL
(There is no UKN-MTL, by the way; STK-MTL is used even for non-QB)
Buy 920457 on a PO (PUR-UKN): Ignore Part GL and start with Part Class
Well isn’t that something else. We are buying this part into a different accounting bucket than we are issuing it from. #LearnedThatTheHardWay
(FYI, PUR-STK looks at Part GL, then Part Class. 
)
I guess I’ll report this (@hkeric.wci would want me to have that fun with support), but like I said, it’s totally documented as being this way, so it’s as designed, of course.
I try to avoid this word, but this is just flat-out stupid. Really.
