WebSphere Adapter for Oracle E-Business Suite

Outbound processing sample applications

Two outbound processing sample applications are provided with this solution. One uses Oracle database Interface tables, which is the standard outbound scenario for the Oracle E-Business Suite; and another uses API calls. The first outbound sample has two parts: it uses the Create operation and then the Retrieve operation through the Adapter for JDBC.

Outbound processing using Interface tables

The first outbound request processing sample has two parts:
  • Creating a business object by using a Create operation
  • Retrieving an object by using a Retrieve operation
The Oracle database permits the retrieval of data from the applications's base tables. The business objects used for the Retrieve operation reflect the base tables' representation of the data. The Oracle database does not permit the manual modification of data in the base tables. Thus, this sample uses the interface tables when the Adapter for JDBC sends business objects that change the content in the Oracle database. This is the standard outbound request processing scenario. After the interface tables are updated with the business object data, a function is called, through a stored procedure, that moves the data from the interface to the base tables.
Figure 1. Create scenario
This image is described in the surrounding text.

The Adapter for JDBC is used to populate the interface tables with business object data. Because Oracle permits processing both new and existing updates to data entities through the interface tables, Create is the only operation needed to process new and changed data. The business object data can be moved into the Oracle base tables by invoking an internal, standard Oracle function. The function is called through a stored procedure to move the data to the base tables using AfterCreateSP application-specific information on the business object.

The Create and Retrieve operations use different sets of business objects because they represent different tables in the Oracle database. This sample application includes the wrapper stored procedure for the function call to move the data to the base tables, plus the sample content to use for the procedure.

Figure 2. Retrieve scenario
This image is described in the surrounding text.

Outbound processing using API call

This sample shows how the Adapter for JDBC can call an Oracle E-Business Suite API directly. The JDBC driver limits parameters to simple, non-record data types when the Adapter for JDBC calls an API directly. Most Oracle APIs include record parameters. API calls that use record type parameters can be called through the Adapter for JDBC only if they are wrapped so that the call to the wrapper stored procedure does not use the record type parameter. The API call for this sample uses simple data type parameters.

This sample uses the Adapter for JDBC to call an Oracle API directly, which creates a concurrent program executable in the Oracle database. The content for this sample includes examples of the API call.

Related tasks
Sample 1: Sending outbound data to the EIS
Sample 3: Calling an Oracle E-Business Suite API for outbound processing

Terms of use |

Last updated: Mon 30 Oct 2006 03:46:26

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)