Skip to main content
Solved

Production Order - Pre-check availibility of all items as per BoM

  • December 8, 2025
  • 5 replies
  • 76 views

Hi All,

Acumatica's Production Cycle for a manufactured product consists of 2 major steps: 1) produce volume first and then 2) subsequently, pack the volume into the required SKU.

In such a scenario, is there a way to ensure that there is full availability of all materials required for producing a specific volume of a product, prior to confirming a Production Order? If yes, how and where can this be implemented/checked? In other words, a Production Order should not be allowed to proceed further (any subsequent steps) if there is either no or not enough material as required to produce a specific volume of the manufactured product.

The same applies to the 2nd part above i.e. to again ensure that all packaging material required is available in full quantity during a request for Packaging Materials. Since this is a separate TR request (Inter Warehouse Transfer), how to ensure that this TR request is tied to the Production Order from step 1 above? The reason being, in our case we use some common materials and packaging containers for multiple manufactured products and would like to have a one-stop audit trail/report/GI that provides information from start to finish for a particular Production Order.

Has the above scenario been improved or integrated/updated in 2025 R2 Manufacturing Edition?

Any tips/suggestions/clarifications will be greatly appreciated.

 

Manish

Best answer by angierowley75

Some of your questions are more specific to defining internal workflow processes - which might be better suited for an experienced VAR to address; however, in 2025R1 of Acumatica ERP, a new Production Orders by Build Capability screen was introduced, which should help address some of your needs.

See page 114 of the release notes for details

https://acumatica-builds.s3.amazonaws.com/builds/25.1/ReleaseNotes/AcumaticaERP_2025R1_ReleaseNotes.pdf

5 replies

angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • Answer
  • December 8, 2025

Some of your questions are more specific to defining internal workflow processes - which might be better suited for an experienced VAR to address; however, in 2025R1 of Acumatica ERP, a new Production Orders by Build Capability screen was introduced, which should help address some of your needs.

See page 114 of the release notes for details

https://acumatica-builds.s3.amazonaws.com/builds/25.1/ReleaseNotes/AcumaticaERP_2025R1_ReleaseNotes.pdf


Forum|alt.badge.img
  • Varsity I
  • February 17, 2026

Is this GI dependent on any specific manufacturing processes or system features (e.g., Advanced Planning), or does it require any particular feature to be enabled in order to function properly?”


angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • February 17, 2026

The Production Order Build Capability is part of the core/base manufacturing edition.

It does not consider capacity or time phased inventory, therefore APS and MRP are not required.


Forum|alt.badge.img
  • Varsity I
  • February 25, 2026

@angierowley75  

Thank you for the clarification that the Production Order Build Capability is part of the core Manufacturing edition and does not require APS or MRP.

However, in testing this GI across multiple live customer environments, we are experiencing inconsistent behavior:

  • In some databases, it returns the error:
    “Divide by zero error encountered.”

  • In other environments, the GI continues loading in page mode without returning results.

  • Another returns Error  “ Denial Code 511: System was unable to process the request due to data size limits. Please review your operation and consider requesting a smaller dataset.”

This is occurring even in environments where core Manufacturing is enabled and functioning normally.

Any guidance would be appreciated.


angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • February 25, 2026

The divide by zero error was a bug that was found and fixed.  Please reach out to Acumatica support for more details.