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

Table extension 8008 "Usage Based Item Reference"

Subscription Billing · Microsoft.SubscriptionBilling

Open in Claude8008.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Table 5777 "Item Reference" (relates to)Item ReferenceTable 8015 "Usage Data Supplier Reference" (relates to)Usage Data Supplier Reference

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 Item Reference.

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
8000 Supplier Ref. Entry No. Integer Specifies the sequential number of the associated product reference for processing usage-based billing. This is only relevant if you are using Subscription Billing functionalities. via Page extension 8006 “Item Reference Entries” TableRelation Table 8015 “Usage Data Supplier Reference” (“Usage Data Supplier Reference” where(Type = const(Product))); DataClassification CustomerContent

Procedures

  • FindForVendorAndSupplierReference(VendorNo: Code[20]; SupplierReferenceEntryNo: Integer): Boolean (internal)

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

Evidence 1 sources