BC Observatoryunofficial, made by waldo
tablePurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Table 267 "Vendor Amount"

Base Application · Microsoft.Purchases.Vendor

Open in Claude267.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC282 fields changed
  5. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Table 23 "Vendor" (relates to)Vendor

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

Properties

Property Value
Caption Vendor Amount
DataClassification CustomerContent

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
1 Vendor No. Code[20] — TableRelation Table 23 “Vendor”
2 Amount (LCY) Δ BC28 Decimal —
3 Amount 2 (LCY) Δ BC28 Decimal —

Keys

  • Key1: Amount (LCY), Amount 2 (LCY), Vendor No. (clustered)

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

Evidence 1 sources