BC Observatoryunofficial, made by waldo
reportPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Report 409 "Purchase Reservation Avail."

Base Application · Microsoft.Purchases.Document

Open in Claude409.mdSource on GitHub

Across versions

  1. BC23-28present
  2. BC29declaration changed
  3. BC30unchanged

Neighbourhood 2 connected objects and pages

Analytics in purchasing (Learn pages)Analytics in purchasingPurchase Reservation Availability (report) (Learn pages)Purchase Reservation Availab…

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

Properties

Property Value
Caption Purchase Reservation Avail.
UsageCategory ReportsAndAnalysis
ApplicationArea Reservation

Events published

  • OnAfterPurchLineModify(var PurchLine: Record "Purchase Line") (integration)

Procedures

  • InitializeRequest(NewShowPurchLines: Boolean; NewShowReservationEntries: Boolean; NewModifyQtyToShip: Boolean)

Triggers

OnPreReport

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). 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: "Purchase Reservation Avail."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 3 sources