Best Of

Hi @Selina

There is no separate 'page 2' layout.

The template layout is repeated in the subsequent pages when the amount of item rows exceeds what can fit on one page.

Example:

@CDK

Once inventory shortages and pending builds have been accumulating for years, it usually becomes a historical inventory repair issue, rather than a simple build problem.

What often happens is 1 negative component creates another shortage later, which then snowballs through the file over time.

My suggestion would be rather than trying to perfectly repair 10+ years of history, instead:

• choose a clean cutoff date
• correct stock quantities from that point
• clear current pending builds
• & then enforce processes to prevent future negatives.

Selling assembly items before completing the build is commonly what starts the problem.

At this stage, focusing on getting stock accurate going forward is usually far more practical than trying to trace every historical shortage transaction-by-transaction 😬

What you’re describing usually indicates a component shortage somewhere, even if it’s not immediately obvious.

A few things I’d check:

• Build date timing — Reckon checks component availability as at the Build date, NOT today’s quantities. Historical negatives can cause a build to go Pending even when stock currently looks fine.

• Run a Stock Status by Item report for the components and look closely for:

• negative available qty
• committed stock
• tiny decimal shortages/rounding issues

• Try changing the Build date to today/future & test again.

• Try building qty = 1 only, in case it’s a rounding issue on one component.

• Run Verify/Rebuild (after backup). Old pending builds can sometimes leave inventory inconsistencies behind.

• If all else looks normal, create a brand new test assembly using the same components. Occasionally an assembly item itself can become damaged/corrupted.

The fact there’s no warning message and it silently moves to Pending Builds generally points more toward a stock availability issue than a hard data corruption error though 😊

From your screenshot, it looks like the issue is because that Assembly is already in the negative at that point eg you previously "sold" (or allocated) one you hadn't yet built! Try building it on a prior date, when it was last at 0 or a positive count.