My Oracle Support Banner

Manual And Pain001 SCT Payments Fail When CREDITOR BIC Is INDIRECT PARTICIPANT In The Network (Doc ID 2793741.1)

Last updated on JULY 23, 2021

Applies to:

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


On : version, Implementation Support

Manual and pain001 SCT payments fail when CREDITOR BIC is INDIRECT PARTICIPANT in the network.

While inputting SCT payments( manually or through pain.001) with a CREDITOR BIC which is indirect participant in the network,

Case 1. For manual payments the transaction fails to be saved during the Enrich process with the error code : Network participation of the given BIC doesn't not match with network preference(Error Code is :PA-TXP-171).

The BIC Code that was used for the test was identified as INDIRECT PARTICIPANT in the network. the routing BIC of PYMXMTMTXXX which is the BIC LIABLT2XXXX and is a direct participant in the Network.

Case 2. For the transaction processed with the pain.001 file the payments are moved to Repair Queue with the error of : CounterParty Bank Code not found.


The issue can be reproduced at will with the following steps:
1. In the Network Maintenance Screen Network Network Participation is maintained as DIRECT.
2. In SEPA Routing Directory screen PMDSEPAD, Creditor BIC Code is maintained as Indirect Participant.
3. The routing BIC LIABLT2XXXX is maintained as DIRECT Participant in the network

The issue has the following business impact:
Due to this issue, users cannot see payments processed successfully.




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

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