Codeunit 6481 "Serv. Item Tracing Mgt."
Base Application · Microsoft.Inventory.Tracking
Across versions
- BC23-24not present
- BC25added
- BC26-27unchanged
- BC282 procedures changed
- BC29-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Inventory.Tracking · BC25-30 · source at ea08af5e · facts from BC29
Events published
OnSetRecordIDOnBeforeProcessServiceDocument(ItemLedgEntry: Record "Item Ledger Entry"; var TrackingEntry: Record "Item Tracing Buffer")(integration)
Event subscriptions
- OnSetRecordIDOnProcessServiceDocument subscribes to Codeunit “Item Tracing Mgt.” OnSetRecordIDOnProcessServiceDocument
- OnShowDocument subscribes to Codeunit “Item Tracing Mgt.” OnShowDocument
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.
- Page 5972 “Posted Service Credit Memo” (1 call:
OnShowDocument → (object)) - Page 5975 “Posted Service Shipment” (1 call:
OnShowDocument → (object)) - Page 5978 “Posted Service Invoice” (1 call:
OnShowDocument → (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: "Serv. Item Tracing Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.