看来，我们大多数SAP程序员都在使用旧版本的ABAP，这是面向对象之前的版本。我还注意到，使用OO，该语言更加简洁和现代（他们显然是借此机会摆脱了过时的事物）。
It appears that most of our SAP programmers are using the old version of ABAP, the one before object-oriented stuff. I also noticed that the language is much cleaner and more modern with OO (they apparently took the opportunity to get rid of deprecated things).
由于该系统尚未推出，因此现在进行重新设计的时间应该比现在晚。
As the system is not rolled out yet, the time to make any redesign is now rather than later.
是否值得将新代码编写为OO ABAP程序？如何卖给管理层？与非OO程序的接口是否工作正常？
It is worth requesting that new code be written as OO ABAP programs? How to sell that to management? Does the interface with non-OO programs work well?
（已更新，以至于我特别在谈论新代码，尤其是计划在明年进行的开发）
(updated to note that I'm talking specifically about the new code, especially planned for the next year)
推荐答案如果在生产环境中可用，请不要重写代码。不值得花费时间或金钱，也没有任何管理层（在一家足以运行SAP的公司中）会同意这一点。
If it's working in production, don't rewrite your code. Not worth the time or money, and no management (at a company big enough to be running SAP) would agree to it.
除非您迁移到绿地环境，您将永远无法将所有内容都用OO重写。 SAP甚至还没有使用其核心ECC模块来做到这一点。期望能够使用您的自定义内容做到这一点是不现实的。
Unless you move to a green field environment, you're never going to get everything re-written in OO. SAP hasn't even done that with their core ECC modules. Expecting to be able to do it with your custom stuff is unrealistic.
我只会阅读OO ABAP并开始使用它编写新程序。
I would just read up on OO ABAP and start writing new programs with it.
OO ABAP和程序性ABAP可以很好地协同工作。您可以调用课程&程序程序中的方法，（反过来则更多）。
OO ABAP and procedural ABAP work together just fine. You can call classes & methods from procedural programs and (more limited, but) vice versa.
更多推荐
过渡到OO ABAP？
发布评论