Oracle Warehouse Builder 11g/10g - Ebusiness Suite Connector
Posted by Venkatakrishnan J on August 31, 2007
I was speaking to one of the users of OWB yesterday and the conversation drifted towards the Ebusiness Suite connector that OWB 11g/10g provides to the end users. The user wanted to know how is the ebusiness connector different from a normal connection to an oracle database? It made a lot of sense to me considering the fact that OWB connector does not provide out of the box ETL mappings (based on business modules in ebusiness suite like BI Applications) to a target warehouse. The only way to find that out was to use the connector and see what it does differently. I did exactly that and thought that this deserves a blog entry in itself. Ebusiness suite connector does a lot of things other than connecting to the ebusiness database. It logically groups all the tables according to the business functions.
The first step i did was to create a connection to an ebusiness suite database using the Application module. The connection details would be exactly same as what you would give for an oracle database.
Once the connection details are specified, the connector gives a window that would look like this
As you see above, the connector provides 2 options. First one is an option where in one can choose a business domain and the 2nd one is an option similar to an ordinary table import wizard from a schema. The 1st one is the one that is unique to the connector i.e identifying and segregating the tables based on the business modules. The business modules would look like this
In our illustration i would choose the Order Entry (OE) module and import all the tables under that.
As you see above, the connector helps a developer in working on the tables that are specific to his module. It reduces a lot of effort, considering the fact that ebusiness suite has a huge number of tables. Apart from making the life of a developer easy by segregating the tables and views, the connector can also write back to an ebusiness suite instance. It can deploy objects to the concurrent manager. One can use the ebusiness suite objects both in the mappings and also in the process flows. One can access the documentation about the connectors here
October 31, 2007 at 8:43 am
Good Post as usual. E-Bis already has strict naming convention and typically a table for OE will start with OE_. Though there are overlaps like certain tables are used across the modules. HZ_% tables being one of the example of this. It would be interesting to see whether this are brought over while migrating AR module and even OE module (both of this use HZ_% modules extensively).
I have worked with OWB for some time but never got an opportunity to use the E-Bis connector. It would be interesting to see whether the connector leverages the flex-field setups and other metadata and present it to the ETL developer in more user user friendly manner. The connector is paid option and I bet that it should have some interesting features to extract the transaction and master information from EBS more easily without bothering about where to go for lookups, or which tables to link for particular transaction etc. Also it would be good to explore the parallels/contrasts between the EBS adapter for OWB and the one that comes with SOA suite. Some thought food
February 1, 2008 at 3:41 am
Hi Venkat,
Can we use Oracle Warehouse Builder to load data into Oracle EBusiness Suite table(s)?
For example: we may have a workflow system to create Chart of Accounts, once a new
account is created there, we would like to load the new account into Oracle Ebusiness Suite.
Thanks,
March 4, 2008 at 4:57 am
Lian,
I’m one of the PMs for Warehouse Builder.
The short answer to your question is “yes”. All of the OWB Connectors (except the one for SAP) allow you to write to the application as a target.
Come to http://www.oracle.com/technology/products/warehouse for more details.