There are many discussions (meetings) when a MDM PIM project starts. Scoping establishes what systems will be replaced and what systems will be spoke systems for the MDM initiatives.
The systems that are to become spoke systems have either already existed in the organization or they are being implemented at the same time as the MDM PIM initiative.
Some organizations use the PIM Data Hub to supplement or enhance the E-Business Suite applications.
For this post, the author’s opinion is that the project planners, managers, and sponsors should enforce the idea that PIM data hub should create and manage a universal ID for items used by the entire “scoped” MDM PIM “hub and spoke” system. In other words, the PIM Item number should be the mapping equivalent to the same part in the other systems. The PIM item number might not be the number used in other systems but it should be the unique identifier for the item to map to and from the central product hub (Oracle PIM Data Hub).
Instead of discussing this as a decision “to be made”, the author of this post states that the project membership should discuss the decision “that has been made”. You will save time and come to the same manageable conclusion.
I am sure there are exceptions to this practice but I haven’t come across them while being exposed to many highly diverse industries using Oracle PIM Data Hub.
I have seen this discussing the decision “to be made” across the industries and they all have come back to the same “Centralized Universal ID” decision. Oracle has two distinct identifications for items in their application item master. One is the inventory item id. This numeric value is a pure sequenced number that is not typically seen by the application users. It is used in combination with an organization id to designate that the item is assigned to organizations with Oracle E-Business Suite (EBS). It is not practical to use this number for centralized universal id. The second is the system item key flexfield functionality from within the EBS. This is the place recommended to place the centralized universal id. This can be managed using Oracle PIM item numbering functionality to be very tailored to the organization’s needs. Oracle PIM and EBS will never allow duplicate item numbers. Oracle PIM gives you the ability to number your items upon creation and by different methods selected based on organization’s needs and predefined methods.
This post is to strongly recommend that you make the decision to create a centralized universal id for Oracle items that are synchronized across the enterprise in an MDM initiative before you start the project. Have the decision made when you start the software implementation.
One question I frequently get asked: What if another system creates an item and then sends it to Oracle PIM? How will Oracle PIM create the item number if the item already exists? Answer: Don’t let the originating system establish the universal id. If it is technically possible, obtain the ID from Oracle PIM before creating the item in the starting system. If not, then map the id in the originating system via an attribute or a cross reference to the created item in Oracle PIM.
Business needs and technical feasibility has been proven over and over to be satisfied easier with this recommendation.