My Oracle Support Banner

OBPM Outbound Cross Border Restriction Based On Network Code Is Not Considered While Creating Transaction (Doc ID 3009694.1)

Last updated on MARCH 19, 2024

Applies to:

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

Symptoms


ACTUAL BEHAVIOR
---------------
OBPM - 14.6.0.4.0 - OUTBOUND CROSSBORDER - RESTRICTION

In payments account entitlement maintenance, user has restricted outbound transactions based on network code and restricted particular customer with the account entitlement.

But for that customer, users are able to outbound cross border successfully.


EXPECTED BEHAVIOR
-----------------------
System should validate the restrictions maintained.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Maintain the account entitlement group restrictions for the account in STDCRACC.
2. Perform Account Entitlement Restriction for Outbound txn in PMDPAYRS.
3. Post a transaction with restricted account and verify if the transaction is posted successfully


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are able to post txn for an restricted acc and restricted network code

Changes

 

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
Changes
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.