Bill-Level Adjustments Do Not Pass Reason Code Information To Adjustment Validation Policy (Doc ID 565453.1)

Last updated on JULY 27, 2017

Applies to:

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

Symptoms

On Oracle Communications Billing and Revenue Management(BRM), 7.3.0.0.0 version, the bill level adjustments do not pass reason code information to adjustment validation policy.

Steps To Reproduce:

1.Created a custom reason code for bill adjustment in reasons.en_US.($PINHOME/opt/portal/7.3/sys/msgs/reasoncodes/reasons.en_US).
2. Run load_localized_strings -v reasons.en_US to load the above changes.
3. Restarted services.
4. Passed a bill adjustment (credit value) for an account.
5. Verify the contents of input flist to fm_bill_pol_valid_adjustment in the cm.pinlog.

You will see that PIN_FLD_STR_VERSION and PIN_FLD_STRING_ID fields (they identify the reason code) that were in op_ar_bill_adjustment input flist are not passed on to op_bill_pol_valid_adjustment input flist.

The PIN_FLD_STR_VERSION and PIN_FLD_STRING_ID fields that were in op_ar_bill_adjustment input flist actually do not appear in the op_bill_pol_valid_adjustment input flist.

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