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

Report 6641 "Return Order"

Base Application · Microsoft.Purchases.Document

Across versions

  1. BC23present
  2. BC242 events changed
  3. BC25unchanged
  4. BC26declaration changed
  5. BC27-28unchanged
  6. BC29declaration changed
  7. BC30unchanged

Neighbourhood 4 connected objects and pages

Codeunit 365 "Format Address" (calls, 4 links)Format AddressCodeunit 368 "Format Document" (calls, 3 links)Format DocumentCodeunit 5051 "SegManagement" (calls, 2 links)SegManagementCodeunit 9520 "Mail Management" (calls)Mail Management

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

Countries that replace it

CH

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.

Evidence 1 sources