Codeunit 99001015 "Prod. Definition Version Mgmt."
Base Application · Microsoft.Manufacturing.Wizard
Across versions
- BC23-29not present
- BC30added
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Manufacturing.Wizard · BC30 · source at f18567dc · facts from BC30
Procedures
ShowBOMVersionSelection(ProductionBOMNo: Code[20]; var SelectedVersion: Code[20]): Boolean(internal): Opens a lookup page for certified Production BOM versions and returns the selected version code.ShowRoutingVersionSelection(RoutingNo: Code[20]; var SelectedVersion: Code[20]): Boolean(internal): Opens a lookup page for certified routing versions and returns the selected version code.GetDefaultBOMVersion(ProductionBOMNo: Code[20]): Code[20](internal): Returns the default active BOM version code for a given production BOM as of the work date.GetDefaultRoutingVersion(RoutingNo: Code[20]): Code[20](internal): Returns the default active routing version code for a given routing as of the work date.ShowBOMSelection(var SelectedBOMNo: Code[20]): Boolean(internal): Opens a lookup page for certified production BOMs and returns the selected BOM number.ShowRoutingSelection(var SelectedRoutingNo: Code[20]): Boolean(internal): Opens a lookup page for certified routings and returns the selected routing number.CheckRoutingExists(RoutingNo: Code[20]; RoutingVersionCode: Code[20]): Boolean(internal): Checks whether a routing (or a specific routing version) exists in the database.TestRoutingCertified(RoutingNo: Code[20]; RoutingVersionCode: Code[20])(internal): Validates that the specified routing (or routing version) has Certified status. Throws an error if not certified.CheckBOMExists(ProductionBOMNo: Code[20]; BOMVersionCode: Code[20]): Boolean(internal): Checks whether a production BOM (or a specific BOM version) exists in the database.TestBOMCertified(ProductionBOMNo: Code[20]; BOMVersionCode: Code[20])(internal): Validates that the specified production BOM (or BOM version) has Certified status. Throws an error if not certified.GetBOMVersionNoSeries(ProductionBOMNo: Code[20]): Code[20](internal): Returns the number series code used for BOM versions of the specified production BOM.GetRoutingVersionNoSeries(RoutingNo: Code[20]): Code[20](internal): Returns the number series code used for routing versions of the specified routing.ValidateBOMVersionNoSeries(BOMNo: Code[20])(internal): Validates that the production BOM has a version number series configured. Raises an actionable error that opens the affected production BOM if not set.ValidateRoutingVersionNoSeries(RoutingNo: Code[20])(internal): Validates that the routing has a version number series configured. Raises an actionable error that opens the affected routing if not set.
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 99000756 “VersionManagement” (2 calls:
GetDefaultBOMVersion → GetBOMVersion,GetDefaultRoutingVersion → GetRtngVersion)
Called by
- Codeunit 99001017 “Production Definition Manager” (8 calls:
CreateBOMIfNotExists → CheckBOMExists,CreateRoutingIfNotExists → CheckRoutingExists,PrepareBOMAndRoutingDataForScenario → GetDefaultBOMVersion, …) - Page 99001021 “Production Definition Wizard” (4 calls:
LoadBOMLines → CheckBOMExists,LoadRoutingLines → CheckRoutingExists,SetBOMRoutingEditable → CheckBOMExists, …) - Codeunit 99001016 “Prod. Definition Temp Data” (3 calls:
CreateTemporaryComponentFromBOMLine → CheckBOMExists,CreateTemporaryComponentFromBOMLine → GetDefaultBOMVersion,LoadRoutingLines → GetDefaultRoutingVersion)
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: "Prod. Definition Version Mgmt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.