PUPL Job Not Processing Records In Suspense Account
Last updated on JULY 24, 2017
Applies to:Oracle Financial Services Revenue Management and Billing - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Payments to Suspense accounts are moving to error in staging level itself during PUPL processing in upgraded environment. Existing production PUPL (ORMB 188.8.131.52) loads these suspense payments from staging CI_PAY_TNDR_ST to ORMB base table CI_PAY_TNDR but upgraded PUPL is not doing it (i.e.) it marks the payments to error and keeps it in the staging table CI_PAY_TNDR_ST with no record entries in CI_PAY_TNDR. Upgraded Cobol program throws below warning and issues Rollback.
02:45:13,553 [CobolThread 55] WARN (com.splwg.base.support.cobol.DBLocalCobolSQLProcessBackend) more than one row returned from select statement with SQL:
'SELECT SA.SA_ID FROM CI_TNDR_SRCE TS, CI_SA SA WHERE TS.SA_ID = SA.SA_ID AND SA.ACCT_ID = ? /* SQL for COBOL program 'CIPPMBIX', SQL name 'S_SUSACCT' */' with bind parameters:
Parameter 1 (Char)'0000115984'
1. Job updates the account number in payment tender staging (CI_PAY_TNDR_ST) as 9999999999 if that particular account in not available in ORMB system during data loading step.
2. In ORMB table CI_TNDR_SRCE, there are multiple tender source mapped to same Suspense Account Contract ID (SA_ID).
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