Report 6521 "Item Tracking Appendix"
Base Application · Microsoft.Inventory.Reports
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Reports · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Item Tracking Appendix |
Procedures
IsStartNewGroup(var TempTrackingSpecification: Record "Tracking Specification" temporary): Boolean
Plus 14 local procedures.
Triggers
OnPreReport
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 365 “Format Address” (7 calls:
AddressInvoiceHdr → SalesInvBillTo,AddressPurchaseHdr → PurchHeaderBuyFrom,AddressPurchaseHdr → PurchHeaderPayTo, …) - Codeunit 6503 “Item Tracking Doc. Management” (4 calls:
HandleInvoice → RetrieveDocumentItemTracking,HandlePurchase → RetrieveDocumentItemTracking,HandleSales → RetrieveDocumentItemTracking, …)
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: "report", object_name: "Item Tracking Appendix"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.