Data Transformation Engine Intelligent Business Integration Reference Guide

Chapter 3 - Methods of Execution Event-Driven Execution Model
Intelligent Business Integration Reference Guide
45
The data flow for this system is as follows:
1 The VBInput source to the VBtoSQL map component is a file. The arrival or
update of this file is the trigger for the automatic invocation of an instance of
the VBToSQL map component by the Event Server. This trigger, represented
by the glasses symbol (
), displays on the VBtoSQL map component icon
and on the VBInput card.
If the map component has been configured accordingly, multiple instances of
the same map component are invoked if the file is updated again before the
first map instance completes.
The transformation logic in the map component is executed, and the resulting
output is delivered to a SQL Server database table (SQLInsert output).
2 The output SQLInsert from the VBtoSQL map component is the same table
as the input to the second map, SQL to R/3 (VendorMaster). Inserts to this
table are also defined as triggers to the SQL to R/3 map component. When
inserts to the VendorMaster table occur, the Event Server triggers the SQL to
R/3 map automatically to retrieve the rows inserted.
The data from the input rows in the VendorMaster table are converted into
SAP R/3 IDocs. The Mercator R/3 ALE adapter delivers the resulting IDocs as
output to the R/3 system.
3 SQL to R/3 (VendorMaster) is configured to generate an audit log. Based on
the map settings configuration, the audit log can contain various aspects of
each map thread’s execution, settings, and data. These audit logs can
themselves be mapped as input data to provide transaction history and error
and exception logging to any output resource supported by a Mercator
resource adapter (such as the Database or E-mail adapter).
Because maps are able to handle multiple inputs and multiple outputs in a single
execution thread, it is easy to create additional output cards for the maps so that
transaction logging data can be delivered to any enterprise-level database, or
update transaction data, in real-time, to data warehouse databases.
For example, the AuditLogProcessing subsystem (a subsystem is an object that
represents another system that you have already defined) is a reusable Event
Server-controlled system that provides the transaction logging and exception
handling service. This system can be used to process the audit logs for multiple
Event Server-based systems. Execution history logging can be achieved by
mapping each map thread’s audit log to an external database.