Oracle's JD Edwards EnterpriseOne is an integrated applications suite of comprehensive enterprise resource planning software that combines business value, standards-based technology, and deep industry experience into a business solution with a low total cost of ownership.
Essentially, an ERP and set of buzzword-bingo cards in the same box.
an integrated applications suite = bunch of software interfaces for...
of comprehensive enterprise resource planning software = your business purchasing and maintenance problems
that combines business value = giving you the most bang for your buck,
standards-based technology = not sure about this one... can be tweaked by your IT department OR helps you select products/services that meet regulatory standards so that you won't get sued for cutting corners
deep industry experience = nobody got fired for picking something everyone uses
into a business solution = we will unpack and assemble it for you, but you should really buy the Gold Support Package or budget a lot more for your IT department, because it isn't compatible with anything else
with a low total cost of ownership = we make most of our money on the Gold Support Package, but will let you fool yourself into thinking that you won't need it.
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.
Roughly 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.
Hundreds, 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.
