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

Report 321 "Vendor - Balance to Date"

Base Application · Microsoft.Purchases.Reports

Across versions

  1. BC23-25present
  2. BC261 events added
  3. BC27-28unchanged
  4. BC29declaration changed
  5. BC30unchanged

Neighbourhood 3 connected objects and pages

Codeunit 368 "Format Document" (calls)Format DocumentAccounts payables analytics (Learn pages)Accounts payables analyticsVendor - Balance to Date (report) (Learn pages)Vendor - Balance to Date (re…

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.Reports · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Vendor - Balance to Date
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

Events published

  • OnAfterCalcVendorRemainingAmount(var TempVendorLedgerEntry: Record "Vendor Ledger Entry" temporary; PrintAmountInLCY: Boolean; var RemainingAmt: Decimal; var CurrencyCode: Code[10]) (integration)
  • OnAfterVendLedgEntry3OnAfterGetRecord(VendorLedgerEntry: Record "Vendor Ledger Entry"; PrintAmountInLCY: Boolean; var OriginalAmt: Decimal; var RemainingAmt: Decimal; var CurrencyCode: Code[10]) (integration)
  • OnVendorOnAfterGetRecordOnAfterCalcShouldSkipVendor(var Vendor: Record Vendor; var ShouldSkipVendor: Boolean) (integration)
  • OnCalcTotalVendorAmountOnAfterUpdateCurrencyTotalBuffer(var TempVendorLedgerEntry: Record "Vendor Ledger Entry" temporary; var TempCurrencyTotalBuffer: Record "Currency Total Buffer" temporary; Counter1: Integer; RemainingAmt: Decimal; ShowEntriesWithZeroBalance: Boolean) + BC26 (integration)

Procedures

  • InitializeRequest(NewPrintAmountInLCY: Boolean; NewPrintOnePrPage: Boolean; NewPrintUnappliedEntries: Boolean)

Plus 9 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.

Recent changes

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "Vendor - Balance to Date"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 3 sources