Send Services
Send services notify the Integration Server of changes in Oracle Applications systems when specific events occur in the Oracle Applications system, such as when data is inserted, updated, or deleted. Send services then deliver the data in the form of business documents.
Send services use a two-part process:
On the Oracle Applications system, custom triggers and stored procedures capture events that occur in the Oracle Applications production tables. The events are recorded in a custom table called WM_TRACKCHANGES. The custom table maintains the events as records until a send service polls the tables to retrieve the data. Each send service uses one or more custom triggers or stored procedures to capture events.
On
Integration Server side, send services poll the custom tables and the Oracle Applications production tables to retrieves business documents related to the events recorded in the custom tables, and then the send services send the documents to the designated recipients of the service.
Send services handle transactions differently depending on whether the event on the business document is an INSERT, UPDATE, or DELETE event, as follows:
INSERT and UPDATE events: Whenever a business object is inserted or updated in Oracle Applications, the service creates a snapshot of the business document in the Oracle Applications production tables at the instance the tables are polled, and sends it to
Integration Server.
The INSERT and UPDATE events are captured using stored procedures. These procedures use a reference table called WM_SEND_REFERENCE_T to compare and identify the changes made between the previous and current send service.
DELETE events: Send services process delete events differently depending on how the business object is deleted in Oracle Applications. Business objects may be deleted from Oracle Applications in one of the following two ways:
Actions performed in the Oracle Applications system that result in a status update in the transaction header base table that indicates a “logical” delete of a business object are treated as if they had a status of UPDATE.
Actions performed in the Oracle Applications system that result in an actual DELETE of the record from the transaction header base table will result in the object being deleted. Business documents corresponding to this type of action will not be complete documents; they will only contain basic header-level information required to properly identify the business document to delete the business object.
Custom triggers capture the DELETE events that occur in the Oracle Applications production tables.
The following sections describe how the custom tables work, and how the send services interact with the custom tables to retrieve data and send it to the Integration Server.