tableextensionSales & Receivablesofficial - Microsoftderived - from the source, no model text

Table extension 8001 "Contracts Customer"

Subscription Billing · Microsoft.SubscriptionBilling

Across versions

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

Neighbourhood 3 connected objects and pages

Table 18 "Customer" (relates to)CustomerTable 8052 "Customer Subscription Contract" (relates to)Customer Subscription ContractTable 8057 "Subscription Header" (relates to)Subscription Header

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

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 Cust. Subscription Contracts Integer Specifies the number of Customer Subscription Contracts that have been registered for the customer. via Page extension 8000 “Contract Sales H. Sell Factbox” FlowField: count(“Customer Subscription Contract” where(“Sell-to Customer No.” = field(“No.”), Active = filter(true))); not editable
8011 Subscription Headers Integer Specifies the number of Subscriptions that have been registered for the customer. via Page extension 8000 “Contract Sales H. Sell Factbox” FlowField: count(“Subscription Header” where(“End-User Customer No.” = field(“No.”))); 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: "Contracts Customer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources