Connection of Business Objects 
To process business objects from other SAP application systems in SAP Event Management (SAP EM), you must have defined and implemented an interface between the SAP application system and the SAP EM interface.
If a connection to a certain business object in an SAP standard system already exists, you do not have to define one.
Note
For an overview of the existing connections to certain business objects in standard SAP systems, see SAP Service Marketplace at
For more information about connecting business objects, see SAP Service Marketplace at
If a connection to a certain business object in an SAP standard system does not exist, you must define and implement one yourself.
You can use the following options to connect business objects from other SAP application systems to SAP EM:
Business Add-Ins(BAdIs)
The BAdIs implemented in other SAP application systems call Business Application Programming Interfaces(BAPIs) (for example, to create event handlers or to report events).
Note
For more information about Business Add-Ins, see the SAP Library under
Business Transaction Events (BTE)
User exits
Direct calls in the SAP application system
Irrespective of the option that you choose for connecting a business object, you must collect the following information and transfer it to data containers:
All application tables that are relevant to the business object
The business process that is relevant to the business object
The SAP application system uses the data containers to determine the supply chain event management relevance of an application object and to transfer the relevant data to SAP EM.
You must have installed an SAP Plug-In in the SAP R/3 system that contains the SAP EM interface. The Support Packages and SAP Notes that refer to the SAP Plug-In must have been imported.
You must have executed Customizing for the connection in the SAP Plug-In and in SAP EM to be able to connect to SAP EM.
The following figure shows the overall picture when linking an SAP application system to SAP EM and the BAdI call:

The BAdI that the system calls from a transaction (for example, saving a shipment document) or using an application system interface (= call from an existing business object) is found in the SAP system.
You have defined the application interface settings for the following:
Creating and updating event handlers
Creating events
You can also connect external systems to SAP EM using BAPI interfaces .
SAP EM contains Customizing that is specific to an event handler type.
All these elements are also provided with a visibility process .
Example
You implement the shipment BAdI BADI_LE_SHIPMENT (BAdI implementation /SAPTRX/LE_SHIPMENT with BAdI method BEFORE_UPDATE) to establish the technical connection so that SAP EM creates an event handler in accordance with Customizing, for example.
You decide on an interface type.
You implement this interface type with the relevant implementation method.
Note
For more information about implementation methods, see SAP Service Marketplace at
After you have completed the implementation, you test your application interface with the transaction from the SAP application system.
Note
For example, on the SAP Easy Access screen, choose:
or choose transaction VT01N (transportation) or
or choose transaction VL31N (inbound delivery).
You have connected a business object to SAP EM. The SAP application system calls the SAP EM interface. If you have configured Customizing accordingly, the SAP application system extracts data and sends it to SAP EM. SAP EM performs one of the following options:
Creates a corresponding event handler
Updates the corresponding event handler on the basis of an event message
Reports an event