Table 5903 "Service Order Type"

Base Application · Microsoft.Service.Setup · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Service Order Type
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	Code Δ BC28	Code[10]	Specifies a code for the service order type.	NotBlank
2	Description Δ BC28	Text[100]	Specifies a description of the service order type.

Keys

Key1: Code (clustered)

Trigger event subscribers

OnBeforeInsertEvent: Codeunit 5999 “Service Experience Tier” BlockInsertServiceOrderType

Triggers

OnDelete, OnRename

Relations

lookup page Page 5908 “Service Order Types”

Referenced by

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

Table 5900 “Service Header”: Service Order Type
Table 5907 “Service Ledger Entry”: Service Order Type
Table 5965 “Service Contract Header”: Service Order Type
Table 5968 “Service Contract Template”: Service Order Type
Table 5970 “Filed Service Contract Header”: Service Order Type
Table 5990 “Service Shipment Header”: Service Order Type
Table 5992 “Service Invoice Header”: Service Order Type
Table 5994 “Service Cr.Memo Header”: Service Order Type
Table 6010 “Service Header Archive”: Service Order Type

Pages and codeunits on this table

Page 5908 “Service Order Types” (source table)

Extended by

Table extension 6619 “FS Service Order Type”

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 408 “DimensionManagement” (2 calls: OnDelete → DeleteDefaultDim, OnRename → RenameDefaultDim)

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: "Service Order Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.