My Oracle Support Banner

Noex: XXNOET06 Telepay Stopfile Shows Data in Wrong Positions When Using UTF8 (Doc ID 740857.1)

Last updated on APRIL 07, 2020

Applies to:

Oracle Financials for EMEA - Version to [Release 11.5]
Information in this document applies to any platform.
This problem can occur on any platform.
NOEX - Norwegian Extensions
XXNOET06.sql - Stop Payment File XXNO


Find creating a stop payment file in the UTF8 instance makes the transaction code appear in wrong
positions and file not accepted by bank

The Application Header record shows 101 characters instead of 40 as expected

This works as expected in a non UTF8 environment

Expect the stop payment file to show values in correct position and be accepted by bank

The issue can be reproduced at will with the following steps:
1. Create and sent payment file to the bank.
2. Import receipt file sent by the bank
3. Confirmed the payment batch
4. Query the payment batch, click <Payments>
5. Then click <Actions 1>, Initiate/Release stop
6. the Stop File is generated .


changed character set to UTF8


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.