Page 99000766 "Routing"
Base Application · Microsoft.Manufacturing.Routing
Across versions
- BC23-25present
- BC262 procedures added, 1 procedures removed
- BC271 procedures added
- BC28unchanged
- BC291 procedures added
- BC30unchanged
Neighbourhood 9 connected objects and pages
Base Application · Microsoft.Manufacturing.Routing · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Routing |
| SourceTable | Routing Header |
| PageType | ListPlus |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| General | No. | No. | Specifies the number of the involved entry or record, according to the specified number series. from the table field |
| Description | Description | Specifies a description for the routing header. from the table field | |
| Type | Type | Specifies in which order operations in the routing are performed. from the table field | |
| Status | Status | Specifies the status of this routing. from the table field | |
| Search Description | Search Description | Specifies a search description. from the table field | |
| Version Nos. | Version Nos. | Specifies the number series you want to use to create a new version of this routing. from the table field | |
| Active Version | ActiveVersionCode |
Specifies if the routing version is currently being used. | |
| Last Date Modified | Last Date Modified | Specifies when the routing card was last modified. from the table field | |
| Content | RoutingLine | part Page 99000765 “Routing Lines” | — |
| FactBoxes | Documents | part Page 1178 “Doc. Attachment List Factbox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Routing | Comments | View or add comments for the record. | Page 99000784 “Manufacturing Comment Sheet” |
| Versions | View or edit other versions of the routing, typically with other operations data. | ||
| Where-used | View a list of BOMs in which the item is used. | Page 99000782 “Where-Used Item List” | |
| Attachments | Add a file as an attachment. You can attach images as well as documents. | ||
| Functions | Copy Routing | Copy an existing routing to quickly create a similar BOM. | |
| Reporting | Routing Sheet | — | Report 99000787 “Routing Sheet” |
Events published
OnBeforeOnQueryClosePage(var RoutingHeader: Record "Routing Header"; var xRoutingHeader: Record "Routing Header"; var Result: Boolean; var IsHandled: Boolean)+ BC26 (integration)
Procedures
4 local procedures, no public ones.
Triggers
OnAfterGetRecord, OnQueryClosePage
Relations
- source table Table 99000763 “Routing Header”
Pages and codeunits on this table
- Page 99000764 “Routing List” (card page)
Extended by
Calls
From the extracted call graph of BC29 (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 1330 “Instruction Mgt.” (1 call:
OnQueryClosePage → ShowConfirmNonCertified) - Codeunit 99000756 “VersionManagement” (1 call:
RefreshActiveVersionCode → GetRtngVersion)
Called by
- Codeunit 99000820 “Mfg. Bom Buffer” (1 call:
OnAfterShowWarning → (object)) - Codeunit 99000861 “Mfg. Planning Integration” (1 call:
PlanningErrorLogOnShowError → (object))
Recent changes
- 2026-07-10 #9123 Bug 641489: Show Next/Previous Operation No. on routing lines when Type = Parallel (main, BC30, fix)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 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: "page", object_name: "Routing"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.