Report 5900 "Service Order"

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

Properties

Procedures

• InitializeRequest(ShowInternalInfoFrom: Boolean; ShowQtyFrom: Option)

Plus 2 local procedures.

Triggers

OnInitReport

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 6001 “Service Format Address” (2 calls: FormatAddressFields → ServiceOrderSellto, FormatAddressFields → ServiceOrderShipto)
• Codeunit 365 “Format Address” (1 call: FormatAddressFields → GetCompanyAddr)
• Codeunit 368 “Format Document” (1 call: OnInitReport → SetLogoPosition)
• Codeunit 9520 “Mail Management” (1 call: IsReportInPreviewMode → IsHandlingGetEmailBody)

Countries that replace it

CA, MX, US

Documented on Microsoft Learn

• Service Order (document report)
• Service management reports

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