Newsfeed Is Not Created With Allocation Reason_Id For Item Transfer When Use Custom Opcode (Doc ID 2269773.1)

Last updated on JUNE 13, 2017

Applies to:

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

Symptoms

On :  7.5.0.17.0 version, Customer Care

Newsfeed is not created with allocation reason_ID for item transfer when custom opcode is used.

Scenario:

In a customized MTA application, which run daily to check the credit items on accounts and transfer the amounts to debit items by invoking a custom opcode, which in turn calls PCM_OP_BILL_ITEM_TRANSFER opcode.

When Billing Care or Customer Center is used, the newsfeed is created with reason_id 134 (Allocation). These payments are showing as closed in the audit trial of Billing Care.
However, the payments which got transferred to bill items using the customized MTA/opcode are not having newsfeed with correct reason_id. The reason_id is assigned as 100 (Payment) instead of 134 (Allocation). Due to this, billing care is showing these payments as still OPEN in the audit trial.

Steps to replicate:

The issue can be reproduced at will with the following steps:
1. Invoke the PCM_OP_BILL_ITEM_TRANSFER from the custom opcode with the same input flist as item transfer.


Changes

 

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