Oracle DRM Data Maps: Intro

Those familiar with Oracle Data Relationship Management (DRM) may be aware of its biggest value proposition – DRM centralizes the maintenance of metadata structures in one platform and supports the alignment of critical information assets across an enterprise.

Organizations that choose to adopt DRM, are interested in becoming more efficient in:

  • Handling routine metadata changes, (e.g. adding a new Cost Center or Account)
  • Enabling large change management events/projects (e.g. M&A-s, re-orgs, system upgrades)
  • Enforcing data quality and governance process controls

While the primary objective of most DRM implementations is to establish a controlled and efficient maintenance model for sending metadata to subscribing applications, more DRM customers are realizing the tool’s potential to support with the alignment and publication of data maps. Mappings in DRM can be implemented through the familiar context of hierarchies and properties.

Let’s dig into one use case scenario for a mapping property candidate for DRM maintenance. Assume an environment where data needs to be shared across an accounting application (Application A) and a FP&A (Application B). To perform its accounting functions, Application A must present the Account dimension elements down to the lowest level of transaction detail. To support FP&A functions, Application B presents the same Account dimension at a summarized level that is up to user discretion.

As information is shared across Applications A to B, mappings must exist to support the flow of information. Wouldn’t it be nice if mapping updates and metadata changes across these applications could be coordinated through the same change management process (and technology solution)? Here’s where DRM can help. A simple Associated Node type mapping property could be established on Application A’s hierarchy to store the mapping relationship of Application B (or vice versa).


In the example below, the ‘Accounting – FPA Map’ property has been created to track the relationship across two applications in question.


When new accounts are added to the DRM environment, the ‘Accounting – FPA Map’ stores the data mapping relationship. Referential integrity constraints allow updates based on only existing metadata structures of target applications, reducing the risk of user specification errors.

Finally, the relationship across hierarchies and properties can be viewed through the dimensionality of Application A or B.


Flexible export options make the consumption of mapping property information out of DRM simple to maintain. Stay tuned for the next blog post that will discuss use cases of mapping hierarchies implemented in DRM to handle multidimensional map scenarios.

By Julia Radovani, Senior Manager at Peloton Group

1 Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s