Your search did not match any results.
We suggest you try the following to help find what you’re looking for:
Oracle Data Relationship Management (DRM) is an enterprise change management solution for building and retaining consistency within master data assets despite endless changes necessary to support underlying transactional and analytical systems.
As companies grow and evolve, it becomes essential to manage master data across information silos that result from mergers and acquisitions, departmental initiatives, or legacy system proliferation. Data consistency, integrity, quality and accuracy suffer and no one trusts the information and insight that ensues. Oracle DRM provides the industry's first data model-agnostic master data management solution built to enable financial and analytical master data management in dynamic, fast-changing business environments.
If you used Enterprise Performance Management Architect Release 220.127.116.11, you can migrate it to Data Relationship Management Release 11.2(PDF).
Create an enterprise view of financial chart of accounts, cost centers and legal entities with a view to govern on-going financial management and consolidation based on consistent definitions of financial and reporting structures across general ledger systems, financial consolidation, planning and budgeting systems.
Create an enterprise view of analytical dimensions, reporting structures, performance measures and their related attributes and hierarchies using Oracle DRM's data model-agnostic foundation. Construct departmental perspectives that bear referential integrity and consistency with master data constructs based on validations and business rules that enforce enterprise governance policies. Synchronize master data with downstream systems including BI/EPM systems, data warehouses and data marts to gain trustworthy insight.
Through data governance, organizations can exercise business process control and automation over the processes and methods used by their data custodians to handle change management and remediation of enterprise information assets such as master data, enterprise dimensions, hierarchies, relationships, associated attributes and mappings. Oracle Data Relationship Governance (DRG) is a fully configurable, collaborative business application that automates change request approval and data remediation workflows between front-line business users, subject matter experts, signing authorities and data stewards using automated, repeatable business processes to enable data quality, policy compliance, user collaboration, and change awareness across the business community.
Planning & Budgeting Integration: Packaged integration with Oracle Planning & Budgeting Cloud Service and Oracle Hyperion Planning Classic to enable dimension mastering, sharing and synchronization with Data Relationship Management.
Import Enhancements: Automatically create hierarchies from orphans to simplify the import of single section source files. Specify node types and validations in import profiles to assign them to hierarchies upon import. Load multi-line property values and perform reverse-lookups on property values during import.
Substitution Parameters: Pass run-time values to import and export processes to allow reuse of import and export profiles for different sets of data.
Hierarchy Group for Exports: Use hierarchy groups to control which hierarchies get exported instead of selecting individual hierarchies for each export profile.
Architecture Improvements: Application server architecture has been optimized for 64-bit, multi-processor machines to improve concurrency of read operations such as governance requests and exports.
Product Accessibility: Data Relationship Management Web client is compliant with WCAG 2.0 and Section 508 accessibility requirements. Keyboard support and screen reader support is included.
Conditional Workflow: Enables the introduction or exclusion of particular workflow stages depending on whether request items have certain property values or if they fail certain validations. Use conditional stages to split request items that require different approvers or separate enrichment tasks into new requests to follow separate workflow paths.
Separation of Duties: Enforces the ‘four eyes principle’ by requiring a separate approving user who has neither submitted nor approved any other stage in the same request.
Load Request Items from File: To accelerate the pace for creating multi-item requests in the Web Client or to automate the submission of governance requests using the Batch Client.
File Attachments: May be added to a workflow request to justify change or explain an action taken. Attachments can be viewed and downloaded by request participants.
Workflow Task Enhancements: Configure a hierarchy group filter to limit request items using a particular task to specific hierarchies and define instructions for individual task properties.
Request Details for Transactions: Transaction history provides request details for audit purposes including the users responsible for making changes in a request and committing the changes to the target version.
Data Relationship Governance for EPM Mobile: Use the Oracle EPM Mobile application to review and approve workflow requests generated within Oracle Data Relationship Governance.
Import from Database Tables: External connections to relational databases can be used to import data from database tables into Data Relationship Management. An import profile can source data from tables in a single database. Each section of an import profile can be mapped to a single database table. A query filter can be configured to import a subset of data from the source database tables.
Object Access Groups: Object access groups enable metadata objects to be organized, accessed, and managed collectively by a custom group of users. The previously available object access levels (User, Standard, and System) are now available as core object access groups. Custom object access groups can be created and provisioned by access managers. Users can be assigned Run or Manage permission to each custom object access group.
Hierarchy Constraints for Node Properties: Hierarchy constraints can limit the hierarchies and nodes available for viewing and selection when updating a node data type property value. A hierarchy constraint is an optional configuration for property definitions that use a node data type. The hierarchy constraint feature uses hierarchy groups and hierarchy group properties, which must be configured before you can assign hierarchy constraints.
Job Management: Job management enables greater control and visibility over long running operations (jobs) and the results they produce. Running an operation as a job enables users to perform a different task while the process is running and have access to the status and any results of the operation when they return.
Localized Documentation: To support globalization requirements for international organizations, the Data Relationship Management users guide, implementation guide and installation guide for this release have been translated into Simplified Chinese, Japanese, Korean, French and German.
New Product in 18.104.22.168: Fully configurable governance workflow oriented business application targeted at front-line business users. Shares metadata with Oracle Data Relationship Management and extends it through the configuration of workflow models, stages, and tasks. Configurable and extensible by DRM administrators. Native workflow engine, only requires DRM as pre-requisite.
Workflow Models: Used to control user tasks, stages of workflow, and types of data involved to govern a set of changes to data in Oracle Data Relationship Management.
Workflow Requests: Used to initiate changes or corrections to be completed, approved, enriched, and committed by other users using governance workflows.
Governance Work List: A central location for interacting with change and remediation requests. From the work list, governance users may submit change requests or review and participate in requests assigned to their user group.
Alerts and notifications: Provides Data Relationship Management alerts and email notifications to governance users and data managers for requests to which they are associated. The configuration of stages for the workflow model for a request controls whether users are notified of activities taking place in a particular stage and which users get notified.
Policy Management: High level enterprise data policies articulated by data governance committees may be broken down into business rules, data validations, and data access privilege assignments. Metadata artifacts familiar to Oracle Data Relationship Management administrators may be reused or extended to enforce governance against these data policies as business users request and respond to changes executed as governance workflows.
Workflow Automation: Workflow automation is dynamic, data-driven and exception-based. Requests are routed dynamically from one stage to the next based upon how both the data requested as well as how access to it is configured. Requests are routed dynamically based upon request items, workflow data access groups, and user privilege assignments associated with a given workflow model.
The Oracle by Example series provides step-by-step instructions on how to perform a variety of tasks. Because the step-by-step solutions are built for practical real world situations, not only is knowledge gained through valuable hands-on experience, but also the solutions presented may then be used as the foundation for production implementation, dramatically reducing time to deployment.