Table 99000763 "Routing Header"

Base Application · Microsoft.Manufacturing.Routing · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 99000766 “Routing” (2 Learn pages), Page 99000764 “Routing List” (1).

Properties

Property	Value
Caption	Routing Header
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	No. Δ BC28	Code[20]	Specifies the number of the involved entry or record, according to the specified number series.
2	Description Δ BC28	Text[100]	Specifies a description for the routing header.
3	Description 2	Text[50]	—
4	Search Description Δ BC28	Code[100]	Specifies a search description.
10	Last Date Modified Δ BC28	Date	Specifies when the routing card was last modified.	not editable
12	Comment	Boolean	—	FlowField: exist(“Manufacturing Comment Line” where(“Table Name” = const(“Routing Header”), “No.” = field(“No.”))); not editable
20	Status Δ BC28	Enum “Routing Status”	Specifies the status of this routing.	enum Enum 99000764 “Routing Status”
21	Type Δ BC28	Option	Specifies in which order operations in the routing are performed.	OptionCaption: Serial,Parallel
50	Version Nos. Δ BC28	Code[20]	Specifies the number series you want to use to create a new version of this routing.	TableRelation Table 308 “No. Series” (No. Series)
51	No. Series	Code[20]	—	TableRelation Table 308 “No. Series” (No. Series); not editable

Keys

Key1: No. (clustered)
Key2: Search Description
Key3: Description
Key4: Status

Trigger event subscribers

OnAfterDeleteEvent: Codeunit 99000783 “Prod. Document Attachment Mgt.” DeleteAttachedDocumentsOnAfterDeleteRoutingHeader
OnBeforeInsertEvent: Codeunit 99000788 “Mfg. Experience Tier” BlockInsertRoutingHeader

Procedures

AssistEdit(OldRtngHeader: Record "Routing Header"): Boolean
RoutingLinesExist(): Boolean + BC26

Triggers

OnDelete, OnInsert, OnModify, OnRename

Relations

drill-down page Page 99000764 “Routing List”
lookup page Page 99000764 “Routing List”
No. Series: TableRelation Table 308 “No. Series”
Version Nos.: TableRelation Table 308 “No. Series”
Comment: CalcFormula Table 99000770 “Manufacturing Comment Line”

Referenced by

41 fields in 41 objects relate to this table (TableRelation or CalcFormula).

Table 20560 “Subcontractor WIP Ledger Entry”: Routing No.
Table 20573 “Subc. Routing Comment Line”: Routing No.
Table 20574 “Subc. Prod. Rtng. Comment”: Routing No.
Table 5405 “Production Order”: Routing No.
Table 5406 “Prod. Order Line”: Routing No.
Table 5409 “Prod. Order Routing Line”: Routing No.
Table 5410 “Prod. Order Capacity Need”: Routing No.
Table 5411 “Prod. Order Routing Tool”: Routing No.
Table 5412 “Prod. Order Routing Personnel”: Routing No.
Table 5413 “Prod. Order Rtng Qlty Meas.”: Routing No.
Table 5415 “Prod. Order Rtng Comment Line”: Routing No.
Table 9056 “Manufacturing Cue”: Routings under Development
Table 99000764 “Routing Line”: Routing No.
Table 99000770 “Manufacturing Comment Line”: No.
Table 99000773 “Family”: Routing No.
Table 99000775 “Routing Comment Line”: Routing No.
Table 99000786 “Routing Version”: Routing No.
Table 99000802 “Routing Tool”: Routing No.
Table 99000803 “Routing Personnel”: Routing No.
Table 99000805 “Routing Quality Measure”: Routing No.
Table extension 20512 “Subc. Purchase Line”: Subc. Routing No.
Table extension 20513 “Subc. Purch. Rcpt. Line”: Subc. Routing No.
Table extension 20514 “Subc. Purch. Inv. Line”: Subc. Routing No.
Table extension 20515 “Subc. Purch. CrMemo Line”: Subc. Routing No.
Table extension 20516 “Subc. Purchase Line Archive”: Subc. Routing No.
Table extension 20517 “Subc. Transfer Line”: Subc. Routing No.
Table extension 20518 “Subc. Transfer Rcpt. Line Ext”: Subc. Routing No.
Table extension 20519 “Subc. Transfer Shpt. Line Ext”: Subc. Routing No.
Table extension 20523 “Subc. DirectTrans. Line Ext”: Routing No.
Table extension 99000750 “Mfg. Item”: Routing No.
Table extension 99000751 “Mfg. Purchase Line”: Routing No.
Table extension 99000752 “Mfg. Purchase Line Archive”: Routing No.
Table extension 99000754 “Mfg. Purch. Invoice Line”: Routing No.
Table extension 99000755 “Mfg. Purch. Receipt Line”: Routing No.
Table extension 99000757 “Mfg. Item Templ.”: Routing No.
Table extension 99000758 “Mfg. Item Journal Line”: Routing No.
Table extension 99000759 “Mfg. Stockkeeping Unit”: Routing No.
Table extension 99000800 “Mfg. Inventory Adjmt. Entry”: Routing No.
Table extension 99000801 “Mfg. Capacity Ledger Entry”: Routing No.
Table extension 99000820 “Mfg. BOM Buffer”: Routing No.
Table extension 99000860 “Mfg. Requisition Line”: Routing No.

Pages and codeunits on this table

Page 99000764 “Routing List” (source table)
Page 99000766 “Routing” (source table)

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.

Page 456 “No. Series” (2 calls: AssistEdit → (object), OnInsert → (object))

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: "table", object_name: "Routing Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.