[求助]SD的用户出口

[求助]SD的用户出口

通常是要的,兄弟你能不能问一些有实质意义的问题,这个问题太简单了,显然我就是condition呀,pricing什么弄exit的金牌杀手, 商量一下,你名字叫bug如果不改以下去做ABAP人家会不放心,老出虫子怎么行?

呵呵，因为写的程序bug总是免不了，所以这个名字没法改，哪天到了程序没有bug的境界再改吧。多谢回答，我们的原则是尽量避免写程序，所以第一次用user exit，刚才查了sap的notes，才知道exit也分几种，以前用的准确的说是cusomter exit。In the SD area (SCM Sales) the following exit technologies are used:User exitsCustomer exitsVOFM routinesBusiness Transaction Events, Business Add-Ins (this will not be explained in more detail in this noteUser exits:At the beginning of the R/3 development the SAP Basis did not offer technologies for exits yet, nevertheless many customers wanted to implement their own functions, checks, and so on. Thus, in the SD area, includes were delivered like, for example, MV45AFZZ. This include contains some empty FORM routines (user exits) to which you can go from the respective processing programs.From the organizational point of view the delivery is arranged as follows: an include with empty FORM routines is delivered with a release and afterwards may no longer be corrected by SAP. This should prevent that a FORM routine which may have been adjusted by the customer is overwritten by SAP again.User exits have no defined interface, that is there is a lot of data available and a lot of program-internal data can be changed. Thus, the user exit is a very flexible and thus also a HIGHLY CRITICAL utility for customer-specific adjustments. When you use user exits for adjustments you must be very careful.When you use user exits, we highly recommend that the functions you developed yourself should be programmed "switched", so when a problem occurs you can restrict whether it is caused by modifications in the user exit or if the problem is on SAP side. Simple example: you define a user-specific ZZ* table with key "Modification" and attribute "active". This table contains an entry for each modification in a user exit. Before a customer-specific source code is processed by reading the customer-specific ZZ* table the system checks whether a user exit (and thus the respective modification) is active. Changes to user exits in SD are MODIFICATIONS, since the original of an object belongs to SAP (thus when you change a user exit an SSCR registration is also required).Customer exits:Unlike the user exits described above, customer exits have a defined interface, that is you can only transfer certain fields to the interface and you can also only change certain fields in a customer exit. In addition, customer exits can be activated and deactivated and thus they can be "switched". With the activation of a project an object is created with the original on customer side, thus it is no modification but a customer-specific enhancement. When you use customer exits, you therefore do not need an SSCR registration either. If available you should use customer exits.VOFM routines:You can develop customer-specific routines with Transaction VOFM for application areas like, for example, conditions of pricing, output determination, data transport routines to copy quotations after sales order, sales order after delivery.These routines are stored in Customizing of every application area (pricing, output determination, and so on), that is enhancements with VOFM can be activated/deactivated. SAP also delivers certain functions by VOFM.依老兄的话，看来用VOFM也可以解决，研究一下