Skip to main content

Failing back to default Non-Project Code (800) on advance purchasing receipts and manufacturing issue credits – UI/Setup conflict?

  • August 20, 2026
  • 2 replies
  • 30 views

Our team buys and receives inventory in advance directly to the project before a production order even exists (pre-purchasing/stocking for the job). Because of this advance procurement step, we cannot use the "Mark for PO" option from the production order materials tab.

When we create a standalone Purchase Order directly to a specific project and task, the system strips our project ID during the Purchase Receipt release, defaulting the inventory lines straight to our non-project fallback code (Project 800). Similarly, during production execution, our WIP debits hit the project perfectly, but the inventory credits fall back to 800.

To solve this, we tried setting up a fresh test project with "Track by Project Quantity and Cost" enabled. However, it still fails back to Project 800.

Upon digging deeper, we noticed a weird configuration mismatch:

  1. The global Project-Specific Inventory feature flag is definitely checked and enabled on our Enable/Disable Features (CS100000) screen.
  2. However, when we look at our Stock Items (IN202500) profile screen on the General tab, the entire Project Tracking dropdown/section is completely missing from the UI layout.

Since the feature flag is active but the stock item fields are hidden, it seems like the database isn't fully initializing the project inventory cost layers, forcing everything back to standard valuation (and thus Project 800).

Has anyone run into a scenario where the global feature is active but the stock item tracking rules remain hidden in the UI? Do we need to run a specific database initialization utility, or is there an Item Class setting we are missing to expose this field?

Any guidance or technical tips would be greatly appreciated!

2 replies

angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • August 21, 2026

Could you please provide the version/build of Acumatica ERP you are using?


Forum|alt.badge.img+2

@AKR2025 Are the Inventory Asset accounts included in an Account Group (PM201000)? For both Production Order Material Issues and Purchase Receipts GL transactions, the project may be removed if the related account is not mapped to an Account Group. That could explain why the transaction is defaulting back to Non-Project Code (800).

If the account mapping is correct and the issue still occurs, I recommend submitting a support ticket for further investigation.