My Oracle Support Banner

OBPM-Field 72 Validation During Cancellation Of Contract-NonSTP (Doc ID 2862353.1)

Last updated on APRIL 13, 2022

Applies to:

Oracle Banking Payments - Version 14.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

User is deleting the cancellation and modify the contract to update field 72 value and
then perform cancellation.

However,we have a problem with the solution of modifying the contract to correct the field 72 from non stp queue as system is releasing the message from NON Stp queue after modify option.

Suggested Steps:
1)Message in Non STP queue with invalid 72 field
2) User tries to correct the field 72 as cancel option fails if not done
3) After modification from PQSNSTPQ, txn got released from Non stp and accounting got posted.

Expected :
1) User should have option directly to cancel the contract from NONSTP queue
as user does not want a contract to be created in system for the message.

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


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