JD Edwards 的开发学习曲线是怎样的？
平均而言，熟练使用 JD Edwards 进行开发需要多长时间？ 容易学吗？ 有什么先决条件吗？
On an average, how much time does it take to become proficient in development using JD Edwards? Is it easy to learn? Are there any prerequisites?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我假设您有兴趣学习 JD Edwards 的开发技能，而不是系统实际实现的业务流程。
JDE 有 2 个版本。 运行在AS/400平台、DB2数据库上，并使用RPG（语言）来实现报表和功能。 我不熟悉该版本（做了很少的接口工作，而且由于 DB2 与我常用的数据库（Oracle 或 SQL Server）的差异，它们都很复杂）。
另一个版本是EnterpriseOne（以前称为OneWorld）。 我从 2000 年开始开发这个版本，一直活跃到 2006 年。很容易达到基本的开发水平，然后你就可以面对系统中的奇怪现象和已知问题，以及如何避免它们，那时你就变得有经验了。
所有开发工具都是 JDE 内部的。 有一个表设计器、一个查询设计器（具有类似于任何可视化查询设计器的网格界面）、一个交互式程序设计器（表单）、一个报表设计器和一个业务规则设计器。
如果您有任何 RDA 工具（例如 Visual Studio）和数据库开发经验，您将能够利用这些知识来简化学习曲线。 就我而言，我是一名 SQL 程序员，并且在 Visual Basic 和 Microsoft Access 方面拥有丰富的经验。 我能够通过理解系统的基本概念并适应它们来利用这些经验。 我花了大约 25 个小时接受了一位经验丰富的程序员的培训，才让我准备好至少为真实的客户做基本的事情。 显然，这个时间长度因人而异。
然而，我可以说，在为第一个客户进行 6 个月的日常工作后，我才开始感觉到自己正在理解这些工具和流程。 大约 12-18 个月后，我对自己编写的第一个应用程序感到羞愧，所以我实际上用自己的时间回去重写了一些应用程序...:-)
JDE 的问题是：JDE 上的编码/功能非常少数据库方面（因为它过去在数据库选择上很灵活）。 所有的表格和报告都是由设计者在实际系统中编写的。
所有“编码”都是通过简单（有时是愚蠢的）点击界面来完成的。 例如：您不编写赋值语句，例如 var = value。 您选择“分配”按钮，然后在列表中选择变量，然后在列表中选择值（或者输入值，如果它是固定的）。
表单、报告和业务规则背后的所有规则都是以这种方式创建的。 一个例外：当您编写业务规则时，您可以选择使用此方法（称为命名事件规则 - NER）或使用 C 语言（称为业务函数）。
如果你选择NER，完成后，系统实际上将其转换为C。
有表单、报告和业务规则的调试功能。
这是基本的发展。 还有其他工具和功能通常分配给开发人员，因此您将能够做更多的事情。 我在界面、互操作性、工作流程等方面做了很多工作。
另外值得注意的是，JDE 有一个内部工具，用于管理对象、版本控制、签入、签出以及将对象从一个环境传输到另一个环境以完成开发周期。
作为开发人员，您对正在实施的业务流程了解得越多越好。 您可以了解功能的内部（代码、规格）和外部（流程），这有助于您作为开发人员，并有助于您的职业生涯（和薪资）。
现在，我对我的答案唯一的警告是：正如我所提到的，我离开 JD Edwards 开发已经有一段时间了。 据我所知，情况几乎相同，但我不能肯定。
我可以提供的最佳建议：访问 www.jdelist.com 了解具体问题并帮助解决问题。 要有礼貌，尝试询问具体问题而不是一般性问题（我的意思是：如果你问那些人学习 JDE 需要多长时间，他们可能会忽略你，但如果你问诸如“在你看来，什么”之类的问题JDE 开发人员需要掌握的最复杂的任务是什么？”您可能会得到一些很好的答案）。
希望它对您有所帮助，并祝您 JDE 好运。 经过最初的颠簸之后，我非常享受乘坐它的乐趣。
I'm assuming you're interested on learning the development skills of JD Edwards, not the business processes that the system actually implements.
There are 2 versions of JDE. One runs over AS/400 plataforms, DB2 database and uses RPG (language) to implement reports and functionalities. I'm not acquainted with that version (did very few interface jobs and they were all complicated due to DB2's differences from my usual flavours of databases - Oracle or SQL Server).
The other version is EnterpriseOne (formerly OneWorld). I started developing for this version in 2000 and kept active until 2006. It's very easy to achieve the basic level of development and then you get to face the oddities and known issues from the system and how to dodge them and that's when you become experienced.
All development tools are internal to JDE. There's a table designer, a query designer (with a grid interface that resembles any visual query designer), an interactive programs designer (forms), a report designer and a business rules designer.
If you have experience with any RDA tool (like Visual Studio, for instance) and development for databases, you will be able to use this knowledge to ease the learning curve. In my case, I was a SQL programmer and I had a lot of experience with Visual Basic and Microsoft Access. I was able to use that experience by understanding the underlying concepts of the system and adapting for them. It took me about 25 hours of training with a more seasoned programmer to get me ready to at least do basic stuff on real customers. This amount of hours varies from person to person, obviously.
However, I can say that I only started to feel that I was understanding the tools and the process after 6 months of daily work on my first customer. After about 12-18 months, I was ashamed of the first applications that I wrote, so I actually went back and rewrote some on my own time... :-)
The thing about JDE is: there's very little coding/functionality on the database side (because it used to be flexible on databases choices). All the forms and reports are written inside the actual system by way of the designers.
All "coding" is done by way of a simple (and sometimes dumb) point-and-click interface. For instance: you don't write an assignment statement, like var = value. You select the Assignment button, then you select the variable in a list, then you select the value in a list (or enter the value, if it's fixed).
All the rules behind forms, reports and business rules are created that way. One exception: when you're writing a business rule, you can opt between using this approach (called Named Event Rule - NER) or using the C language (called Business Function).
If you choose NER, after you finish, the system actually converts that to C.
There are debug functionalities for forms, reports and business rules.
This is basic development. There are other tools and functionalities that are usually assigned to developers and so you will be able to do a lot more. I've worked a lot with interfaces, interoperability, workflow and more.
Also noteworthy is that JDE has an internal tool for managing objects, version control, checkins, checkouts and transfering objects from one environment to another to complete the development cicle.
As a developer, the more you learn about the business processes being implemented, the better. You get to learn the inside (code, specs) and outside (process) for the functionalities and this helps you as a developer and helps you in your career (and paygrade).
Now, my only caveat regarding my answer: as I've mentioned, it's been a while since I left JD Edwards development. As far as I know, things are pretty much the same, but I can't say for sure.
Best advice I can offer: go to www.jdelist.com for specific questions and help with issues. Be polite, try to ask questions about specific matters instead of general questions (I mean: if you ask those guys how long does it take to learn JDE, they will probably ignore you, but if you ask stuff like "in your opinion, what are the most complex tasks for a JDE developer to master?" you will probably get some pretty good answers).
Hope it helps and wish you good luck with JDE. After the initial bump, I enjoyed my ride on it quite a lot.
您可以从 JD Edwards EntepriseOne 开发人员指南开始，了解对象管理工作台、表、表单和报告的设计工具以及业务功能 API。
https://docs.oracle.com/cd/E53430_01/nav/development。嗯
You can start with the JD Edwards EntepriseOne Developer guide to learn about object management work bench, design tools for table, form and reports and API for Business Functions.
https://docs.oracle.com/cd/E53430_01/nav/development.htm
据我所知，这取决于JDE的版本。 有很多不同的组件和不同的版本（据我所知）。例如，我们的一家姊妹公司正在通过终端运行 JDE 到 AS/400。 这都是基于文本的“绿屏”屏幕，在命令提示符下键入三个字母命令，然后使用光标在屏幕上移动。
我还没有尝试深入学习它，但尝试学习足够的知识来提供基本支持已经花费了我几个月的时间，每周几个小时。 将 JDE 视为 SAP 的婴儿版本，它可以让您了解问题的范围。
As far as I can tell, it depends on the version of JDE. There are a lot of different components, and different versions (from what I can tell.) For example, a sister company of ours is running JDE over terminals to an AS/400. It's all "Green Screen" text-based screens, typing three letter commands at a command prompt, and using the cursor to move around the screen.
I haven't tried to learn it in depth yet, but trying to learn enough to do basic support has taken me several months at a few hours a week. Think of JDE as a baby version of SAP, that gives you an idea of the scope of your question.
我教授了一些有关 JDEdwards EnterpriseOne 开发的课程。
我的一位以前从未编程过的学生接受了大约 320 小时的培训才能够在 JDEdwards 上进行一些开发。 现在他是一名同事和一名优秀的程序员。
他的 320 小时训练是：
正如我所说，在这之后，他已经能够执行任务JDEdwards 开发人员的所有任务。
我对要学习这一点的人的建议是充分了解 SQL 并以前使用任何编译语言进行过编程，这会很有帮助。
I taught some classes about JDEdwards EnterpriseOne Development.
One of my students who never programmed before took about 320 hours of trainning to be able to do some developments on JDEdwards. Nowadays he's a coworker and a good programmer.
His 320 hours of trainning was:
As I've said after all this, he has being able to perform all tasks of a JDEdwards Developer.
And my advice to who is going to study this is to have a good knowledge of SQL and have programmed before in any compiled language, it helps a lot.