Error In Purchasing Deal With Start/End Time Offset (Doc ID 790343.1)

Last updated on JULY 28, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.1]
Information in this document applies to any platform.
Information in this document applies to any platform.
**Checked for relevance on 13-Nov-2012***
**Checked for relevance on 30-Dec-2014***

Goal

The usage of 0,1,1 for purchase, cycle and usage start_t's respectively in the I/P flist of purchase deal opcode with end_t as future dated/backdated value just before the end of accounting cycle like 23:59:59 works fine for the normal purchase of the deal. However, when they use the offset for these fields this results in the error.

E Sun Apr 5 01:00:00 2009 xxxxxxxx cm:9232498 fm_subscription_purchase_product.c:2312 1:xxxxxxxx:testnap:1593472:1:108:1232012616:1
fm_subs_purchase_verify error
<location=PIN_ERRLOC_FM:5 class="PIN_ERRCLASS_APPLICATION":4 errno=PIN_ERR_BAD_VALUE:46>
<field num=PIN_FLD_CYCLE_START_T:8,266 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>
E Sun Apr 5 01:00:00 2009 xxxxxxxx cm:9232498 fm_subscription_purchase_product.c:630 1:xxxxxxxx:testnap:1593472:1:108:1232012616:1
op_subscription_purchase_product error
<location=PIN_ERRLOC_FM:5 class="PIN_ERRCLASS_APPLICATION":4 errno=PIN_ERR_BAD_VALUE:46>
<field num=PIN_FLD_CYCLE_START_T:8,266 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>

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