Saturday, 9 November 2013

P93091 unicode conversion in JD Edwards

P93091 is pretty much all you need to know.

The top button builds a list of all "Non unicode" data sources in the system.  This list is based on the "System" datasource in your ini file, therefore if you run it from the deployment server, it'll use the planner F98611.  This might not be what you want.  This run R930811, I run it locally.  It actually won't run in DEP / planner - so I recommend using a normal fat client.

The second button allows you to work with the results of the first.  Despite the confusing interface, you need to double click a row (till the green tick appears) and then tick the "build information" tick box too.  Once this is done and you select OK the job starts processing. R930912 runs and will hopefully build your list of tables to convert.  The list is called UniDataConv.xml in your install dir in a dir called script.  Note that this report works off sys tables / all_objects and not OL to list the tables, as you'll see tables mentioned that are not in OL.

If there are ANY errors in the data source that you specify, none of the tables will be written to the uniDataConv file, so you need to make sure that it's pretty clean.

Wow, it's hard to cut and paste the XML and see the actual characters...

I'll upload the file somewhere  https://drive.google.com/file/d/0B30UFGvbR-EjNEt3d001MXRmZWM/edit?usp=sharing













F964001


F96401


F96402


F9640S


F96411


F96450


F9649


F96491


F96492


F9660


F980011


F980014


F980021


F9801NEW


F9801OLD


F98231D


F98231H


F98301


F983061


F98610


F9880


F9890


F98TC002


F98TC01


F98TC03


F98TCDTL


F98TCHDR


F99102D


F99RDDS


FF31112T


FF31113T


FF3112ST


FF3113ST








Business Data - TEST








You then need to run UnicodeDataConv.exe  from your bin32 dir on the fatty that has the file in the script dir.

No comments:

Extending JDE to generative AI