Written by Helene Abrams Thursday, April 15 2010
Everyone always asks us how we do what we do, and why, in over 20 years of Oracle E-Business Suite implementations, no one else has ever created software to automate the process of changing the underlying configurations or consolidating or separating data. eprentise software is built on a proprietary process called Metadata Analysis that is really the engine that drives the changes in an Oracle E-Business Suite. eprentise Metadata Analysis uses patterns and rules-based technology to discover everything about a particular database.
A good analogy for Metadata Analysis is an architecture diagram for an already-built house (see That Old House). The architecture diagram includes all the wires and the pipes in addition to all the other internals of the house, like where every stud is located, whether the wallboard is aligned, the mechanicals including the type and efficiency of the heating unit, and the age of each appliance and how it is used.
This architecture diagram knows the capacity of each wire or object in the house, knows what it is connected to, knows the order of operations if something needs to be changed, and fully understands the impact of that change. Metadata Analysis discovers and documents all database objects (e.g., tables and columns, primary and unique keys, rows and objects, foreign keys, other constraints, triggers) and application objects. It understands the data and has a built-in knowledge repository of how every piece of data is used, and how that data supports each business process. When it finds information (in the format of rules) about an instance, it confirms the information by checking every row of data to see if the information is consistent within the database, then validates the information against the eprentise Knowledge Repository. In addition, the eprentise Knowledge Repository houses information from each version of Oracle E-Business Suite gleaned from a variety of methods. (Only about 30% of what we find is documented in the DBA or FND tables or in the Oracle Technical Reference Manuals).
After all the rules about the metadata are confirmed and validated, Metadata Analysis populates the eprentise Knowledge Repository with information specifically about the database, its schemas, constraints, and other database objects. It also compares configuration details between a source and a target. The source and targets can be different database instances, or different operating units, or really anything in the EBS. eprentise software uses the rules that it finds during the Metadata Analysis process to dynamically generate code to perform four functions: copy, filter, change, and merge.
Again, back to the house analogy. Once you have all the building materials available, and if you can get a good schematic of the house, you can remodel it with the right tools. You can move walls, add on to the existing structure, or even start over again on the same foundation. Within Oracle E-Business Suite, Metadata Analysis gives us the schematic, your data and business processes are the building materials, and we have the software tools to remodel EBS any way that you want, whether it is merging data together, splitting it apart, changing it, or moving data to realign it with the changes in your business.
| < Prev | Next > |
|---|
Related Articles
Related Pages
Enter your email address to sign up for our Newsletter
January Puzzle
A traveler gets lost on a deserted island and finds himself surrounded by a group of n cannibals.
Each cannibal wants to eat the traveler but, as each knows, there is a risk. A cannibal that attacks and eats the traveler would become tired and defenseless. After he eats, he would become an easy target for another cannibal (who would also become tired and defenseless after eating).
The cannibals are all hungry, but they cannot trust each other to cooperate. The cannibals happen to be well versed in game theory, so they will think before making a move.
Does the nearest cannibal, or any cannibal in the group, devour the lost traveler?
Solution
The short answer is the traveler’s fate depends on the parity of the group. If there is an odd number of canibals, the traveler will be eaten, but if there is an even number, the traveler will survive.
To prove this, we will consider small groups and use mathematical induction to explain the solution for larger groups.
Case n = 1: this is an obvious case. If there is one cannibal, the traveler will be eaten. It doesn’t matter that the cannibal will get tired because there are no other cannibals around as a threat.
Case n = 2: this is a more interesting case. Each cannibal wishes to each the traveler, but each knows he cannot. If either cannibal eats the traveler, then he will become defenseless and the other one will eat him. So each cannibal uses backwards induction to realize that the only strategy is to not eat the traveler. The hapless traveler finds a bit of luck, therefore, and actually survives.
Case n = 3: this is where the problem gets interesting. The best strategy is for the closest cannibal to make a move and eat the traveler. The cannibal will be defenseless after eating, but ultimately he will be safe. Why is that? The reasoning is due to induction: once the cannibal eats the traveler, the resulting situation has 2 unfed cannibals and the 1 defenseless cannibal. But as we just showed above, when there are 2 unfed cannibals, neither will make a move for fear of being eaten by the other! Thus the first cannibal to make a move will be safe as the remaining 2 cannibals block each other.
We can prove the higher cases using mathematical induction. If the number n is odd, then the closest cannibal can safely eat the traveler because the remaining number of unfed cannibals is even (and by induction, with an even number of unfed cannibals no one makes a move). If the number n is even, then no cannibal will eat the traveler, for if he did, the remaining number of cannibals would be odd, meaning he will get eaten by the induction hypothesis.
Success Tips for Oracle Project Management
- Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
- Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
- If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
- Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
- Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
- Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
- Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
- Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
- Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
- Include governance, risk, and compliance management as part of the project plan.
- Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.
The Analyst Corner
John Van Decker, Research VP of Gartner, states:
"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."
