BC Observatoryunofficial, made by waldo
codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 1407 "Return Receipt Header - Edit"

Base Application · Microsoft.Sales.History

Open in Claude1407.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 6660 "Return Receipt Header" (relates to)Return Receipt HeaderPage 1353 "Posted Return Receipt - Update" (calls)Posted Return Receipt - Update

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

Properties

Property Value
TableNo Return Receipt Header
Permissions TableData “Return Receipt Header” = rm

Events published

  • OnBeforeReturnReceiptHeaderModify(var ReturnReceiptHeader: Record "Return Receipt Header"; ReturnReceiptHeaderRec: Record "Return Receipt Header") (integration)
  • OnRunOnAfterReturnReceiptHeaderEdit(var ReturnReceiptHeader: Record "Return Receipt Header") (integration)

Triggers

OnRun

Relations

Called by

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.

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: "codeunit", object_name: "Return Receipt Header - Edit"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources