IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > SAP Software > Configure the module for deployment > Performing prerequisite tasks specific to an interface

Implementing event-detection mechanisms

When you use the Advanced event processing interface for inbound processing, you must determine an event-detection mechanism for the business process with which you are working. You then implement that process.

These procedures are for the Advanced event processing interface only.

If you are not using the Advanced event processing interface, skip the procedures.

Sample code and examples are provided to help you implement an event-detection mechanism.

• Implementing custom triggers
  Custom triggers requires encapsulating a portion of ABAP code in a custom function module. The event-detection code is written as a function module to ensure that the processing remains separate from the transaction. Any tables or variables used from the transaction must be passed to the function module by value and not by reference.
• Implementing batch programs
  To implement batch program as an event detection mechanism, you must write an ABAP program that evaluates database information.

  If the criteria in the ABAP program is fulfilled when the program executes, then an event is triggered.

• Implementing business workflows
  Business workflow is a set or sequence of logically related business operations. The processing logic within a workflow detects events. The business workflow event-detection mechanism relies on the SAP Business Object Repository (BOR), which contains the directory of objects along with their related attributes, methods, and events.
• Implementing change pointers
  A change pointer uses change documents and is one of the more challenging event detection mechanisms to implement. The SAP Business Object Repository (BOR) is used as well as Application Link Enabled (ALE) technology. A change document always refers to a business document object having at least one database table assigned to it.

  If the data element in a table is marked as requiring a change document and the table is assigned to a business document object, then a change in value of the field defined by the data element generates a change document. The changes are captured in tables CDHDR and CDPOS and are used for event detection.

Performing prerequisite tasks specific to an interface