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

Table 8014 "Usage Data Supplier"

Subscription Billing · Microsoft.SubscriptionBilling

Across versions

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

Neighbourhood 11 connected objects and pages

Table 23 "Vendor" (relates to)VendorPage 8044 "Usage Data Suppliers" (pages and codeunits on it, 3 links)Usage Data SuppliersTable 8012 "Usage Data Supp. Customer" (referenced by, 2 links)Usage Data Supp. CustomerTable 8013 "Usage Data Import" (referenced by, 2 links)Usage Data ImportTable 8015 "Usage Data Supplier Reference" (referenced by, 2 links)Usage Data Supplier ReferenceTable 8016 "Usage Data Supp. Subscription" (referenced by, 2 links)Usage Data Supp. SubscriptionTable 8017 "Generic Import Settings" (referenced by)Generic Import SettingsImport data in usage-based billing (Learn pages)Import data in usage-based b…Usage data supplier references (Learn pages)Usage data supplier referencesUsage data suppliers (Learn pages)Usage data suppliersUsage-based billing customers and subscriptions (Learn pages)Usage-based billing customer…

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

Learn documents this table through its pages: Page 8044 “Usage Data Suppliers” (4 Learn pages).

Properties

Property Value
Caption Usage Data Supplier
DataClassification CustomerContent
LookupPageId Usage Data Suppliers
DrillDownPageId Usage Data Suppliers

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 No. Code[20] Specifies the unique number of the usage data supplier. via Page 8044 “Usage Data Suppliers” NotBlank
2 Description Text[80] Specifies a short description of the supplier of the usage data. via Page 8044 “Usage Data Suppliers”
3 Type Enum “Usage Data Supplier Type” Specifies how to process usage data and synchronize subscriptions. via Page 8044 “Usage Data Suppliers” enum Enum 8015 “Usage Data Supplier Type”
4 Unit Price from Import Boolean Specifies whether the sales price from the usage data should be used. If yes, the pricing is overridden on the basis of the Subscription Line. via Page 8044 “Usage Data Suppliers”
5 Vendor Invoice per Enum “Vendor Invoice Per” Specifies how vendor invoices are generated. You can choose between the generation of a collective invoice per import or an invoice per end customer. via Page 8044 “Usage Data Suppliers” enum Enum 8016 “Vendor Invoice Per”
6 Vendor No. Code[20] — TableRelation Table 23 “Vendor”
7 Vendor Name Text[100] Specifies the vendor that belongs to the usage data supplier. via Page 8044 “Usage Data Suppliers” TableRelation Vendor.Name

Keys

  • PK: No. (clustered)

Procedures

  • OpenSupplierSettings() (internal)

Plus 3 local procedures.

Triggers

OnDelete

Relations

Referenced by

9 fields in 5 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

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: "Usage Data Supplier"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources