After you activate a customer exit in an SAP standard program, it calls an empty function module. So when the SAP standard program calls the user exit, the user exit calls the function module, and the function module calls your code:.
Activating a function exit requires creating a project in the transaction CMOD Customer Exits and activating the project. An entity provided by SAP to allow the standard behavior of a specific application, such as Financials, to be enhanced without modifying the standard solution. Instead of putting logic in a standard SAP program or function module, you create a class that implements predefined methods from an interface.
The SAP standard fires those methods at predefined points. Some BAdIs can have multiple implementations, which is great for software development as many developers can use the same BAdI independently. Furthermore, you can create BAdIs for your own programs. BAdIs are great because they can be used without modifying the original code such as customer exits. There are both single-implementations and multiple-implementations of the BAdI, and multiple implementations can be created from a single BAdI definition.
A BAdI consists of an interface, a set of filters, and various settings that can be customized depending on the prerequisites in place, and these implementations can be externally controlled through switch framework.
BAPIs provide an object-oriented view of developing business solutions and an interaction method by which objects can be fused and integrated to resolve problems. Plus, don't miss future infographics and free SAP tips and insights that are available only to newsletter subscribers. BADI allows more complex system infrastructure that can include SAP, country-specific versions, industry solutions, customer developments, and so on.
There are two kinds of applications of BAPIs. Second, they can be defined as interfaces that are implemented outside of an SAP system but can be called from within the SAP system.
BAPI is commonly used for setting up a synchronous communication interface between two parties. It is identified with a three character code that tells the SAP system that a custom chunk of code needs to be executed at a predefined point of a standard SAP program.
If a code starts with S letter, it is a standard user exit delivered by SAP. If a code starts with U letter, it is a custom user exit defined by a user. Inside a user exit it is possible to read and change almost any data local or global from the host SAP program. Therefore, user exits give you a lot of flexibility but this flexibility comes at a price of the higher risk to make a critical error that would lead to an ABAP dump or inconsistency in database records.
It serves the same purpose as User Exit : enabling users to add their own functionality to the standard SAP transactions.
Unlike User Exits , Customer Exits are more restrictive in terms of what you can do with them because inside a Customer Exit you can only access and manipulate the parameters specified with keywords import, export, changing, tables.
At the same time it is much safer to use Customer Exits than User Exits because the risk to break something or create inconsistent database entries is low.
Nevertheless, let us elaborate a little bit. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Collectives on Stack Overflow. Learn more. Ask Question. Asked 7 years, 5 months ago. Active 1 year, 2 months ago. Viewed 16k times. Improve this question. Boghyon Hoffmann Eduardo Copat Eduardo Copat 4, 5 5 gold badges 22 22 silver badges 39 39 bronze badges. Add a comment. Active Oldest Votes.
0コメント