Prod. Order Component does not exist error on Planning/Requisition Worksheets

Business Central/NAV
1

Hi folks,
We’re getting an error occasionally when calculating the plan from the requisition worksheet, running a regenerative plan on the planning worksheet, or deleting a line on the planning worksheet.

We have checked that the components do exist on the prod order, there are no issues there. It looks like this error is something to do with the reservation system, but I haven’t been able to find a solution. Any ideas please?

Error message:
The Prod. Order Component does not exist. Identification fields and values: Status=‘3’,Prod. Order No.=‘PROD38040’,Prod. Order Line No.=‘0’,Line No.=‘10000’

AL call stack:
“Prod. Order Comp.-Reserve”(CodeUnit 99000838).GetSourceValue line 12 - Base Application by Microsoft
“Prod. Order Comp.-Reserve”(CodeUnit 99000838).OnGetSourceRecordValue line 3 - Base Application by Microsoft
“Reservation Management”(CodeUnit 99000845).OnGetSourceRecordValue(Event) line 2 - Base Application by Microsoft
“Reservation Management”(CodeUnit 99000845).GetSourceRecordValue line 5 - Base Application by Microsoft
“Reservation Management”(CodeUnit 99000845).SourceQuantity line 2 - Base Application by Microsoft
“Reservation Management”(CodeUnit 99000845).DeleteReservEntries line 35 - Base Application by Microsoft
“Plng. Component-Reserve”(CodeUnit 99000840).DeleteLine line 7 - Base Application by Microsoft
“Planning Component”(Table 99000829).OnDelete(Trigger) line 2 - Base Application by Microsoft
“Requisition Line”(Table 246).DeleteRelations line 28 - Base Application by Microsoft
“Requisition Line”(Table 246).DeleteRelations line 2 - Base Application by Microsoft
“Requisition Line”(Table 246).OnDelete(Trigger) line 19 - Base Application by Microsoft
“Calculate Plan - Req. Wksh.”(Report 699).“Item - OnAfterGetRecord”(Trigger) line 22 - Base Application by Microsoft

2

I don’t know if this is your issue, but the Line 0 is generally a clue. If your components have Reservations (especially if Item Tracked), you need to ensure your consumption is matching the specific Serial/Lot being consumed.

For example, if the system generated a Purchase Order for the component (Lot 123), and you try to consume the same Item but a different Lot (987), even though you have the component available, because the Lot being consumed doesn’t match the Lot that is reserved it can trigger an error message.

We saw a similar message when consuming Produced Items (Lot Tracked) against a Job. The system can be picky when dealing with Item Tracking and Reservations. Even Microsoft’s documentation mentions scenarios where customization is needed to make it work.

Design Details - Item Tracking and Reservations - Business Central | Microsoft Learn

Not sure if this helps or not, but please update if you find something out.

Best Regards,
Ben Baxter
Accent Software Inc