BC Observatoryunofficial, made by waldo
tableextensionPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table extension 6469 "Serv. Reason Code"

Base Application · Microsoft.Foundation.AuditCodes

Open in Claude6469.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 231 "Reason Code" (relates to)Reason CodeTable 5969 "Contract Gain/Loss Entry" (relates to)Contract Gain/Loss Entry

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.Foundation.AuditCodes · BC25-30 · source at ea08af5e · facts from BC29

Extends Reason Code.

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
5900 Date Filter Date — FlowFilter
5901 Contract Gain/Loss Amount Δ BC28 Decimal — FlowField: sum(“Contract Gain/Loss Entry”.Amount where(“Reason Code” = field(Code), “Change Date” = field(“Date Filter”))); not editable

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "tableextension", object_name: "Serv. Reason Code"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources