Report 6641 "Return Order"
Base Application · Microsoft.Purchases.Document
Across versions
- BC23present
- BC242 events changed
- BC25unchanged
- BC26declaration changed
- BC27-28unchanged
- BC29declaration changed
- BC30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Return Order |
Events published
OnAfterInitReport()Δ BC24 (integration)OnAfterPostDataItem(var PurchaseHeader: Record "Purchase Header")Δ BC24 (integration)
Procedures
4 local procedures, no public ones.
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 365 “Format Address” (4 calls:
FormatAddressFields → GetCompanyAddr,FormatAddressFields → PurchHeaderBuyFrom,FormatAddressFields → PurchHeaderPayTo, …) - Codeunit 368 “Format Document” (3 calls:
FormatDocumentFields → SetPurchaser,FormatDocumentFields → SetText,FormatDocumentFields → SetTotalLabels) - Codeunit 5051 “SegManagement” (2 calls:
InitLogInteraction → FindInteractionTemplateCode,OnPostReport → LogDocument) - Codeunit 9520 “Mail Management” (1 call:
IsReportInPreviewMode → IsHandlingGetEmailBody)
Countries that replace it
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: "Return Order"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.