BC Observatoryunofficial, made by waldo
codeunitInventoryofficial - Microsoftderived - from the source, no model text

Codeunit 6483 "Serv. Item Tracking Mgt."

Base Application · Microsoft.Inventory.Tracking

Open in Claude6483.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-27unchanged
  4. BC282 procedures changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 6500 "Item Tracking Management" (calls)Item Tracking ManagementTable 5991 "Service Shipment Line" (calls)Service Shipment Line

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.Inventory.Tracking · BC25-30 · source at ea08af5e · facts from BC29

Event subscriptions

  • OnIsOrderNetworkEntity subscribes to Codeunit “Item Tracking Management” OnIsOrderNetworkEntity
  • OnAfterItemTrkgTypeIsManagedByWhse subscribes to Codeunit “Item Tracking Management” OnAfterItemTrkgTypeIsManagedByWhse

Procedures

  • CopyHandledItemTrkgToServLine(FromServLine: Record "Service Line"; ToServLine: Record "Service Line")

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.

Called by

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: "Serv. Item Tracking Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources