Codeunit 99001017 "Production Definition Manager"
Base Application · Microsoft.Manufacturing.Wizard
Across versions
- BC23-29not present
- BC30added
Neighbourhood 11 connected objects and pages
Base Application · Microsoft.Manufacturing.Wizard · BC30 · source at f18567dc · facts from BC30
Events published
OnAfterPostWizardProcessing(TempData: Codeunit "Prod. Definition Temp Data"; var ProdOrder: Record "Production Order")(integration)
Procedures
RunForSource(Source: Variant; Mode: Enum "Prod. Definition Mode"): Boolean(internal): Opens the Production Definition Wizard for any source record type using the default Released production order status.RunForSource(Source: Variant; Mode: Enum "Prod. Definition Mode"; ProdOrderStatus: Enum "Production Order Status"): Boolean(internal): Opens the Production Definition Wizard for any source record type. The source is dispatched through Prod. Def. Source Initializer, which handles Item, Stockkeeping Unit, and Sales Line natively. For other source types such as Purchase Line, subscribe to OnInitializeFromSource on that codeunit. BOM a…ProcessBOMAndRoutingData(ItemNo: Code[20])(internal): Persists the temporary production BOM and routing data collected during the wizard run. If no existing BOM or routing is found for the item, new records are created using the configured number series and certified immediately. If a version code is present, a new BOM or routing version is created ins…GetTempData(var OutTempData: Codeunit "Prod. Definition Temp Data")(internal): Returns the internal temporary data codeunit that holds the BOM, routing, and source document data collected during or after a wizard run. Use this to inspect or pass the wizard results to other codeunits without re-running the wizard.OpenCreatedProductionOrder(ProdOrderNotification: Notification)(internal): Opens the production order card page that corresponds to the status stored in the notification. This procedure is the action callback for the notification sent after a production order is created by the Production Definition Wizard.
Plus 19 local procedures.
Calls
From the extracted call graph of BC30 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 99001016 “Prod. Definition Temp Data” (22 calls:
CreateBOMIfNotExists → LoadBOMLines,CreateReservationFromSalesLine → GetGlobalSalesLine,CreateRoutingIfNotExists → LoadRoutingLines, …) - Codeunit 99001015 “Prod. Definition Version Mgmt.” (8 calls:
CreateBOMIfNotExists → CheckBOMExists,CreateRoutingIfNotExists → CheckRoutingExists,PrepareBOMAndRoutingDataForScenario → GetDefaultBOMVersion, …) - Codeunit 8703 “Feature Telemetry” (5 calls:
CreateBOMIfNotExists → LogUsage,CreateRoutingIfNotExists → LogUsage,ExecuteWizardProcess → LogUptake, …) - Page 456 “No. Series” (4 calls:
CreateBOMIfNotExists → (object),CreateRoutingIfNotExists → (object),SaveBOMVersionIfRequired → (object), …) - Codeunit 6500 “Item Tracking Management” (2 calls:
CreateReservationFromSalesLine → ComposeRowID,CreateReservationFromSalesLine → CopyItemTracking) - Codeunit 99001018 “Prod. Order Direct Creator” (2 calls:
PostWizardProcessing → CreateProductionOrderFromTempData,PostWizardProcessing → RefreshProductionOrder) - Codeunit 5402 “Unit of Measure Management” (1 call:
CreateReservationFromSalesLine → QtyRndPrecision) - Codeunit 5407 “Prod. Order Status Management” (1 call:
FlushReleasedProdOrderForSalesSource → FlushProdOrder) - Codeunit 700 “Page Management” (1 call:
OpenCreatedProductionOrder → PageRun) - Codeunit 99000832 “Sales Line-Reserve” (1 call:
CreateReservationFromSalesLine → BindToTracking)
Called by
- Page extension 99000883 “Mfg. Sales Order Planning” (1 call:
CreateOrder → RunForSource)
Recent changes
- 2026-08-16 #9067 Production Definition Wizard - Implementation (main, BC30, feature, added)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC30 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Production Definition Manager"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.