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

Page 8035 "Usage Data Billings"

Subscription Billing · Microsoft.SubscriptionBilling

Across versions

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

Neighbourhood 3 connected objects and pages

Table 8006 "Usage Data Billing" (relates to)Usage Data BillingTable 8006 "Usage Data Billing" (pages and codeunits on it, 2 links)Usage Data BillingImport data in usage-based billing (Learn pages)Import data in usage-based b…

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

Properties

Property Value
Caption Usage Data Billings
SourceTable Usage Data Billing
PageType List
ApplicationArea All

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
General Entry No. Entry No. Specifies the sequential number assigned to the record when it was created.
Usage Data Import Entry No. Usage Data Import Entry No. Specifies the sequential number of the related import that was assigned to it when it was created.
Supplier No. Supplier No. Specifies the number of the supplier to which this usage data refers.
Partner Partner Specifies whether the Subscription Line partner is a customer or a vendor.
Contract No. Subscription Contract No. Specifies the contract on which the usage data is billed.
Contract Line No. Subscription Contract Line No. Specifies the contract line through which the usage data is billed.
Service Object No. Subscription Header No. Specifies the number of the related Subscription.
Service Object Description Subscription Description Specifies the description of the related Subscription.
Service Commitment Description Subscription Line Description Specifies the Subscription Line for which the usage data is billed.
Product ID Product ID Specifies the unique ID of the product for this subscription with the supplier. from the table field
Product Name Product Name Specifies the vendor’s product name for this subscription. from the table field
Processing Status Processing Status Specifies whether the row has been processed. In case of an error during processing, it is displayed in the “Reason (Preview)” field. from the table field
Processing Date Processing Date Specifies the date of processing.
Processing Time Processing Time Specifies the time of processing.
Reason (Preview) Reason (Preview) Specifies the preview why the last processing step failed.
Charge Start Date Charge Start Date Specifies the start date of the usage.
Charge End Date Charge End Date Specifies the end date of the usage.
Charged Period (Days) Charged Period (Days) Specifies the calculated period (in days).
Charged Period (Hours) obsolete Pending 26.0; #if not CLEAN26 Charged Period (Hours) Specifies the calculated period (in hours).
Quantity Quantity Specifies the quantity.
Unit Cost Unit Cost Specifies the unit cost.
Cost Amount Cost Amount Specifies the total cost.
Unit Price Unit Price Specifies the unit price.
Amount Amount Specifies the total amount.
Currency Code Currency Code Specifies the currency code.
Usage Base Pricing Usage Base Pricing Specifies the criterion used to calculate the usage based pricing.
Pricing Unit Cost Surcharge % Pricing Unit Cost Surcharge % Specifies the unit cost surcharge for usage-dependent pricing.
Billing Line Entry No. Billing Line Entry No. Specifies the billing line through which the usage data is billed.
Document Type Document Type Specifies the document type through which the usage data will be invoiced.
Document No. Document No. Specifies the document number via which the usage data is billed.
Document Line No. Document Line No. Specifies the document line for which the usage data will be billed.

Actions

Group Action ToolTip Runs
Navigation Usage Data Metadata Shows the metadata related to the Subscription Line.

Relations

Pages and codeunits on this table

Recent changes

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 2 sources