In Multischeam System pin_rerate Using The Incorrect Search Template (Doc ID 1305398.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

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

Symptoms

The pin_rerate application calls an incorrect search template. The environment is configured as multischema, not multidb, and an account was created on secondary schema.

pin_rerate makes the following search:
"select X from /event where ( F1 >= V1 ) and ( F2 >= V2 and F3 <= V3 ) and ( F4 = V4 ) and ( event_t.account_obj_id0 > 48657 ) order by event_t.account_obj_id0 asc"

The clause "event_t.account_obj_id0 > 48657" is not correct.

This may impact for example the following operational situation. Suppose for example that another BRM user doesn't know (or doesn't verify), that a rerate job already exists for an account and calls pin_rerate with:
pin_rerate -a ACCOUNT_OBJ_ID0 -t DATE

1) In the BRM documentation there is nothing about verifying rerate jobs, before running pin_rerate utility with parameters "-a ACCOUNT_OBJ_ID0 -t DATE".  In this example, invalid template occurs in pin_rerate log. So, the pin_rerate utility at the beginning should check if any rerate job already exists for the same account.

2) Suppose that another BRM user will need to analyze a different re-rating issue on his environment. While analyzing logs and verifying each input and output flist he will surely find an SR when he find this searching template.

This issue concerns invalid search template (not correct or incorrect re-rating status). Also, the search template does not meet searching requirements, according to BRM documentation:

BRM Documentation - Programmer’s Guide - Customizing BRM server components
-> Searching for objects in BRM databases
[...]
"You specify the arguments for the search query in the PIN_FLD_ARGS array. "


How to reproduce:
1. Create an account on secondary schema
2. Rate EDRs for the account
3. Call pin_rerate application, with following parameters

 pin_rerate -a ACCOUNT_OBJ_ID0 -t DATE

Cause

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