Codeunit 9065 "Check Service Document"

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

Properties

Events published

• OnBeforeCheckServiceLines(Item: Record Item; CurrentFieldNo: Integer; CheckFieldNo: Integer; CheckFieldCaption: Text; var IsHandled: Boolean) + BC25 (integration)
• OnBeforeCheckServiceContractLines(Item: Record Item; CurrentFieldNo: Integer; CheckFieldNo: Integer; CheckFieldCaption: Text; var IsHandled: Boolean) + BC25 (integration)

Event subscriptions

• ItemOnBeforeCheckDocuments subscribes to Table “Item” OnAfterCheckDocuments

Procedures

• CheckServiceLines(Item: Record Item; CurrentFieldNo: Integer; CheckFieldNo: Integer; CheckFieldCaption: Text) + BC25 (internal)
• CheckServiceContractLines(Item: Record Item; CurrentFieldNo: Integer; CheckFieldNo: Integer; CheckFieldCaption: Text) + BC25 (internal)

Plus 1 local procedures.

Triggers

OnRun

Relations

• runs on Table 5900 “Service Header”

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 5980 “Service-Post” (1 call: RunCheck → CheckServiceDocument)

Called by

• Codeunit 9084 “Check Service Doc. Backgr.” (1 call: RunServiceDocCheckCodeunit → (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: "codeunit", object_name: "Check Service Document"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.