Transaction Amount is not Getting Aggregated if a Different Feed File has the Same Product and TXN_DTTM Date Account (Doc ID 1966139.1)

Last updated on JULY 24, 2017

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.3 and later
Information in this document applies to any platform.

Symptoms

On :  2.3.0.1.0 version, OTH - Other Bugs

When a different feed file (with a different header) has the same product, transaction date time and account the transaction amount is not getting aggregated.

If the feed file has a different header with a different TXN_DTTM date for the same the account and product than the transaction amount is aggregated.


EXPECTED BEHAVIOR
-----------------------
The transaction amount should get aggregated despite the header id of the feed file being different.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Use a feed file for a transaction that has an account with TXN_DTTM date as -19-Dec-14 and for a product, for example ABC of volume 1.
2. Run the batch jpb from C1-TXNIP (Initial Product Determination) , C1-TXNVP (Price assignment and summarization). C1-TXNEX (Mark error), C1-TXNSQ (Service Quantity Calculation and C1-TXNCM (Mark complete) batch. A Billable charge is created for Volume 1.

Next


3.Obtain a transaction feed file for the same account with the same TXN_DTTM date (i.e 19-Dec-14) and for the same product (i.e ABC of volume 1).
4.Run the TFM batch again starting from C1-TXNIP , C1-TXNVP. C1-TXNEX, C1-TXNSQ and C1-TXNCM batch.
5. Once the batch is executed check if the billable charge amount should get aggregated to (1+1=2).


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