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

Codeunit 9089 "Top Vendors By Purchases Job"

Base Application · Microsoft.Purchases.Vendor

Across versions

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

Neighbourhood 3 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryCodeunit 9059 "Acc. Payable Performance" (calls)Acc. Payable PerformanceCodeunit 9091 "Top Five Vendors Chart" (calls)Top Five Vendors Chart

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

Properties

Property Value
TableNo Job Queue Entry

Event subscriptions

  • OnFindingIfJobNeedsToBeRun subscribes to Table “Job Queue Entry” OnFindingIfJobNeedsToBeRun

Procedures

  • UpdateVendorTop10List(): Updates the vendors by purchases buffer with top 10 vendors.

Plus 1 local procedures.

Triggers

OnRun

Relations

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 Vendors By Purchases Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources