3.38 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.

The PricingQuantity column adheres to the following requirements:

• PricingQuantity MUST be present in a 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 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.
• When PricingQuantity is not null, PricingQuantity adheres to the following additional requirements:
  • PricingQuantity MUST be a valid decimal value.
  • The product of PricingQuantity and a unit price (e.g., ContractedUnitPrice) MUST match the corresponding cost metric (e.g., ContractedCost) when the unit price is not null and ChargeClass is not "Correction".
• Discrepancies in PricingQuantity, unit prices (e.g., ContractedUnitPrice), or costs (e.g., ContractedCost) MAY exist when ChargeClass is "Correction".

The volume of a given SKU associated with a resource or service used or purchased, based on the Pricing Unit.

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.