Page 8044 "Usage Data Suppliers"
Subscription Billing · Microsoft.SubscriptionBilling
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 6 connected objects and pages
Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Usage Data Suppliers |
| SourceTable | Usage Data Supplier |
| PageType | List |
| UsageCategory | Lists |
| 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 | No. | No. | Specifies the unique number of the usage data supplier. |
| Description | Description | Specifies a short description of the supplier of the usage data. | |
| Vendor Name | Vendor Name | Specifies the vendor that belongs to the usage data supplier. | |
| Type | Type | Specifies how to process usage data and synchronize subscriptions. | |
| Unit Price from Import | Unit Price from Import | 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. | |
| Vendor Invoice per | 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. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Settings | Opens the supplier settings relevant for Usage Data Import. | |
| Usage Data Imports | Opens the “Usage data imports” related to the supplier. | Page 8041 “Usage Data Imports” |
Relations
- source table Table 8014 “Usage Data Supplier”
Pages and codeunits on this table
- Table 8014 “Usage Data Supplier” (drill-down page)
- Table 8014 “Usage Data Supplier” (lookup page)
Documented on Microsoft Learn
- Usage-based billing customers and subscriptions
- Usage data supplier references
- Usage data suppliers
- Import data in usage-based billing
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 Suppliers"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.