Codeunit 6482 "Serv. Item Tracking Doc. Mgt."

Base Application · Microsoft.Inventory.Tracking · BC25-30 · source at ea08af5e · facts from BC29

Event subscriptions

• OnRetrieveDocumentItemTracking subscribes to Codeunit “Item Tracking Doc. Management” OnRetrieveDocumentItemTracking
• OnAfterTableSignFactor subscribes to Codeunit “Item Tracking Doc. Management” OnAfterTableSignFactor
• OnAfterGetInvoiceSource subscribes to Page “Item Tracking Lines” OnAfterGetInvoiceSource
• OnAferGetHandleSource subscribes to Page “Item Tracking Lines” OnAfterGetHandleSource

Procedures

3 local procedures, no public ones.

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 6503 “Item Tracking Doc. Management” (4 calls: RetrieveTrackingService → FindReservEntries, RetrieveTrackingService → FindTrackingEntries, RetrieveTrackingServiceInvoice → FindInvoiceEntries, …)

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