codeunitService Managementofficial - Microsoftderived - from the source, no model text

Codeunit 1414 "Service Shipment Header - Edit"

Base Application · Microsoft.Service.History

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28-30unchanged

Neighbourhood 3 connected objects and pages

Table 5990 "Service Shipment Header" (relates to)Service Shipment HeaderPage 1358 "Posted Service Ship. - Update" (calls)Posted Service Ship. - UpdatePage 5975 "Posted Service Shipment" (calls)Posted Service Shipment

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Service.History · BC27-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Service Shipment Header
Permissions TableData “Service Shipment Header” = m

Events published

  • OnBeforeServiceShptHeaderModify(var ServiceShipmentHeader: Record "Service Shipment Header"; ServiceShipmentHeader2: Record "Service Shipment Header") (integration)

Procedures

  • ModifyServiceShipment(var ServiceShptHeader2: Record "Service Shipment Header")

Relations

Called by

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.

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

Evidence 1 sources