3.1.45 Pricing Quantity
The Pricing Quantity represents the volume of a given SKU associated with a resource or service used or purchased, based on the Pricing Unit. Distinct from Consumed Quantity (complementary to Consumed Unit), it focuses on pricing and cost, not resource and service consumption.
3.1.45.1 Requirements
PricingQuantity adheres to the following requirements:
- PricingQuantity MUST be present in a Cost and Usage FOCUS dataset.
- PricingQuantity MUST be of type Decimal.
- PricingQuantity MUST conform to NumericFormat requirements.
- PricingQuantity nullability is defined as follows:
- PricingQuantity MUST be null when SkuPriceId is null.
- PricingQuantity MUST be null when ChargeCategory is "Tax".
- PricingQuantity MUST NOT be null when ChargeCategory is "Usage" or "Purchase" and ChargeClass is not "Correction".
- PricingQuantity MAY be null in all other cases.
- PricingQuantity MUST be a valid decimal value when not null.
- Cost metric (e.g., ContractedCost) MUST equal the product of the corresponding unit price (e.g., ContractedUnitPrice) and PricingQuantity when the unit price is not null and PricingQuantity is not null.
3.1.45.4 Description
The volume of a given SKU associated with a resource or service used or purchased, based on the Pricing Unit.
3.1.45.5 Usability Constraints
Aggregation: When aggregating Pricing Quantity for commitment utilization calculations, it's important to exclude commitment discount purchases (i.e. when Charge Category is "Purchase") that are paid to cover future eligible charges (e.g., commitment discount). Otherwise, when accounting for all upfront or accrued purchases, it's important to exclude commitment discount usage (i.e. when Charge Category is "Usage"). This exclusion helps prevent double counting of these quantities in the aggregation.
Constraints
| Property | Value |
|---|---|
| Column Type | Metric |
| Feature Level | Mandatory |
| Allows Nulls | Yes |
| Data Type | Decimal |
| Value Format | Numeric Format |