Rate Management

"Rate Management doesn't support CSV based decision tables and decision matrices." (p.514) All lookup tables must be native Salesforce lookup tables or the predefined tables shipped with Rate Management. Comuniqa cannot bulk-import ARS rate updates via CSV. Rate changes must use Rate Card Entry records via the UI or Salesforce API, following the Draft → Active → Inactive lifecycle.

Starting Summer '25, admins can choose between decision tables and real-time data for rating procedures. Real-time data ensures accuracy but impacts performance. Decision tables enhance performance but require manual updates when rates change. Real-time data does not support the "not matches" or "contains" operators. Real-time support is available for: Get Binding Object Rate Adjustment, Get Binding Object Rate Card Entries, Negotiated Rate Card Entries, Negotiated Base Rate, Negotiated Volume-Based Rate Adjustment, and Commitment Rate Adjustment elements.

"Enable Transaction Management to view and invoke the asset-based lookup tables involved in the negotiable rating procedure." (p.514) This includes Asset Rate Card Entry 2, Asset Rate 2, Asset Tier-based Rate Adjustment 2, and related tables. The alternative is creating custom lookup tables. For any Comuniqa segment requiring asset-level negotiated rates, this is a prerequisite — not optional.

"The default rating procedure uses the Usage Ratable Summary object, which isn't generally available." (p.569) Access requires contacting a Salesforce account executive. Alternatively, create custom context mappings using a custom context definition. This must be resolved before any rating procedure can be activated against real data.

Per documentation p.511: "For runtime users to access the data created by rating designers, managers or catalog admins, set up record sharing for all the Rate Management entities." Record sharing must be configured (via Organization-Wide Defaults or Sharing Rules) for: Rate Card, Unit of Measure, Usage Resource, Rating Frequency Policy, Rating Request, and Expression Sets. The Rate Management Run Time User permission set provides Read access to relevant objects — this must be assigned to all runtime users. Without this, rating procedures will fail at runtime even if the design is correct.

Per documentation p.502: "To create Unit of Measure records for Rate Management, you must add picklist values for the Type field on the Unit Of Measure object." This requires a Setup step in Object Manager before any UoM records (GB, ARS, etc.) can be created. The Type dropdown on a new UoM record will be empty until these picklist values (e.g. Currency, Volume) are added. This is a common blocker when starting a fresh org implementation.

Rate Management is not supported on mobile devices. All Rate Management configuration — Rate Card management, RCE lifecycle operations, Rating Procedure builder access — must be performed from desktop environments.

The Rounding Values element sets rounding precision for single-currency orgs. When multicurrency is enabled, org currency settings determine precision and the Precision variable on the element is not used. The element determines currency values for outputs of preceding elements such as Manual Rate Discount and Volume-Based Rate Discount. For Comuniqa (ARS, single currency), this element must be present with Precision mapped to a constant of 0.

Before any procedure design or RCE configuration: (1) Add UoM Type picklist values in Object Manager; (2) Enable Rate Management via Setup → Usage Management → Usage Management Settings; (3) Enable Rating Waterfall via Setup → Usage Management → Rate Management Setup (requires Design Time permission); (4) Enable Waterfall Persistence (requires Admin permission); (5) Set up record sharing for runtime users. These steps cannot be done in reverse order and are not automatically triggered by enabling RCA.

The documentation instructs users to create procedures by cloning predefined templates from Expression Set Templates. The correct path: Expression Set Templates → select template → Details tab → Rating Procedure Versions section → click version → builder opens → Save As | New Rating Procedure. Building from scratch risks missing mandatory context mappings, pre-wired lookup table registrations, the Status constant mapping on Base Rate, and correct usage type registration.

The documented RCE lifecycle is Draft → Active → Inactive. The correct rate revision sequence: (1) create new RCE in Draft with future effective start date; (2) set explicit end date on current Active entry; (3) activate new RCE; (4) deactivate old one. This prevents two simultaneously active entries for the same resource/product/UoM/selling model combination — a critical risk for Comuniqa's frequent ARS updates.

One Default procedure covers all products where rates are centrally defined; one Negotiable procedure covers all customers where asset-level rates have been negotiated. Product differentiation is handled inside the procedure via Rate Card lookup — not by having separate procedures per product. Fewer procedures means fewer versions to maintain.

Use the Simulate tool as a mandatory validation step. Input via JSON (Advanced) for exact ID and quantity specification. The Waterfall View shows every calculation step. "When you're happy with the simulation result, click Activate." (p.522) For Comuniqa, test: zero overage (TotalAmount = 0), consumption at exact tier boundary values (inclusive), and maximum expected overage volumes.