过渡到 OO ABAP?

本文介绍了过渡到 OO ABAP?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

似乎我们的大多数 SAP 程序员都在使用旧版本的 ABAP，即面向对象之前的那个版本.我还注意到，面向对象的语言更简洁、更现代(他们显然借此机会摆脱了不推荐使用的东西).

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.