I am sharing my experience of migrating from OBI to Incorta.
Process
Start with Incorta EBS Blueprint
Configure and customize for the deploying company
Optionally, Demo the Fusion Connector
Preview and demo to business users using their own data
Provide the existing OBI dashboard usage analysis – Help prioritize the replacement project
Provide the lineage and SQLs from OBI. Get the access to nqquery log and SDE logic to the development team
Analyze the SQL and OBI report one by one against the blueprint business schemas
Interactive processes about enhancing Incorta physical schema and creating dashboards in Incorta
Create materialized View when necessary
Demo and get feedback from business users during the development
Leverage the existing OBI team in verifying and comparison, help the team gain knowledge about Incorta for future support
Prepare the pilot and overlap period before shutting down OBI. Define the Exit criteria
Prepare the training to the future analyzers/superuser, who can create and manage their own contents. This may be necessary as a recursive event for several months. Providing an office hour will be helpful.
Provide a demo to Excel Add-in if necessary
Provide the SQL interface if necessary. Control the usage by understanding their usage. This may be helpful for Tableau users, but need to be careful as it impacts the system resource usage
Schedule the dashboard delivery and the download. Configure the integration with network drive storage. FTP, dropbox, OneDrive, GDrive, etc.
Along with the development of the new content, start discussion about job schedule options. For example, dependencies from Incorta to source app batch process. Also, understand the source data update pattern and frequency. For example, when the Transfer to GL was executed, when the depreciation process is executed. How frequent these processes are run. For example, any difference in period closing weeks?
Very few resistance from existing OBI developers since most of them see this as an opportunity.
Learning new skills such as using Spark SQL and PySpark in creating materialized views. Explore ML library in Incorta.
Their Data Model knowledge is typically the asset to the new platform.
One of the major change introduced in BI Apps 11.1.1.7.1 is the way how we manage the ETL task sequence and trim the unnecessary tasks.
This functionality was accomplished earlier using DAC. The problem we frequently faced was that the DAC repository and the INFA repository are maintained as two separate repositories. We have to sync up the name of tasks exactly in order to use DAC to manage the task execution of the Informatica workflow tasks.
Several people are curious about what are OTBI and OBIA, and what are the differences between OTBI and OBIA. I will discuss these in this article.
OTBI stands for Oracle Transactional Buisness Intelligence.
OBIA stands for Oracle Business Intelligence Applications.
Let’s start with OBIA. OBIA is the pre-packaged BI Apps that Oracle has provided for several years. It is the data warehouse based solution. It is based on the universal data warehouse design with different prebuilt adapters that can connect to various source application to bring the data into the data warehouse. It allows you to conslidate the data from various sources and bring them together. It provides a library of metrics that help you measure your business. It also provides a set of predefined reports and dashboards. OBIA works for multiple sources, including E-Business Suite, PeopleSoft, JDE, SAP, and Fusion Applications.
OTBI is different. First of all, it is a real time BI. There is no data warehouse or ETL process for OTBI. Second, it is for Fusion Apps only. OTBI is leveraging the advanced technologies from both BI platform and ADF to enable the online BI queries agains the Fusion Applications database directly. In addition, in some area, such as Financial, you can also connect to the Essbase cubes. Unlike OBIA, OTBI does not have a lot of prebuilt dashboards and reports. The reason is that for some advanced analysis, the data need to be prepared. You cannot get eveything you can get from the OBIA data warehouse in OTBI.
Both OTBI and OBIA are available from the same metadata repository. Some of the repository objects are shared between OTBI and OBIA. It was designed to allow you have the following configurations:
OTBI Only
OBIA only
OTBI and OBIA coexist
If you implement Fusion Apps, you can enable OTBI. You can use the BI EE Answer to access the prebuild metadata and metrics those are built against the Fusion Apps. You may not get the full powerful prebuild dashboard and repost and prebuilt navigation workflow. However, you can start experiencing what the BI EE based reports look like. You can start bring the data out from your OLTP system. You can provide training to the users to get familar with the subject areas, some of which are shared with OBIA.
If you enjoy OTBI and want to further get OBIA with a data warehouse based solution. You can implement OBIA later. Some of the OTBI reports maybe switched to run against OBIA. Some of OTBI reports can continue connecting to Fusion Apps directly. They can coexist in a single BI server and a single BI answer client.
Both OTBI and OBIA are accessing Fusion Apps via the ADF. This is a more advanced topic.
User Defined Function (UDF) is a very powerful feature from ODI.
One of features that are absent from other ETL tool is to address the need to support different database platforms. I won’t blame those ETL tools since they are not really designed for pre-package BI Apps.
Who will need to switch database platform like that?
If your data warehouse is deployed on Oracle, you can use Oracle SQL. If you are using Teredata, you can use Teradata. You know that your PeopleSoft is running on DB2, you can write the DB2 SQL. In the custom data warehouse ETL environment, switching database platforms is uncommon, one time only task. You do not need to switch among different database platforms within your code.
A prepackaged BI apps ETL developers, however, are facing different challenges. You do not know if the source apps is running on which database platform. Also, you want to give customers the choices on the database platforms to deploy the data warehouse.
ODI UDF comes very handy. You can create a UDF to use in your SQL, you can have multiple implementation of the UDF for different database platform. You can use GetDate() for MS SQL and use SYSDATE for Oracle database in the implementation, but you can create you own function such TODAY() and use in your SQL.
User Defined Function is not a new idea. You may see something similar in other tools. However, to be able to use UDF in SQL and to be able to use UDF with multiple implementations under different technologies, I only see the feature in ODI.
I won’t be surprised to see those “me too” products in the near feature.
More and more companies are moving to use prepackaged BI apps.
1. It does not allow you to use parameters to the PeopleSoft connect. It may be changed later. However, it was a big issue when we try to address customer issues.
2. It requires EFFDT as an input.
It expects that people change the EFFDT using Mapping Editor. How can a business user does that every month?
3. It asks for a Tree Name. Many PeopleSoft tree structure supports multiple trees. Tree is just a header of the hierarchy. Whenever you add a new Tree, you need to create a new mapping!!
It does not make sense to use PowerConnect due to the customer demands. All above requirements are from customers.
We have no choice but stop using it.
It is a nice feature, but it was not designed for a prepackaged apps.
The OLTP source applications like PeopleSoft and Siebel applications can run on many different databases including Oracle, MS SQL, or DB2. The target data warehouse can also run on different database platforms, incluidng the above databases, plus Teradata.
Various technologies can be used to enable the cross database platform support in the pre-packaged BI apps. Oracle BI Enterprise Edition allows you configure the database connections using the native drivers. ODBC can also be used to access different databases.
In order to deliver to deliver the pre-packaged ETL adapters, two technologies can be used : ANSI SQL and ETL tool specific SQL. It is preferable to avoid the dependency on the ETL plarform and use ANSI SQL92 syntax. When we move from ETL to ELT, Read the rest of this entry »
Typically using SQL*Loader assumes that a flat file will be used as the input. The file will need to be created and generated before the SQL*Loader can take the data from the file and load the data into Oracle. The performance can be improved and the disk space can be saved if you use named pipe with SQL*Loader.
Oracle BI Applications 7.9.5 is released early this month. Here is a quick summary of the features introduced in this release and where you can get more information about it.
To develop or deploy a BI solution for your organizations, you need to have the right people involved in the time time. Here are typical roles involved in a BI data warehouse project.
PeopleSoft Enterprise Performance Management was the pre-packaged BI applications for PeopleSoft application. It has been in market for nearly 10 year. I recently learned its history, product coverage and architecture from my colleagues. Read the rest of this entry »
You must be logged in to post a comment.