My Oracle Support Banner

"Pay ID (ID#) has wrong status (50) for freezing" PUPL Error While Applying Creating Payment In Suspense Account (Doc ID 2615281.1)

Last updated on NOVEMBER 27, 2019

Applies to:

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

Symptoms

On : 2.6.0.1.0 version, BT - Batch

PUPL error while applying creating payment in suspense account

When the Account ID is coming incorrectly then we are getting error. This error doesn't come every time but when it starts coming it continues for few days and then this error goes after few days.

ERROR
-----------------------
Pay ID (ID#) has wrong status (50) for freezing.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Make the entries in the below table.

CI_DEP_CTL_ST / CI_TNDR_CTL_ST / CI_PAY_TNDR_ST / CI_PAY_ST

Make sure in CI_PAY_TNDR_ST table the CUST ID column should have Account Id which is not available in the system so that the payment should be moving to Suspense Account as per the functionality available in ORMB base Product itself.
The suspense account is fetched from the Tender Source (CI_TNDR_SRC) from the column SA_ID.

2) Run the ORMB Product base Batch Job PUPL to process the loaded records in Base Staging tables. Now the payment should move to Suspense Account as CUST ID doesn’t exist in the system.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.