Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter Sample Transaction Definitions User’s Guide Documentation | Adapter Services | Considerations When Using Transactions | Considerations for Multiple Organizations
 
Considerations for Multiple Organizations
You can configure a single installation of Oracle Applications to support multiple organizations within an enterprise.
*Oracle Applications-to-IS transactions perform selects of information that is stored in the Oracle Applications DBMS. These select statements and stored procedures work on views defined on the Oracle Applications DBMS. Transaction definitions are available for use with the Oracle Apps Adapter that return data from all organizations within the Oracle Applications instance. You can customize these views or the queries in the transaction definition by adding a WHERE clause that subsets the data returned to a particular organization ID or set of organization IDs.
*IS-to-Oracle Applications transaction definitions insert data into the Oracle Applications open interface tables. The Integration Server can receive transactions from any number of sources, via any number of protocols.
*When you implement integration between two trading partners, your service must be able to figure out who the transaction is for; in other words, it must be able to map organization IDs. When your service encounters an organization ID, it needs to look the ID up in a database, in an LDAP store, or it must be hard-coded in the service.