UK Oracle User Group


Understanding JD Edwards EnterpriseOne Object Naming

5 June 2015

Whether a seasoned veteran or a newbie, learning a new ERP system can be an uphill battle, regardless of the position one holds, which makes it nice when a software vendor can do something to help increase the upskilling of individuals learning the product...

One way JD Edwards completes this task is with its naming convention.  Really?  JD Edwards naming convention?  Are you serious!?  How can a codename actually help a user to better understand E1 vs a longer, more descriptive, name which may be more intuitive!?  Whoa there, I hear what you are saying, but there really has been a plan all along with this method, which has served JD Edwards well for many years and actually leads to a lower total cost of ownership.

No doubt you have heard words of wisdom all of your life, for instance:

"Time is really the only capital that any human being has, and the only thing he can’t afford to lose." —Thomas Edison

Our naming convention actually helps to fulfill your need to save time.  The real Business Reason behind a standard naming convention is that it promotes:

  • Understanding
  • Taking ownership
  • Governance
  • Reporting
  • Integration

Consider this fact about the potential complexity with tables.

In 2007 there was a posting stating SAP has over 125,000 standard tables, http://scn.sap.com/thread/328958.


The handy reference on this third party site, http://www.jdetables.com/, lists EnterpriseOne 9.1 as having a total of 5112 tables. Although, I am not certain this is the exact amount, even if it were 10,000 tables, the less complicated JDE data model would be significantly easier to understand than SAP’s 125,000+.  This is low TCO (total cost of ownership) by design!!!

Ok, so there are fewer tables, which means less JD Edwards EnterpriseOne 9.1 Business Process Models (Doc ID 1642289.1), but what does this have to do with the naming conventions?

In JD Edwards, the naming convention for objects tells you the:

  • Object type
  • System code
  • Group type

For example,

  • F = File
  • Position 1-2: Is the System (09 General Accounting / 41 Inventory / 12 Fixed Asset / 09E Expenses, etc.)
  • Position 3-4: 01 (Master Table) 11 (Detail Table) 02 (Balance / Summary)

What is F0911?

  • File + General Accounting + Detail Table

And F0902?

  • File + General Accounting + Balances Table

Of course, these are simple examples but with this "basic" tip you can navigate most key important data models in JDE.  And the best part is this naming conversion doesn’t end with the tables.  Naming conventions are used for all object types.  See the following diagram taken from the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide under Chapter 3 Understanding JD Edwards EnterpriseOne Naming Conventions

 

NamingConventionforObjects.png


Using this foundation, you can begin to learn the ins and outs of the product quicker, and if you are developing new content, simply use the same convention with system code 55-59 to identify custom objects and the transition is an easy one!  For more details on the naming convention for all of the object types, including new ones not shown in the graphic, see the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide under Chapter 3 Understanding JD Edwards EnterpriseOne Naming Conventions.


Source: JD Edwards EnterpriseOne Support Blog


We'd love to get your feedback on this; you'll need a UKOUG login to provide it, so if you don't have one, please click on 'create a web profile' first.

Top