Oracle PIM Data Hub in R12.1.3 and prior is actually contained in a EBS Applications instance. Therefore, there is a question posed as to whether the PIM data hub should be managed on the same instance as the rest of the Oracle E:Business Suite ERP system is managed.
If you run your implementation project well with a good phase zero happening for MDM, you could potentially come up with multiple scenarios.
1) Run the implementation on one instance but divide the “gold” instance right before go live so that there are two production instances with a full synchronized interface working for the item and product information.
2) Run the implementation of both EBS (Financials and/or Manufacturing) and PIM data hub at the same time but on two separate configured instances. Then have the same interface described in number one above.
3) Run the Product MDM Data Hub implementation completely separate from the EBS implementation (or re-implementation) but work the Product Hub into the same instance as the EBS instance.
4) Run the Product MDM Data Hub implementation completely separate from the EBS implementation but plan the Hub to be a separate instance integrated/interfaced OR not.
Size and use: First parameter of decision criteria for me is how big is your product MDM hub and spoke going to be? The bigger the “in and out” of the hub the more transactions hitting the instance. No one in the Financials or Manufacturing wants you to kill their transaction performance.
The second facet is the “Use”. If the “Use” of the PIM data hub is primarily for the EBS users then you might weigh heavily to share the same instance to give the EBS users instance integration and access to product information. This is especially true if you don’t have any other spoke systems gathering product data.
Second part of the decision criteria is always the three big ones, Time, Money, and Resources. No need to elaborate on the big three. Most project managers are quite familiar with these constraints.
Lastly, Oracle Specific Factors are the final part in the article to mention because this is where Oracle provides the limitations on instances together or separate. Oracle PIM changes faster than the EBS functionality and abilities in the past few years. It is easier and less restrictive to upgrade PIM to 12.2 than it is to upgrade EBS to 12.2. It is especially true when there are a lot of customizations or an older EBS instance to attempt the patch applications upon.
- Why Phase One in “16 weeks” minimum? (mckinleyalexandra.wordpress.com)
- Shared vs Full HR Install in the PIM Data Hub instance (mckinleyalexandra.wordpress.com)
- Implementation Strategy Comparison between Siebel and PIM Data Hub (mckinleyalexandra.wordpress.com)
- New Poll for Oracle PIM Data Hub Implementations (mckinleyalexandra.wordpress.com)