Seasonal Pricing for Price Items in a Deal

Oracle Revenue Management and Billing enables the relationship manager to create a seasonal pricing for a price item. This feature enables the relationship manager to offer different rates for a price item for different periods. You can create a seasonal pricing for a price item by overriding the proposed pricing of the price item which is effective from the deal start date. While creating a seasonal pricing, you need to ensure the following:

  • Start and end dates are specified in the seasonal pricing

  • Start date is later than the deal start date

  • End date is not later than the date which is calculated using the start date and number of months specified in the Validity Period for Deal in Months option type of the C1-Deal feature configuration

  • Price assignment type of the seasonal pricing should be same as the proposed pricing which is overridden

If the proposed pricing which you are overriding to create the seasonal pricing is open-ended (i.e. the end date is not specified in the proposed pricing), the system automatically ends the proposed pricing of the price item. The end date of the proposed pricing is set to Seasonal Pricing Start Date - 1.

You can define more than one seasonal pricing for a price item which is effective during a different date range. However, note that you cannot define more than 10 seasonal pricing for a customer or an account. Along with the proposed pricing, the system sends the seasonal pricing of a price item for product, division, and deal level approval. An approver can only approve the seasonal pricing, but cannot recommend a change in the seasonal pricing. An approver can approve the seasonal pricing when the average price falls within the floor and ceil limits of the approver. The relationship manager or approver can send the seasonal pricing of a price item to the price item manager for approval. In such case, the price item manager can view both proposed and seasonal pricing for the price item. But, the price item manager can only approve the seasonal pricing of the price item.

You cannot specify the commitments for the seasonal pricing in the deal. By default, the system considers the commitments of the proposed pricing while calculating the revenue from the seasonal pricing. Also, the system does not consider the seasonal pricing of a price item while calculating the product, division, and deal level financial summary. The system only considers the proposed pricing of a price item while calculating the product, division, and deal level financial summary. You can view the revenue generated for a price item from the seasonal pricing in the Pricing and Commitments screen.

If the seasonal pricing is created for a price item with the assignment level other than Customer Agreed or Account Agreed, the system will automatically consider the proposed pricing of the price item after the seasonal pricing's effective end date. However, if the seasonal pricing is created for a price item with the assignment level as Customer Agreed or Account Agreed, the relationship manager will have to create a new seasonal pricing for the price item for the remaining deal period.

The following table illustrates different seasonal pricing scenarios at different assignment levels:
Scenario Assignment Level Proposed Pricing Seasonal Pricing
Start Date End Date Start Date End Date
Scenario 1 Customer Price List or Account Price List 01-01-2021 31-12-2021 01-03-2021 30-06-2021
Scenario 2 Customer Agreed or Account Agreed 01-01-2021 31-12-2021 01-02-2021 31-05-2021

In scenario 1, the system considers the proposed pricing of the price item after the seasonal pricing of the price item is expired. However, in scenario 2, the relationship manager will have to create a new seasonal pricing for the price item which is effective from 01-06-2021 to 31-12-2021.