My Oracle Support Banner

R12: AP/IBY: SEPA: "Cdtr" and "Ultmtcdtr" Identification Are Not Populated Correctly In SEPA Credit Transfers (Doc ID 1306933.1)

Last updated on AUGUST 19, 2021

Applies to:

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


Creditor "Cdtr" and ultimate Creditor "UltmtCdtr" Identification is not populated correctly when processing SEPA payment for Internal Supplier's expense reports (i.e.Employees)

A- The Identification of supplier will be provided in the following order as :

1-Tax Registration Number – In the supplier UI this is the Default Reporting Registration Number [Column Name - In AP_SUPPLIERS it is stored in the column VAT_REGISTRATION_NUM]

2-Legal Entity Registration Number – In the supplier UI this is the Tax Payer Id [Column Name – In AP AP_SUPPLIERS this is stored in column ‘Num_1099’]

3-Supplier number – Supplier number is there in supplier UI. (Column Name - In AP_SUPPLIERS its stored in the column ‘SEGMENT1’)

4-Party Number – In the Supplier UI this is the Registry Id (It is stored in column ‘PARTY_NUMBER’ in HZ_Parties)

5-First Party Reference – There is no UI field. (This is stored in column ‘Party_Id’ in HZ_Parties)

B- Ultimate Creditor is mapped to the Remit to Supplier.
If Remit to Supplier information is not available, then it is mapped to the Supplier. The mapping is the same as for the creditor.

The issue can be reproduced at will with the following steps:
Processing SEPA payment for Employees

The issue has the following business impact:
Due to this issue, Creditor Identification missing in SEPA credit Transfer




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.