5 ms·
JDE has a consistent, logical, and totally infuriating table and column naming convention that's a holdover from its System/34 days, so that you're always havin
by HillRat 13y ago
JDE has a consistent, logical, and totally infuriating table and column naming convention that's a holdover from its System/34 days, so that you're always having to select GLAA from F0911 and so on.
Worse yet, the system doesn't store human-readable descriptions in a consistent manner, so you have to do half a dozen joins just to get to the object names. So JDERef would have provided a valuable service to anyone who needs to talk to a JDE database -- without a handy schema reference, it's just a pile of characters.
- arethuza 13y agoOut of interest, how many tables does JDE have in its database?
- endersshadow 13y agoHundreds, depending on the packages used by the customer. The good news is that the names never changed, so you could write a third-party add-on to it and it would always work. I know of a company that wrote a plug-and-play data warehouse for only JDE customers.
- HillRat 13y agoRoughly 5,000, as I recall (JDE was only tangentially related to my world). I think about 1,500 of those map to specific system objects. There's also various naming conventions for other objects; user-defined value lists have terse names like "UDC 98/SY" (which is, I think, the value list of value lists, or some such), batch routines have names like "R09430," and so on. It's all horribly brain-deadening, and the cognitive barrier to entry is extremely high. Evidently ORCL likes it that way.