1. Using Revenue Management
  2. Service Duration and Price Periodicity Impact on Existing Contracts

Service Duration and Price Periodicity Impact on Existing Contracts

You may or may not see the service duration and price periodicity on your revenue contracts, depending on whether the revenue contract was created before or after you began using the feature:

  • Contracts created before you begin providing the service duration and price periodicity for services: the application displays the contracts without the service duration and price periodicity.
  • Contracts created after you begin providing the service duration and price periodicity for services: the application displays the contracts with the service duration and price periodicity, if these values are populated by the integrated application.
  • Contracts created before you begin providing the service duration and price periodicity for services but revised after you began using this feature: the application displays the base contract without the service duration and price periodicity.
    • When you perform revisions to existing contracts, for the service duration and price periodicity values on services not previously provided for the line, if the integrating application is Subscription Management, Revenue Management uses the value in the Extensible line character attribute 30 column to determine how to treat the new service duration and price periodicity values.

The Subscription Management user populates the Extensible line character attribute 30 column and Revenue Management processes the line as follows:

Source Application Scenario Extensible Line Character Attribute 30 Revenue Management Treatment
Subscription Management When you override the values of Quantity, Unit Selling Price, or Unit Standalone Selling Price using Service Mapper. Equal to CUSTOM The application processes the version line as it was received from Subscription Management. The revenue line is displayed with the service duration and price periodicity.
Subscription Management When you don't override the values of Quantity, Unit Selling Price, or Unit Standalone Selling Price using Service Mapper. Not equal to CUSTOM
  • If you override the values of Quantity, Unit Selling Price, or Unit The application ignores the service duration and price periodicity populated in the version lines.
  • The application calculates the unit selling price as Unit Selling Price * Service Duration on the revenue contract.
  • The application copies the unit standalone selling price of the base revenue line to the version line as well.
  • The promised service is represented as if it was imported from Subscription Management without the service duration and price periodicity.
All other sources Not applicable The invalid version line is displayed in the Correct Contract Document Errors spreadsheet. Remove the values for the two attributes and reprocess the line.

Refer to Using Oracle Subscription Management for more information.