Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter Sample Transaction Definitions User’s Guide Documentation | Adapter Services | Transaction Processing
 
Transaction Processing
The adapter communicates using two types of transactions: Oracle Applications‐to‐IS transactions and IS‐to‐Oracle Applications transactions. Within each type of transaction there are two types of operations. For IS‐to‐Oracle Applications transactions, the adapter can insert data into open interface tables and can execute error SQL to retrieve error information. For Oracle Applications‐to‐IS transactions, the adapter can query the Oracle Applications system and can run corresponding acknowledgment (ACK) services, which mark the data as processed.
The following sections describe the processing for these types of transactions.
webMethods IS-to-Oracle Applications (Inbound)
webMethods clients can invoke adapter services that insert records into open interface tables. These records will either insert new information or update existing information in the Oracle system. webMethods clients can also invoke services to retrieve open interface import errors from the Oracle system.
To retrieve information from the Oracle database, a service does one of the following:
*Executes stored procedures on the Oracle system
*Executes an SQL SELECT statement
The following diagram illustrates the steps that occur when you run a service to update the Oracle DBMS and then run a service to check for errors that might have occurred during import processing.
Step
Description
1.
The webMethods client invokes a service to update the Oracle DBMS. You created this service from a transaction definition that is based on a set of specific open interface tables. The service receives the information required by the open interface table via the service specification.
2.
The service executes. It connects to the Oracle Applications Instance via JDBC and inserts data into the open interface tables that are associated with the service.
3.
The service receives output to indicate that the table insert is complete.
4.
Output is returned to the client.
5.
An Oracle Applications import process runs in the Oracle concurrent manager. The import process moves the data from the open interface tables to the live Oracle DBMS. If errors occur in the import process, Oracle records them in the appropriate open interface table.
6.
The webMethods client invokes a service to query Oracle Applications for errors that might have occurred during the import process. You created this service from a transaction definition that is based on a stored procedure, view, or SQL SELECT statement. The service receives the query parameters for the SQL statement via the service specification. The service can also be invoked by the webMethods scheduler to periodically pull out transactions for a trading partner.
7.
The service executes. It connects to the Oracle Applications Instance via JDBC. Based on the transaction definition used to create the service, the service does one of the following:
*Calls a stored procedure
*Executes an SQL SELECT statement
8.
The stored procedure or SQL SELECT statement retrieves information from the DBMS.
9.
The retrieved information is returned to the service.
10.
The service returns output back to the webMethods client.
How Data Is Passed During the Transaction
When a webMethods client invokes an adapter service, it passes input values to the service in a document. The service then passes the data from the document in an SQL statement. The statement is executed via a JDBC connection. When a service successfully inserts data into the open interface table, the service puts a variable called message into the pipeline as output. If there is a problem inserting the data into the Oracle Applications open interface tables, a service exception is thrown.
Services that retrieve information from the Oracle system return a document that contains the requested data. If there is a problem selecting the information, a service exception is thrown.
Oracle Applications-to-webMethods IS (Outbound)
webMethods clients can invoke adapter services that retrieve information from the Oracle Applications system. Generally, the Oracle Apps Adapter initiates the interaction with the Oracle Applications instance. However, you can use the Oracle Apps Adapter retrieve the business document to update other systems (legacy systems, ERP systems, or trading partner systems) with information retrieved from the Oracle system. Clients can also invoke acknowledgment services to maintain an accurate status of the transactions within the Oracle Applications system.
The following diagram illustrates the steps required to use Oracle information to update a trading partner’s system.
Step
Description
1.
The webMethods client invokes a service that you created from a transaction definition that is based on a stored procedure, view, or SQL SELECT statement. The service passes query parameters to the stored procedure, view, or SQL SELECT statement.
2.
The service executes. It connects to the Oracle Applications Instance via JDBC. Based on the transaction definition used to create the service, the service does one of the following:
*Calls a stored procedure
*Executes an SQL SELECT statement against tables and views.
3.
The stored procedure or SQL SELECT statement retrieves information from the DBMS.
4.
The retrieved information is returned to the adapter service.
5.
The service returns the output to the webMethods client.
6.
The webMethods client optionally performs internal processing or invokes services. For example, you might choose to update your SAP system at this stage.
7.
If there is an acknowledgment service defined for the transaction, the flow needs to execute it. The acknowledgment service connects to the Oracle Applications instance via JDBC. Based on the transaction definition used to create it, the service does one of the following:
*Calls a stored procedure
*Executes an SQL UPDATE statement
Note:
The acknowledgment service is necessary for Oracle Applications to maintain the accurate status of transactions. For example, suppose that a purchase order has state of “approved” in the DBMS. It remains “approved” until an acknowledgment from the client is received, which changes the state to “approved, printed.” This ensures that the purchase order, which has already been received by the client, will not be included in the next data retrieval transaction.
8.
The adapter service tells the Oracle Applications instance that the transaction has been processed.
9.
The service returns output back to the webMethods client.