OMT Old and New Pricing with Washington - Support and Troubleshooting

OMT Old and New Pricing with Washington Data model changes as part of OMT pricing under Washington release :

Table Name

Field Name

Comments

Order

total_amount

total_discount

total_recurring_price

Deprecated Fields

total_annual_recurring_price

total_monthly_recurring_price

suppress_pricing

Added Fields

Order Line Item

total_price

Deprecated Field

cumulative_monthly_recurring_price

cumulative_one_time_price

cumulative_annual_recurring_price

Periodicity

Added Fields

Pricing Adjustments

adjustment_method

Deprecated Field

adjustment_type

adjustment_source

sequence

Added Fields

Pricing is an option feature in the OMT Washington release.

In Washington, a new UI is introduced for the Order capture process and the Inbuild Pricing feature is available on this UI. We also have an option for existing customers to be on Old UI (can be done through system property configuration)

Support old Order Capture TMT Pricing (existing pricing feature before W release):

Orders created via the old order capture UI do not adhere to the new pricing engine logic. This property sn_app_orm_wksp.pre_washington_order_capture_enabled should be set to true. System property 'pre_washington_order_capture_enabled' under the Configurable Workspace for the Order Management application The mapping of pricing fields can be achieved by transferring the Monthly recurring charges and Non-recurring charges from the product offering to the Total recurring price and Total one-time price of the line item with that specification, accounting for multiples of quantity. If characteristic-based pricing is defined under product offering characteristics for Monthly recurring charges and Non-recurring charges, those values can be copied to Total Recurring Price and Total One-Time Price, respectively, accounting for multiples of quantity. For each order line item, Cumulative monthly recurring price is filled with Total recurring price and similarly Cumulative one time price as Total one time price. As part of roll-up logic, for the parent line Cumulative fields will be sum of parent and all its child's cumulative fields. The cumulative fields of parent lines roll up to match the corresponding pricing field values at the order level.

API Orders TMT pricing (existing pricing feature before W release):

Orders created via the TMF 622 API do not adhere to the new pricing engine logic. For these orders, set the suppress pricing flag to true. While creating the orders from API we are setting the flag value to true. Once that flag is true, no pricing engine call will be triggered. Pricing update will not happen on Quantity or characteristics change on inflight/revision of orders done from UI for API orders, as we are not calling pricelist on API orders/ we don’t have any source to update price. There is no modification to the pricing calculations, only mapping fields from API attributes to new Database fields were changed as part of this release. The recurring charges from the payload will be mapped to Total recurring price and nonRecurring charges will be mapped to Total one time price on the order line items. For each order line item, Cumulative monthly recurring price is filled with Total recurring price and similarly Cumulative one time price as Total one time price. As part of roll up logic, for the parent line Cumulative fields will be sum of parent and all its child's cumulative fields. These cumulative fields of parent line roll up to the corresponding order level pricing field values. Data Migration:

To perform data migration from deprecated old pricing fields to new pricing fields on the existing order and order lines, "Order Pricing fields Data migration" is the On Demand Scheduled job. After the upgrade to Washington, the customer is required to manually execute this scheduled job to perform data migration from the old deprecated order/order line pricing fields to the new pricing fields for all existing orders. This is necessary due to the data model changes implemented as part of the Washington release on order/order lines.

New Pricing released with OMT Washington

Key Configurations for Pricing:

Price List/Price List Line needs to be configured for product offering to support pricing for Product Order. T o perform pricing call, product offering should have pricing method has been selected as Recurring/One time. To support Characteristic based pricing, create and configure Attribute Adjustment and Decision Table for the selected characteristics. To support pricing adjustments there are 2 decision tables to configure. Configuration Component Price Adjustment Matrix – Decision table to configure bundle offering adjustments. Standard Price Adjustment Matrix – Decision table to configure adjustments for any offering. To perform data migration from deprecated old pricing fields to new pricing fields on existing order and order lines, "Order Pricing fields Data migration" is the On Demand Scheduled job.

Pricing Support Feature:

At the time of order line creation, pricing API call will be triggered and populates all the pricing fields on order line item and order. Pricing API triggers on parent line item only in case of product offering with Specification Scenario. The Unit list price on order line derived from price list line which is configured for that selected offering. If any attribute adjustments were defined for the selected characteristics that amount also will be included in the list price of the order line item. If any discount/surcharge want to add for the specific factor like account/city/state etc. we can configure in the decision table with adjustment type and values. These are called Auto pricing adjustments. At the time of order line item creation, these Auto pricing adjustments will be created if any configured. Apart from Auto pricing Adjustments, we can create Manual pricing Adjustments for the selected Order line items. Manual Pricing Adjustments can be created/updated/deleted, but we cannot edit/delete Auto pricing adjustments.

Pricing call Triggers:

On save of order line pricing call will be triggered to get list price and adjustments through after BR on order line item. On change of characteristic option or characteristic insertion, pricing call triggers through after BR on order characteristic table and get list price with adjustments. On change of product offering, UOM, Quantity, price list on the order line form, pricing call will be triggered to get list price. If offering with Spec, in those scenarios pricing call always triggers on parent line item. All child level line items with zero pricing values.

For order/order line pricing fields formulae:

Unit list price -> Unit net price + Total adjustment/quantity Total one time price -> Unit net price * quantity if offering has one time pricing method

Total recurring price -> Unit net price * quantity if offering has recurring pricing method

Cumulative monthly recurring price -> Total recurring price if periodicity is monthly Cumulative annual recurring price -> Total recurring price if periodicity is annually Cumulative one time price -> Total one time price For the parent line item, all these cumulative fields will be updated through the rollup of its child lines' cumulative values in addition to the parent's cumulative values. All cumulative fields of the parent line will be rolled up to the corresponding fields in the order, such as Total One Time Price, Total Monthly Recurring Price, and Total Annual Recurring Price.

Manual Adjustments:

Apart from Auto Adjustments, we can create one manual adjustment per each order line. All the pricing fields can be altered based on this manual adjustment record insertion/deletion.