According to Oracle Support metalink note 1113543.1:
In previous versions: “Oracle Product Hub allows you to create Item Catalog Category (ICC), Attribute Groups and its corresponding attributes, Value Sets and the corresponding values through User Interfaces. ”
But in the current 12.1.3 version of the Product Information Management Data Hub PIMDH, Oracle writes:
“However, there is no provision to create them using Interface tables or Import Functionality. Now, you can import ICC, attribute groups, and values sets using interface tables.
A new concurrent program EGO Import Metadata(EGOIMDCP) has been introduced to import key metadata in Product Hub. Use open interface tables to import the following item catalog metadata:
- Item catalog categories (ICCs)
- ICC definition
- Attribute group association
- Item pages association
- Item number and description generation methods
- New item request association
- ICC versionsTransaction attributes
- Value sets
- Non-versioned value sets and values
- Value set versions and values
- Child value sets and values
- Attribute groups and attributes
- Function header
- Function parameters
Using the concurrent program EGO Import Metadata (EGOIMDCP), you can choose to validate and import the above data from the open interface tables into the production tables collectively or one at a time.”
What does this mean to me and you?
This means that we should be able to mimic other systems within a technically feasible means. Front end item creation systems duplicating the PIM Data Hub functionality could literally send their flavor of “Setup Workbench” configuration into the Oracle PIMDH instance. Your spoke system could continue to do its job but more readily share the information with other systems as it changes through the PIMDH. It still requires sql to build this interface into PIMDH and it still requires sending it to other systems as it changes in PIMDH instance. But, you won’t have to “secretly” develop a import of metadata with non supported API. And you shouldn’t have to do it manually twice after this metadata interface is built.