R12: AP/IBY: Two Fields in Record Type 1 of the Zengin Payment Files Do Not Contain the Expected Values When Testing in Preparation for an 11i to R12 Upgrade
Last updated on MARCH 04, 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.
An Oracle Payables customer who was preparing to upgrade from 11i to R12 discovered unexpected values displayed in two fields of Record 1 in the Zengin output file.
The seeded layout template file IBYDE_Z_JP_en.rtf defines several fields in Record Type 1 to be formatted as follows:
<POSITION> <LENGTH> <FORMAT> <PAD> <DATA> <COMMENTS>
4 1 Number L, 0 1 The code type, 1 for EBCDIC/S-JIS
15 40 Alpha R, ‘ ‘ InstructionGrouping/ BankAccount /AlternateBankAccountName Account holder’s name for internal bank account
While the evaluating the results produced by the seeded layout template file named IBYDE_Z_JP_en_.rtf, the customer noticed:
--the value in the Code Type field in position 4 of Record Type 1 was coming as '1' instead of the expected value of '0'
--the Account Holder’s Name field starting in position 15 in Record 1 was empty
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms