Page 8096 "Usage Data Billing Metadata"
Subscription Billing · Microsoft.SubscriptionBilling
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Usage Data Billing Metadata |
| SourceTable | Usage Data Billing Metadata |
| PageType | List |
| UsageCategory | Administration |
| 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 | Service Object No. | Subscription No. | Specifies the number of the related Subscription. |
| Service Commitment Entry No. | Subscription Line Entry No. | Specifies the number of the related Subscription Line line. | |
| Supplier Charge Start Date | Supplier Charge Start Date | Specifies the start date of the usage provided by the supplier | |
| Supplier Charge End Date | Supplier Charge End Date | Specifies the end date of the usage provided by the supplier. | |
| Original Invoiced to Date | Original Invoiced to Date | Specifies the date up to which the Subscription Line was originally invoiced. | |
| Invoiced | Invoiced | Specifies whether the related usage data billing is invoiced. | |
| Rebilling | Rebilling | Specifies whether the related usage data billing comes out of a rebilling scenario. | |
| Billing Document Type | Billing Document Type | Specifies which document type was used to post the associated usage data. | |
| Billing Document No. | Billing Document No. | Specifies which document no. was used to post the associated usage data. |
Relations
- source table Table 8021 “Usage Data Billing Metadata”
Pages and codeunits on this table
- Table 8021 “Usage Data Billing Metadata” (drill-down page)
- Table 8021 “Usage Data Billing Metadata” (lookup page)
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 Billing Metadata"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.