For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.
Ricardo Giampaoli and Rodrigo Radtke have recorded a 2 Minute Tech Tip video based on this article. Watch it here
Nice work, It will reduce the time of integration process.
This is an elegant solution to address a common problem for any application that is dependent on external metadata.
As you correctly point out, the burden is still on the external interfaces that populates the generic inbound metadata table.
Your solution isolates "the source system" dependent details to create a classic "source system agnostic" data architecture for metadata integration.
However, there is still the much larger issue of Data Governance with a large organization. Oracle-Hyperion DRM is a tool to help organizations
manage the source system dependent nature of metadata to create a "normalized" view of an organizations metadata. The solution you present here
is a nice complement to DRM, which you also point out is another potential "external" data source. EPMA and more recently FDMEE
have native integration with DRM (without the need to understand DRM's API or DRM's Data Structures). I for one, would love to see how your
solution paired with DRM, where DRM acts as the central enterprise repository the entire organizations metadata management needs. How
about a DRM to Hyperion Planning IKM !!!!!.