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

Report 1322 "Standard Purchase - Order"

Base Application · Microsoft.Purchases.Document

Across versions

  1. BC23-25present
  2. BC26declaration changed
  3. BC27-30unchanged

Neighbourhood 6 connected objects and pages

Codeunit 368 "Format Document" (calls, 5 links)Format DocumentCodeunit 365 "Format Address" (calls, 4 links)Format AddressCodeunit 5051 "SegManagement" (calls, 2 links)SegManagementCodeunit 9520 "Mail Management" (calls)Mail ManagementPurchasing reports and analytical tasks (Learn pages)Purchasing reports and analy…Standard Purchase Order report (Learn pages)Standard Purchase Order report

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 · captioned “Purchase - Order” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Purchase - Order

Events published

  • OnAfterFormatDocumentFields(var PurchaseHeader: Record "Purchase Header") (integration)
  • OnInitReportForGlobalVariable(var IsHandled: Boolean; var LegalOfficeTxt: Text; var LegalOfficeLbl: Text; var CustomGiroTxt: Text; var CustomGiroLbl: Text) (integration)

Procedures

  • InitializeRequest(LogInteractionParam: Boolean)
  • IsReportInPreviewMode(): Boolean (protected)

Plus 3 local procedures.

Triggers

OnInitReport, OnPostReport

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

Countries that replace it

CA, MX, US

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

Evidence 3 sources