E1: MIG: Considerations for Setting up CCSID on Migrating to EnterpriseOne and Issue with CCSID for the # Character
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.
Checked for relevance on April 24, 2013
This client is migrating from World software A7.3 CUM11 to EnterpriseOne 9.0 application release level, the OS/400 is V5R4 and in this moment they have the CCSID '37' for the user JDE .
They have in data base the # character , they want to have the Ã character for Spanish language instead.
They believe the problem is in the CCSID for iSeries.
Their question is about the problems if they change the CCSID to '65535'. They normally have this character # in 37 is the Ã in 65535. Which exactly CCSID to use after upgrade to EnterpriseOne.
They had run the CCSID conversion <Note 643641.1>, and they have two languages , English and Spanish language.
They have changed the ONEWORLD and JDE profiles CCSID from 37 to 65535, to check that the issue could be solved.
When the profiles has the CCSID 65535, they log on in the AS/400, but the menu doesn't appear to select the JDE900 instance (first menu, they have two entries because they have Multi foundation). After this, they add the library (the menu add this library automatically) to start the services. The services started correctly. They check the character in the programs, but the character is still '#' and not 'Ã' (it same as CCSID 37).
They don't know how to solve the issue , they thought that the change the CCSID for the profiles, this issue would be solved. They have checked that the WS file in the AS/400 has this character ('#') .
They have also tried to change the CCSID for the users from 37 to 13488 , but the system doesn't permit this change (they can't change to put this value). They checked the different CCSID for users, default value,files , etc. The ONEWORLD, JDE, default value are with 37 CCSID.
The files for E1 (for example F0116) have the 13488 CCSID. The F0116 file has different values for the fields (DSPFFD), and for the fields that they have problems normally have 65535.
They will do the migration for A7.3 to EnterpriseOne for production shortly, and the customer will start to work with E1 9.0. They have checked the documentation for the migration. They will use the QSECOFR user with CCSID 65535 in the CCSID Conversion tool step, this way they believe they will have the correct data, but they don't know if this is correct and possible.
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