Data Dictionary


Active Member
Hi all,

I'm gearing up for my first JD Edwards application (long time MS Visual Studio developer, new to JDE) and need some guidance. I'm finishing up the analysis and I will need a custom table to store data related to a receivable. In a nut shell, this will be ancillary data related to past due receivables. The application will be implemented in Xe (Xe Go Live slated for July 2001, no deadline yet on this app)

I have a couple of questions related to creating a custom table:

1) Is it better to create new data dictionary items, marked at system code 55-59, rather than use existing ones for the table layout?
2) I will need to have some free form text associated with the table. I understand that this can be handled through a media object, but I'd rather have something like a memo field associated with the record. As I understand, reporting on media objects can have some problems. Any comments?


William Kunneke - City of Orlando

Live: B733.1 SP7.1
Oracle 805 AS400/DB2
Sandbox: XE SP15
Migrating Central Objects to AS400/DB2


Legendary Poster

here's my 2 cents on your questions:

1) Use existing DD items where Form/Fit/Function are the same (AN8 for customer number, etc). Use net new (55xxxx) where you cannot easily find a match within the existing DD codes.

2) There is no 'memo' or long text field in OW (I wonder if this is because of an AS/400 limitation?). To do what you want will require a child 'text' table with 'X' characters per row (nor more than 256). Implement as a bunch of rows on a grid. Really ugly way to go.
Reconsider using attached text media objects since including them in a report isn't that hard to do in a UBE.


Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP13

Christian Audet

Staff member

Using custom DD is realy a good idea for custom apps. The only time I will use existing DD is for EXACTLY the same field and EXACTLY the same usage.

Even with the best analysis you know that your need will eventualy change, like default value, new visual assist, validation change. So in that case you don't want to use existing DD because it`s not a good practice to modify a JDE DD since we can't be sure of the impact.

Christian Audet

Implementing B7333 (Xe) SP14.1, SQL
(Support B732, B7331 and B7332)


Legendary Poster

Here are my 2 cents that are only a bit addition to Larry's and Christian's really great answers.

Our best pactice for DD hunting is to create a joined Business View over F9200 and F9210 data dictionary tables and create an APPL with a Find/Browes form based on this BSVW.
You can include a Fetch for Alpha, Row and Column descriptions on F9202 and F9203 tables into the Grid Record Is Fetched or into the Write Grid Line-Before event. You can also put a Language Code filter field for the previously mentioned fetches onto the grey header of the form. Of course, you can join these tables to the BSVW too but you have to filter out Language/Form/SystemCode overrides preventing the duplications for the same DD Item.

Believe me, it takes not more than half an hour.
You can use this application to locate the best fitting DD items for your needs filtering on:
* Alias
* Data Item Name
* Row/Column/Alpha description (if you joined F9202,F9203 to the view too)
* Data Type
* Item Size
* File and Display decimals
* Item Class
* System Code
* etc.

At last, using original OW Data Items, I am not too worry about that JDE will change their attributes that can make conflict in existing appliacations. It is just my oppinion.

Good DD Hunting,

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)


Active Member
Thanks to all who responded. I've participated in developer forums in the past and look forward to participating in this one, hopefully contributing as I become more familiar with the product!

Live: B733.1 SP7.1
Oracle 805 AS400/DB2
Sandbox: XE SP15
Migrating Central Objects to AS400/DB2