Bypass CUSTOMER_LOGIN_NOT_VALID_FOR_TIME And CUSTOMER_NO_VALID_PRODUCT Validation (Doc ID 2121306.1)

Last updated on APRIL 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.

Goal

On : 7.4.0.0.0 version, Pipeline Manager

How to configure the Pipeline Rating to bypass the ERR_CUSTOMER_LOGIN_NOT_VALID_FOR_TIME and ERR_CUSTOMER_NO_VALID_PRODUCT validation?
Regardless of the account being inactivated or not, EDR needs to be rated, recycled, and billed.
 
The user has tested with these registry entries:
DAT_AccountBatch.RejectClosedAccounts False
FCT_Account.DisableRatingProductCheck True
FCT_Account.UseAsRouter False as default.

But, the EDR was still been rejected with empty error message:
31.08.2015 14:22:09 The actual log level is Debug. All messages with this or higher severity will be logged.
31.08.2015 14:22:09 Beginning to process stream 'RAT_XXXXXXX1.GRD2424.D17082015.H155042.brm'.
31.08.2015 14:22:09 The EDR with number '00000001' (starting at byteposition:119) contains the errors :
31.08.2015 14:22:09
31.08.2015 14:22:09 The EDR is rejected.
31.08.2015 14:22:09 End of the processing of stream 'RAT_XXXXXXX1.GRD2424.D17082015.H155042.brm'
 
When a new product with "rate even if cancelled, inactive" configuration is created, BRM rates the event even the account is inactive/cancelled correctly.

But, there seems no way to change the configuration of pre-existing products. After changing the flag in Pricing Center, when comiting it to BRM Database, there is the error:
ORA-00001: unique constraint (PIN.I_PRODUCT__NAME) violated.

In fact, as per database, this product is identified as the following:
1 PIN_FLD_NAME STR [0] "XXXXXX PME XXXXXXXX RP - 022113 - VCM:300.00 v2"
1 PIN_FLD_CODE STR [0] "XXXXXX PME XXXXXXXXXXXXX RP - 020242 -VCM: 139.90 v1(9)".

There are a few more products with different values between PIN_FLD_NAME and PIN_FLD_CODE. No customization in Pricing Center and the SET_PRICE_LIST opcode was invoked manually through it.

Should PIN_FLD_CODE not persist with the previous PIN_FLD_CODE?  Should it not be unique?

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