Overview of stored procedures

When processing business object requests, the connector uses stored procedures to invoke APIs that operate on the data present in the interface tables to perform the required operations on the application base tables. These required operations are insert, update, and delete. A stored procedure is a schema object that encapsulates a set of operations that the connector performs on an object in the Oracle application database.

The connector calls stored procedures under the following circumstances:

Note:
For event notification, the connector uses triggers on the application base tables to generate event business objects. Stored procedures are not used for event notification.

Included with the connector are sample business objects and wrapper stored procedures that demonstrate how to invoke concurrent programs and APIs using the connector's stored procedure functionality. Table 18 lists the sample business objects and their corresponding wrapper stored procedures.

Table 18. Sample business objects and wrapper stored procedures
Sample business objects Wrapper stored procedure
BO_ORACLEAPPS_CUSTINTERFACE CW_CUSTOMER_INTERFACE
BO_ORACLEAPPS_CUSTRETRIEVE Not applicable. This object is based on views.
BO_ORACLEAPPS_ITEMINTERFACE CW_ITEM_INTERFACE
BO_ORACLEAPPS_ITEMRETRIEVE Not applicable. This object is based on views.
BO_ORACLEAPPS_ORDER CW_PUBLIC_API_PROCESS_ORDER
BO_ORACLEAPPS_ORDERRETRIEVE Not applicable. This object is based on views.

The sample wrapper stored procedures CW_CUSTOMER_INTERFACE and CW_ITEM_INTERFACE contain logic to call the concurrent program. The parameters required to run the concurrent program can be taken from the business object or can be found in the wrapper stored procedures. The sample stored procedures take their parameters from attributes in the business objects.

The sample business objects and wrapper stored procedures are located in Appendix D. Business object and stored procedure samples

Copyright IBM Corporation 1997, 2005. All Rights Reserved.