Report 405 "Order"

Base Application · Microsoft.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnAfterInitReport() Δ BC24 (integration)
• OnAfterPostDataItem(var PurchaseHeader: Record "Purchase Header") Δ BC24 (integration)
• OnAfterGetRecordRoundLoopOnBeforeAssignPurchaseLine(var TempPurchaseLine: Record "Purchase Line" temporary) + BC27 (integration)

Procedures

• InitializeRequest(NewNoOfCopies: Integer; NewShowInternalInfo: Boolean; NewArchiveDocument: Boolean; NewLogInteraction: Boolean)

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

• Codeunit 368 “Format Document” (5 calls: FormatDocumentFields → SetPaymentTerms, FormatDocumentFields → SetPurchaser, FormatDocumentFields → SetShipmentMethod, …)
• Codeunit 365 “Format Address” (4 calls: FormatAddressFields → GetCompanyAddr, FormatAddressFields → PurchHeaderBuyFrom, FormatAddressFields → PurchHeaderPayTo, …)
• Codeunit 5051 “SegManagement” (2 calls: InitLogInteraction → FindInteractionTemplateCode, OnPostReport → LogDocument)
• Codeunit 9520 “Mail Management” (1 call: IsReportInPreviewMode → IsHandlingGetEmailBody)

Countries that replace it

CH, ES

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