codeunitPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Codeunit 9091 "Top Five Vendors Chart"

Base Application · Microsoft.Purchases.Vendor

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28-30unchanged

Neighbourhood 4 connected objects and pages

Codeunit 9059 "Acc. Payable Performance" (calls, 3 links)Acc. Payable PerformanceCodeunit 9089 "Top Vendors By Purchases Job" (calls)Top Vendors By Purchases JobPage 26 "Vendor Card" (calls)Vendor CardPage 27 "Vendor List" (calls)Vendor List

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.Purchases.Vendor · BC27-30 · source at ea08af5e · facts from BC29

Procedures

  • UpdateChart(var BusChartBuf: Record "Business Chart Buffer"): Update the chart with the top 5 vendors by purchases.
  • DrillDown(var BusChartBuf: Record "Business Chart Buffer"): Drill down to the vendor card or vendor list page based on the selected vendor.

Plus 4 local procedures.

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: "Top Five Vendors Chart"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources