PCM_OP_SUBSCRIPTION_SET_VALIDITY_FROM_STRING Wrongly set the Effective_t of the Product with Offset (Doc ID 2243922.1)

Last updated on NOVEMBER 20, 2019

Applies to:

Symptoms

On : 7.5.0.10.0 version, Subscription Management

ACTUAL BEHAVIOR
---------------

PCM_OP_SUBSCRIPTION_SET_VALIDITY_FROM_STRING wrongly set the effective_t of the product.
Pipeline generates the "fun" file with data. Used UEL to load the "fun" file, which calls PCM_OP_SUBSCRIPTION_SET_VALIDITY_FROM_STRING.
This internally calls "op_subscription_set_validity" opcode.
If the call time is 11:00 AM on Dec 5th with offset of -0600. It should set the product's valid from 00:00 of Dec 5th and valid to 00:00 of Jan 5th for 31 days of validity. Effective_t should be 11:00 AM of Dec 5th.
Opcode sets valid_from & valid_to correctly, but wrongly add 6 hrs (from UTC offset) to effective_t. This is wrong.


EXPECTED BEHAVIOR
-----------------------
Effective_t should be 11:00 AM of Dec 5th.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use UEL to load data usage file generated from pipeline

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.