WHEN_T In Schedule Object Is Getting Rounded To Midnight (Doc ID 2188942.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.14.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

On BRM 7.5.0.14.0 version in Subscription Management

Scenario:

When a product is purchased through subscription_purchase_deal opcode with end_offset and end_unit set, a schedule is created.

The product was purchased on 28th Sept 14:00 with end offset of 24 hours but the schedule object's when_t was Sept 29 00:00.  As a result, the product got cancelled before end_t.

How this can be avoided ?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms