SAP R/3标准代码修改的手段? [英] Means of SAP R/3 standard code modification?

查看:29
本文介绍了SAP R/3标准代码修改的手段?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试确定如何修改已安装系统的 SAP R/3 包代码.任何人都可以为此推荐模块/工具吗?

I'm trying to determine how to modify SAP R/3 package code of an installed system. Can anyone suggest the module/tool for that?

推荐答案

SAP 提供了各种客户插件,以便客户修改和适配标准代码:

SAP has provided various customer plug-ins in order to enable customers to modify and adapt standard code:

  • 用户退出(交易 SMOD、CMOD 和 SE81).这个文章 更详细地介绍了用户存在.

  • User exits (Transactions SMOD, CMOD and SE81). This article covers user exists in greater detail.

BADI(业务插件,交易 SE18).这是一种扩展标准功能的面向对象(ish)方式.这个文章更详细地介绍了 BADI

BADI's (Business Add-inns, Transaction SE18). This is an Object Oriented(ish) way of extending standard functionality. This article covers BADI's in greater detail

显式增强点(仅限 Netweaver 7.0 及更高版本,Transaction SE80)是 SAP 标准代码中的占位符,程序员可以在其中添加自己的代码.在这里阅读更多关于增强点的信息.

Explicit Enhancement Points (Netweaver 7.0 and later only, Transaction SE80) are placeholders in the SAP standard code where programmers can add their own code. Read more here about enhancement spots.

所有这些选项都要求 SAP 已经预料到需要增强代码并提供增强功能的挂钩.如果他们在那里,这是维护 SAP 标准代码而不会使与 SAP 的支持协议失效的好方法.

All these options require SAP to have anticipated the need to enhance the code and provide the hooks for enhancements. If they are there it is a great way to maintain SAP standard code without voiding the support agreement with SAP.

以下两种方式要求 SAP 做任何事情:

The following 2 ways do not require SAP to do anything:

  • 隐式增强点(仅限 Netweaver 7.0 及更高版本,事务 SE80).与显式增强点的工作方式相同,但存在于ALL 函数、表单、方法、结构等的开头和结尾.菜单路径 Edit->Enhancement Operations->Show Implicit Enhancement Points 将使这些可见的.隐式增强点的美妙之处在于 SAP 仍然支持它.

  • Implicit Enhancement Spots (Netweaver 7.0 and later only, Transaction SE80). Works the same as Explicit Enhancement Spots, but exists at the start and end of ALL functions, forms, methods, structures etc. The menu path Edit->Enhancement Operations->Show Implicit Enhancement Points will make these visible. The beauty of Implicit Enhancement Spots is that it is still supported by SAP.

程序修复:在 SE80 中点击更改图标,SAP 将要求修复密钥 - 这可以从 SAP 请求 http://service.sap.com(通常由 Basis 人员提供).提供密钥后,您可以正常编辑代码(如果已打开,则使用修改助手).SAP 不支持修复的对象

Program Repairs: In SE80 hit the change icon and SAP will ask for a repair key - this can be requested from SAP at http://service.sap.com (usually by the Basis guys). Once you've provided the key you can edit the code normally (or with modification assistant if it is turned on). Repaired objects are not supported by SAP

截至 2008/2009 年,根据 SAP Enterprise 许可协议,SAP 可能仍支持修复对象

As of 2008/2009 under the SAP Enterprise licensing agreement Repaired Objects may still be supported by SAP

将 SAP 标准程序复制到 Z 包并修改它应该是最后的手段,因为您必须为每个补丁和升级手动比较和维护任何此类程序,这使您的系统的总体可维护性增加了很多更难.

Copying a SAP standard program to a Z-package and modifying it there should be a last resort, as you will have to manually compare and maintain any such programs for every patch and upgrade which makes the general maintainabiliby of your system a lot harder.

SAP 提供工具来修补或升级所有上述对标准代码的更改,大多数情况下,您只需在修补或升级后确认更改即可.

SAP provide tools to patch or upgrade all the abovementioned changes to standard code and most times you have to do little more than just confirm the change after a patch or upgrade.

注意:您可能需要登录 OSS 才能访问文档.如果你不能,SAP 帮助通常很好.

Note: You may need an OSS logon to access the documents. If you can't SAP help is usually quite good.

这篇关于SAP R/3标准代码修改的手段?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆