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

Table extension 8002 "Vendor"

Subscription Billing · Microsoft.SubscriptionBilling

Open in Claude8002.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 2 connected objects and pages

Table 23 "Vendor" (relates to)VendorTable 8063 "Vendor Subscription Contract" (relates to)Vendor Subscription Contract

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.

Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29

Extends Vendor.

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
8010 Vendor Contracts Integer Specifies the number of Vendor Subscription Contracts that have been registered for the vendor. via Page extension 8001 “Contr. Vendor H. Buy FactBox” FlowField: count(“Vendor Subscription Contract” where(“Buy-from Vendor No.” = field(“No.”), Active = filter(true))); 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: "Vendor"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources