codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 391 "Shipment Header - Edit"

Base Application · Microsoft.Sales.History

Across versions

  1. BC23-26present
  2. BC271 events added
  3. BC28-30unchanged

Neighbourhood 3 connected objects and pages

Table 110 "Sales Shipment Header" (relates to)Sales Shipment HeaderCodeunit 30279 "Shpfy Update Sales Shipment" (event subscribers)Shpfy Update Sales ShipmentPage 1350 "Posted Sales Shipment - Update" (calls)Posted Sales Shipment - Update

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.Sales.History · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Sales Shipment Header
Permissions TableData “Sales Shipment Header” = rm

Events published

  • OnBeforeSalesShptHeaderModify(var SalesShptHeader: Record "Sales Shipment Header"; FromSalesShptHeader: Record "Sales Shipment Header") (integration)
  • OnRunOnAfterSalesShptHeaderEdit(var SalesShptHeader: Record "Sales Shipment Header") (integration)
  • OnRunOnBeforeAssignValues(var SalesShipmentHeader: Record "Sales Shipment Header"; SalesShipmentHeaderRec: Record "Sales Shipment Header") + BC27 (integration)

Triggers

OnRun

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.

Countries that replace it

IT

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

Evidence 1 sources