R12: AP/IBY: Supplier Bank Account Name Field Length Violates ISO 20022 CGI PAIN.001.001.03 Format Xsd
(Doc ID 2050438.1)
Last updated on SEPTEMBER 09, 2016
Applies to:Oracle Payments - Version 12.0.0 and later
Oracle Payables - Version 12.0.0 and later
Information in this document applies to any platform.
In Oracle eBusiness Suite (EBS), when using the PAIN.001.001.03 messaging format, it's discovered the bank payments are failing for supplier bank accounts that are longer than 70 characters.
In the Oracle table IBY_EXT_BANK_ACCOUNTS, the BANK_ACCOUNT_NAME columns' data type is VARCHAR2(80).
However, the </CdtrAcct> field in the ISO 20022 PAIN Format XSD is defined as below:
This maps to the XML elements as below:
<xs:element name="Id" type="AccountIdentification4Choice"/>
<xs:element maxOccurs="1" minOccurs="0" name="Tp" type="CashAccountType2"/>
<xs:element maxOccurs="1" minOccurs="0" name="Ccy" type="ActiveOrHistoricCurrencyCode"/>
<xs:element maxOccurs="1" minOccurs="0" name="Nm" type="Max70Text"/>
That is, the field only permits a maximum of 70 characters.
This means if a supplier bank account name exceeds 70 characters, the Customer Payment Status Report message will show the following:
Concerns regarding the count of potential data violations in the Oracle-seeded formats supposedly compliant with the PAIN.001.001.03 messaging format.
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