In early February, Oracle did a controlled release of the .330 patch of DRM, and in March released it to the masses: Data Relationship Management Suite. The Suite is comprised of classic Data Relationship Management (DRM), Data Relationship Governance (DRG workflow module), and a new module called DRM Analytics.
My understanding is that you will have to download an Analytics zip file (from Oracle) to the server where Oracle EPM Foundation Server is installed and configure it with WebLogic and point it to the DRM database. It will then collect new change data on the versions and hierarchies going forward from install.
DRM Analytics is a Simplified Interface module that looks to the transactions in the DRM database and provides a reporting interface on the changes that take place for Master Data. It’s a new module that was released in the .330 patch for DRM, which is the DRM Suite.
DRM Analytics Dashboards
Change Management Dashboard
Graphical interface to view the changes to Master Data over time – adds, updates, moves, and deletes by hierarchy or node type; allows you to have insight into the changes and trends. You can actually drill back into DRM hierarchies from some screens.
Helps answer questions like “How much growth are we seeing in our account hierarchy over the last 3 months?” or “How many cost center moves have taken place in the last year?”
Growth Analysis Dashboard
How have your versions or hierarchies changed over time? This helps count and quantify the changes in versions.
Request Monitoring Dashboard
This allows you to qualify if your DRG workflows are effective, or need some improvement.
Model Analysis Dashboard
This dashboard allows you to research workflow design by the performance of the requests that are completed – like cycle time, automation, number of requests, and participant engagement in the workflows. This also allows you to drill back into actual DRG requests.
This is going to be useful to understand the workflow models themselves, and whether or not you have very effective (or ineffective) DRG users. Maybe you will have to re-assign some licensing after you look through this dashboard!
DRM Analytics Reports
The DRM Analytics reports give us something new we’ve never had before: security reports! Before DRM Analytics, an admin user would have to go through and take screenshots of the users and their roles to provide for audit purposes. Now these tasks are easy canned reports that can be monitored and shared.
- User Role Assignment Report
- Provides a list of users by role or roles by user with counts by licensed user types.
- Access Group Membership Report
- Provides a list of users by interactive and workflow user groups.
- Object Access Group Authorization Report
- Provides mapping of users and user groups to specific Data Relationship Management objects.
- Hierarchy Access Group Assignment Report
- Provides data grants of users and groups to nodes in a hierarchy.
- Workflow Access Group Assignment Report
- Provides data grants of users and groups to workflow model stages.
- User Login Activity Report
- Provides trend reports for user login activity over time.
- Metadata Object Usage Report
- Provides frequency distribution and aging information for Data Relationship Management objects: queries, compares, imports, exports, blenders, and books.
DRM & DRG New Features
Web Service Connections
Connections to PBCS and other web services (like upcoming Oracle cloud releases! FCCS…) are made easy with Web Service connections. SOAP and RESTful Web services are both supported. You can either use the Web Service connections to look up external data for external lookups, or commit data (like PBCS dimensionality) directly to the application. You’d configure these under the Administer menu > External Connections > and set the Connection Type to Web Service.
External Operations are comprised of External Lookups and External Commits. You can either use the Lookup feature in a Property Definition to find values using an external table source, or commit data to an external system via the Data Relationship Governance workflow tasks once they are committed.
Derive node property values and using lookups with real-time lookups to external tables or data repositories. If you want to derive a property values or have a dropdown list of values off of another table or Web Service, the External Lookups can be configured in the Property Definition. It’s in the same dropdown as Default, Lookup, and Derived (now a 4th option, External Lookup).
Immediately update a target system once a workflow model is committed. Execute SQL or stored procedures on a database to insert, update, or delete data. Invoke a SOAP or REST Web service to create, update, or delete data. This will leverage the Web Service Connections in the External Connections section of the Administer menu.
Dependent Workflow Tasks
You can now optionally configure dependent workflow tasks when adding new limb or leaf members in a workflow. This will result in additional request items for each dependent task; and can be created both manually or loading via a file.