My Oracle Support Banner

R12: In XML Extract, The Unique Remittance Identifier (URI) (UniqueRemittanceIdentifier) Does Not Appear Directly Under The OutboundPayment Group (Doc ID 1554937.1)

Last updated on APRIL 19, 2019

Applies to:

Oracle Payments - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.


After applying Patch 14208483 (PAYMENTS RECOMMENDED PATCH COLLECTION (IBY), AUGUST 2012) and other patches, the unique_remittance_identifier is not getting populated in the IBY_PAYMENTS_ALL table.
As a result, the Payment Instruction element 'UniqueRemittanceIdentifier' does not have a value under the OutboundPayment group.

Expected behaviour
That value/s for the Payment Instruction XML element 'UniqueRemittanceIdentifier' under the OutboundPayment group should be populated

Steps to reproduce
1 - Create invoice/s, ensuring for each invoice (a) Pay Alone flag is disabled, and (b) the URI is populated
2 - Validate invoices
3 - Create a payment batch (PPR), ensuring the Payment Process Profile (PPP) is grouping payments by URI.
4 - Process to completion
5 - Open the Payments Funds Disbursement Extract structure and note the missing data vis a vis Payment Instruction element 'UniqueRemittanceIdentifier' does not have a value under the OutboundPayment group.

Business impact
The customer is using a custom Payment Instruction Format (PIF) that references the Payment Instruction element 'UniqueRemittanceIdentifier' under the OutboundPayment group.
It is unclear if the absence of this element is intended or not.  If not, then the customer would have to edit their custom PIF.


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.