Recalculate Part Low Level Codes (cvbm0002)

Someone in-house ran cvbm0002 last night and I am trying to deteThis text will be hiddenrmine exactly what it does. The description of “Recalculate Part Low Level Codes” is not all too helpful.

I looked at the log from when it was ran, and the last few lines are:

18:07:19 Process has been AutoCanceled, Low Level Code exeeded the allowed limit.
18:07:19 Please fix Low Level Code for next parts:
Company EFGONE, PartNum V53791, LowLevelCode 10000
Company EFGONE, PartNum 224519, LowLevelCode 10000
18:07:19 Recalculate Part Low Level Codes Process Completed

To me, that says that whatever it was doing, didn’t work for at least 2 of those parts. So, I opened up SSMS and ran:

SELECT p.PartNum, p.LowLevelCode FROM Part p ORDER BY p.LowLevelCode DESC

which returned this:

PartNum LowLevelCode
V30672 10000
224519 10000
V53791 10000
T1ASS9168 5
T20-028 5
T20-061 5

I find it high suspicious/unusual that those 3 parts shown have an LLC (whatever it is) of 10000 while the next highest is only at 5.

Does anyone have any knowledge of the LLC, and what running cvbm002 does?

I used the Data Dictonary Viewer form to find the definition in Epicor. A Low level Code of 10000 is large, it indicates that this part is found in an assembly 10000 deep on a BOM.

“Internally assigned integer which indicates the deepest level of assembly indention that this part is used at. This is used by the Cost Rollup routines to control the order in which parts get costed. Part at the bottom (highest levelcode) Product structure are calculated first and continues up the chain, with the final assembly parts being processed last. This insures that when retrieving the cost of an assemblies components the components will already have had their cost rolled up.”

Are they another company with 600 page job travelers??

I’m surprised Epicor doesn’t die on a BOM that crazy, is that number actually accurate?

I would look at the bom for an accidental recursion assuming that 10K was the upper limit.

1 Like

I don’t know about y’all, but I think this here may be the culprit…

Mtl Sequence: 10
Part: 224519 will cause an endless loop in method defined for Part: 224519, Revision: B, AltMethod: .
(Asm Part: 224519, Asm Rev: B, Asm AltMethod: , Mtl Seq: 10, MtlPart: 224519)
image

That would do it. You can manually set low level code on the part master back to 0. Bottom right hand side.