Table 8021 "Usage Data Billing Metadata"

Subscription Billing · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 8096 “Usage Data Billing Metadata” (1 Learn page).

Properties

Property	Value
Caption	Usage Data Billing Metadata
Access	Internal
DataClassification	CustomerContent
LookupPageId	Usage Data Billing Metadata
DrillDownPageId	Usage Data Billing Metadata

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	Entry No.	Integer	—	AutoIncrement
2	Usage Data Billing Entry No.	Integer	Entry No. caption	TableRelation Table 8006 “Usage Data Billing” (Usage Data Billing)
3	Subscription No.	Code[20]	Specifies the number of the related Subscription. via Page 8096 “Usage Data Billing Metadata”	TableRelation Table 8057 “Subscription Header” (Subscription Header)
4	Subscription Line Entry No.	Integer	Specifies the number of the related Subscription Line line. via Page 8096 “Usage Data Billing Metadata”	TableRelation Table 8059 “Subscription Line” (Subscription Line)
5	Supplier Charge Start Date	Date	Specifies the start date of the usage provided by the supplier via Page 8096 “Usage Data Billing Metadata”
6	Supplier Charge End Date	Date	Specifies the end date of the usage provided by the supplier. via Page 8096 “Usage Data Billing Metadata”
7	Original Invoiced to Date	Date	Specifies the date up to which the Subscription Line was originally invoiced. via Page 8096 “Usage Data Billing Metadata”
8	Invoiced	Boolean	Specifies whether the related usage data billing is invoiced. via Page 8096 “Usage Data Billing Metadata”
9	Rebilling	Boolean	Specifies whether the related usage data billing comes out of a rebilling scenario. via Page 8096 “Usage Data Billing Metadata”
10	Billing Document Type	Enum “Usage Based Billing Doc. Type”	Specifies which document type was used to post the associated usage data. via Page 8096 “Usage Data Billing Metadata”	FlowField: lookup(“Usage Data Billing”.“Document Type” where(“Entry No.” = field(“Usage Data Billing Entry No.”))); enum Enum 8008 “Usage Based Billing Doc. Type”; not editable
11	Billing Document No.	Code[20]	Specifies which document no. was used to post the associated usage data. via Page 8096 “Usage Data Billing Metadata”	FlowField: lookup(“Usage Data Billing”.“Document No.” where(“Entry No.” = field(“Usage Data Billing Entry No.”))); not editable

Keys

PK: Entry No. (clustered)

Procedures

InsertFromUsageDataBilling(UsageDataBilling: Record "Usage Data Billing") (internal)
FilterOnServiceCommitment(ServiceCommitmentEntryNo: Integer) (internal)

Relations

drill-down page Page 8096 “Usage Data Billing Metadata”
lookup page Page 8096 “Usage Data Billing Metadata”
Billing Document No.: CalcFormula Table 8006 “Usage Data Billing”
Billing Document Type: CalcFormula Table 8006 “Usage Data Billing”
Usage Data Billing Entry No.: TableRelation Table 8006 “Usage Data Billing”
Subscription No.: TableRelation Table 8057 “Subscription Header”
Subscription Line Entry No.: TableRelation Table 8059 “Subscription Line”

Pages and codeunits on this table

Page 8096 “Usage Data Billing Metadata” (source 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 Billing Metadata"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.