BACK DATED ORDERS FAILS WHEN ACCOUNT STATUS IS UPDATED
Last updated on OCTOBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Customer Registration
In an environment having a RODOD implementation, an account is created with no service (lets say June 29), and it is sent for provisioning. If the network takes may be 3 days to provision the account, and the OSM executes the PCM_OP_CUST_MODIFY_CUSTOMER with the end_t as the account created date. In between if a person from Siebel tries to update the customer account with Update_customer opcode, then there is a cust_set_status opcode called. immediately by the AIA. This will not change the status of the account but will update with the same status.
Later when the PCM_OP_CUST_MODIFY_CUSTOMER opcode is called, the error is thrown.
Backdating is not allowed before the date of the last status change.
<location=PIN_ERRLOC_FM:5 class=PIN_ERRCLASS_APPLICATION:4 errno=PIN_ERR_BAD_VALUE:46>
<facility=0 msg_id=90 version=1>
1) On June 29 2016, account is created in BRM.
2) On July 03 2016, account status is modified (ACTIVE to ACTIVE).
3) On July 03 2016, PCM_OP_CUST_MODIFY_CUSTOMER is executed with end_t as Jun 29 09:58:54 2016.
4) Error occurred for the same with below error.
Random accounts are impacted in the production.
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