Codeunit 8025 "Import And Process Usage Data"
Subscription Billing · Microsoft.SubscriptionBilling
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SingleInstance | true |
| TableNo | Usage Data Import |
Procedures
CreateUsageDataCustomer(CustomerId: Text[80]; UsageDataSupplierReference: Record "Usage Data Supplier Reference"; SupplierNo: Code[20])CreateUsageDataSubscription(SubscriptionID: Text[80]; CustomerID: Text[80]; ProductID: Text[80]; ProductName: Text[100]; Unit: Text[80]; Quantity: Decimal; SubscriptionStartDate: Date; SubscriptionEndDate: Date; UsageDataSupplierReference: Record "Usage Data Supplier Reference"; SupplierNo: Code[20])GetServiceCommitmentForSubscription(SupplierNo: Code[20]; SubscriptionReference: Text[80]; var ServiceCommitment: Record "Subscription Line"): BooleanAvailableServiceObjectExist(var UsageDataImport: Record "Usage Data Import"; SubscriptionID: Text[80]): Boolean(internal)
Triggers
OnRun
Relations
- runs on Table 8013 “Usage Data Import”
Recent changes
- 2026-09-25 #9293 [Bug][SubscriptionBilling] Process Usage Data Billing uses lines marked Processing Status = Error (currency mismatch) (main, BC30, fix)
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: "codeunit", object_name: "Import And Process Usage Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.