C1-TXNHV Batch Run Throws Error “Sum Of Transaction Volume In The Header Cannot Be Zero"

(Doc ID 2359543.1)

Last updated on FEBRUARY 15, 2018

Applies to:

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

Symptoms

On RMB v2.3.0.2.0 against FW v4.2.0.2.0, when C1-TXNHV batch is executed, it throws error “Sum of transaction volume in the header cannot be zero".

C1-TXNHV errors out and BO_STATUS_CD becomes ‘INVL’ throwing error “Sum of transaction volume in the header cannot be zero. Please enter valid data in the header.”
Whereas total # of records, sum of TXN_AMT and sum of TXN_VOL at header level reflecting exact number as that of CI_TXN_DETAIL and these are not 'zero'.

Note that while running the batch since the ‘Checksum Validation Required’ parameter is not provided at first place, batch should not have validated the above columns and made the status as ‘INVL’

ERROR
-----------------------
16:21:19,328 [TP_BILLING_LARGEWorker:1] INFO (com.splwg.ccb.domain.banking.transactionFeed.transactionFeedAgg.TransactionHeaderValidationBatch)  In executeWorkUnit method of TransactionHeaderValidationBatch
16:21:19,353  [TP_BILLING_LARGEWorker:1] ERROR (com.splwg.base.api.batch.ThreadWorkUnitExecutable) Error #1 encountered at work unit TransactionHeader_Id(94639865671859) - this error will be logged and the unit skipped during the database transaction replay com.splwg.shared.common.ApplicationError: (Server Message)
Category: 17000
Number: 1423
Call Sequence:
Program Name: TransactionHeaderValidationBatch$Worker
Text: Sum of transaction volume in the header cannot be zero. Please enter valid data in the header.
Description:  
Table: null
Field: null

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload the transactions and transaction header in CI_TXN_HEADER and CI_TXN_DETAIL_STG in such a way that sum(txn_amt) for all transactions is more than 0.
2. Run C1-TXNHV.
3. Received error message and the affected transaction had bo_status_cd changed to INVL

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
It is in a Live Production environment. Nearly 1M transactions went into INVL status with a dollar value of $125M. 

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