Charge Claim Target 2 Incoming Charge Our PX-PROC-084
(Doc ID 2783468.1)
Last updated on JUNE 10, 2021
Applies to:Oracle Banking Payments - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Implementation Support
Charge Claim Target 2 Incoming charge our
In the moment that a target 2 swift message is coming MT 103 ompb is requiring mandatory maintenance for charge claim.
Even if customer has a RMA Agreement or not this maintenance should be present in OBMP because otherwise contract will fail during process.
Bank is requiring to generate MT 991 not 191 as in this case is generated and charges to be applied as well during contract input.
Final result on accounting entries should be debit Nostro Account for charge amount and the income to be credit.
The issue can be reproduced at will with the following steps:
1. Close RMA for sender of the payment, if present.
2. Upload inbound/pass through transaction with 71A as OUR. 191/291 will not
3. Go to PXDCMN91, and generate 991.
4. Upload 202 for payment of 991.
5. Check if accounting and mapping of these messages are done.
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