The following Patch Set Updates have been released Recently for Oracle Data Relationship Management 11.1.2.4.341.

• Patch 23236297 – PATCH SET UPDATE: ORACLE DATA RELATIONSHIP MANAGEMENT – 11.1.2.4.341
• Patch 23750023 – PATCH SET UPDATE: DATA RELATIONSHIP MANAGEMENT ANALYTICS – 11.1.2.4.341

Oracle Data Relationship Management Analytics is a capstone dashboard and reporting application that draws upon the transactions, requests and actions performed within the suite to provide change and growth analytics for end users, operational intelligence for governance program managers and subject matter experts, as well as operational reports for administrators and access managers to optimize transformation initiatives.

The new DRM Analytics module was a long-awaited tool for monitoring DRG requests, user security and activity.
Several dashboards are available for users:

• Change Management Dashboard – Aggregated views of changes that have occurred in the Data Relationship Management system over time
• Growth Analysis Dashboard – Provides analysis of how versions and hierarchies have changed over time
• Request Monitoring Dashboard – Displays KPIs relating to DRG requests
• Model Analysis Dashboard – Analysis of workflow model design: historical performance
• 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.

You know, Oracle Data Relationship Management (DRM) is a web-based user-friendly platform for users to manage enterprise dimensions.

The application provides many features such as SOX-compliant auditing, powerful and highly customizable business rule enforcement, versioning capabilities for storing historical views of dimensions, and multiple integration formats.

Within DRM , DRG adds configurable, collaborative workflow to help automate master data change management.

Oracle Data Relationship Governance provides the change management and data quality remediation workflows essential for front-line business users, subject matter experts and signing
authorities.

Oracle Data Relationship Management delivers timely, accurate and consistent master data to drive ongoing operational execution, business intelligence and performance management.

Moreover , Oracle Enterprise Data Governance solutions ensure data quality, policy compliance, repeatable business processes, cross functional collaboration and change awareness throughout the enterprise.

DRG is a fully configurable, out-of-the-box governance workflow. It is very good alternative to BPEL and Third Party workflow tools.

• Native to DRM Platform
• Metadata aware
• Pure configuration, no coding
• Existing DRM Administration skills should suffice
• Lowest TCO
• Email notifications

Unique Features of DRG:

• Provides an easy to use tool to help manage requests and approvals for master data changes.
• Integrated workflow with DRM enhances existing DRM implementations and can re-use DRM (hierarchies, properties, validations, and security).
• Configurable tasks and workflows can be designed and deployed by business users.
• Workflows can be configured to handle simple or complex requests, multi-line items, various actions (Add, Update/Enrich, etc.).
• Email notifications and web interface provide information for tracking activity, history, and other audit needs.

Benefits – What’s in it for you?

• Provides workflow for DRM, enhancing any DRM implementation.
• Compliments any Data Governance Council, providing the tool to achieve master data alignment.
• No coding required: Business users can drive the process and have direct participation in building the solution.
• Flexible: Workflows can be adjusted or modified to suit the needs of the business.
• Fully Integrated: Avoid time consuming efforts to leverage DRM outside of the tool, DRG works with the existing features of DRM.
• Provides fully transparent activity trail compliance and audit, as well as email notifications.

The Core

DRG is a component within Oracle’s Data Relationship Management , act as a tool that allows DRM users to easily make changes to their data hierarchies.

It also allows users to communicate within the DRM system, which means users can view, request, and approve data changes all in the same place.

Those , who need more details, can understand DRG has four main focal points:

1. User Roles
2. Access Levels
3. Workflow Tasks
4. Workflow Stages.

User Role

There are several DRG User Role Permissions that can be assigned to DRM users. The permission with the most freedom is the “Workflow Participant”. This permission allows users to Request and/or Approve changes to the data hierarchies. The next level down in the DRG permissions is “Browse Versions”, which allows DRM users to navigate through different versions within the DRM system, but doesn’t allow them to request and/or approve changes to the data structures. Finally, there are three more permission levels: “Browse Hierarchies”, “Browse Categories”, and “Browse Properties”. These three permissions are the lowest level of permissions and there names describe what the user is able to navigate through.

Access Level:

In Data Relationship Governance, there are six different Access Levels that users can be given. All of these access levels build on each other, so, for example, level 3 includes all of the access rights that level 1 and 2 have. Level 6 has all of the access rights that levels 1 through 5 have. The six Access Levels in DRG are: Read, Limited Insert, Edit, Insert, Inactivate, and Add. Read access only allows users to view the data. Any user with this Access Level cannot make any changes. Limited Insert is allowed to insert a node, but only if that node has Global Properties. The Edit access level allows users to modify property values. The Insert access level grants users the ability to insert, move, and remove nodes. Inactivate allows users to deactivate and reactivate nodes. Lastly, the Add access level allows users to do all of the previous tasks, plus add or delete nodes.

Workflow Tasks

A workflow task represents a change action to be performed along with a set of properties to be displayed, edited, and required during the task.

Workflow tasks are defined outside of workflow models and can be used by multiple models to ensure consistency of common tasks performed in different business processes

Workflow Tasks are made up of an action type, properties that need to be reviewed, and validations.

There are eight different Action Types a Workflow Task can use: Add Leaf, Add Limb, Delete, Inactivate, Insert, Move, Remove, and Update.

These Action Types are self-explanatory and they are named for exactly the action that they perform.

Workflow Tasks must be created in the Administer tab within DRM before any user can Request and/or Approve any data changes.

Workflow Stages

A workflow model consists of multiple workflow stages. When a stage is defined for a workflow model, the stage type defines the level of participation for users in that stage of the workflow. A workflow model has:

• A single Submit stage which is defined by a list of allowable workflow tasks that can be used to submit changes
• An optional series of Approval or Enrichment stages, each consisting of a single workflow task
• A single Commit stage used for final approval and commitment of all workflow tasks performed

There are four stages in total, but only three of them are required.

The Workflow stages include: Submit, Enrich, Approve, and Commit.

The Submit stage is where the requests for any sort of data change take place. All of the Action Types are associated with this stage except for the Update action.

The Enrich stage is used to update requests that have already been submitted. This is the stage that is not always necessary to be included, and includes the Update, Insert, and Move Action Types.

The third stage is the Approve stage, which is where all requests are viewed and managed. The Update Action Type is also a part of this Workflow Stage, which is why the Enrich Workflow Stage does not always need to be included.

Finally, the Commit stage is where requests are approved or rejected. Only a user with the access to approve a request may view the Commit stage.

These four components of Data Relationship Governance, User Roles, Access Levels, Workflow Tasks, and Workflow Stages, are what make DRG so useful in DRM.

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.

The Oracle Data Relationship Management (DRM) Suite is an integrated solution that helps enterprises master, govern and analyze enterprise dimensions, hierarchies and related attributes to enable effective business transformations by rationalizing key information assets across transactional and analytical silos, automating change management and data quality remediation processes, and providing a closed loop operational analysis, reporting and drill back experience that optimizes one’s data governance program to lower risk, enable trustworthy analytics and improve one’s confidence in data-driven decision making.

The Oracle Data Relationship Management Suite consists of three key components:

1. Oracle Data Relationship Management is an enterprise master data change management solution for building and retaining consistency within master data assets despite endless changes necessary to support underlying transactional and analytical systems.
2. Oracle Data Relationship Governance (DRG) is a companion application that leverages the DRM platform to deliver fully configurable, automated governance workflows, that enable data stewards to orchestrate the entry, validation, and approval of data changes by front-line business users using repeatable business processes, thereby enabling high-quality master data, policy compliance, collaborative co-authoring, and change awareness across the business community.
3. Oracle Data Relationship Management Analytics aka DRM’s Analytics module is a capstone dashboard and reporting application that draws upon the transactions, requests and actions performed within the suite to provide change and growth analytics for end users, operational intelligence for governance program managers and subject matter experts, as well as operational reports for administrators and access managers to optimize transformation initiatives.

DRM is a master data management tool used to administer hierarchies, attributes, and metadata used by various types of applications.

The DRM tool can act as a centralized enterprise hierarchy management solution serving a wide range of downstream BI, EPM, ERP, operational, and other systems.

Common applications of the DRM tool include management of GL chart of accounts,customer and employee attributes, and product information .

Oracle Hyperion Data Relationship Management (DRM), Fusion Edition functions as a master data management solution where reporting structures are maintained, analyzed, and validated before moving throughout the enterprise. Data Relationship Management does the following:

• Manages business entities, hierarchies, attributes, and mappings across multiple systems.
• Validates data relationships and calculates attribute values using business rules.
• Enforces referential integrity across all subscribing systems and hierarchies.
• Enables you to create and manage alternate views.
• Merges independent data sets from different sources and combines them into a master set.
• Maintains historical versions for comparative reporting and analysis.
• Tracks all hierarchy and attribute changes with a full-featured audit log.
• Can serve as the main point-of-entry to update subscribing systems or be used subsequently for reconciliation and analysis.

You can use Data Relationship Management to manage charts of accounts segment values and hierarchies for Oracle General Ledger.

You can create new segment values, edit their properties, and maintain hierarchies using DRM. This information can be synchronized to one or more general ledger instances using a concurrent request program in the Oracle E-Business Suite.

DRM can integrate with other systems, Oracle or non-Oracle systems. The simplest way to let flow the data in between systems is by Import/Export.

Export can be done to a flat file or a database table where as import can be done via flat file. Additionally, customization can be done through API to perform the same.

DRM is also an Analytical Master Data Management tool. It allows creation of an enterprise view of analytical dimensions, reporting structures, performance measures and their related attributes.

DRM can also be considered a change management tool, as it is often used to facilitate the combination of disparate General Ledgers, product mappings, customer data sets, and other business information.

Mergers and acquisitions are frequently reliant on DRM to enable different systems to be able to communicate with each other.

DRM enables organizational consistency, managed change and becomes the foundation for any technology project

Following is a list of Business Events provided by Oracle Product Hub:

Â

Â

Different types and structures of data exist within an organization. Here to go:

Master Data -Enterprise-level data entities that are of strategic value to an organization. These are typically non-volatile and non-transactional in nature. Typically example of such data are Customer, product, supplier, assets, System Name

Transaction Data-These are Business transactions that are captured during business operations and processes, such examples are PO, Invoices, PR , Payments etc .

Therefore, Data is intrinsically simple and can be divided into data that identifies and describes things, master data, and data that describes events, transaction data.

Reference Data- There are Internally managed or externally sourced facts to support an organization’s ability to effectively process transactions, manage master data, and provide decision support capabilities.

Typical example are as such :
States/Provinces/Territories
Cities within States/Provinces/Territories
Street names within cities
Street types (Dr, Lane, Boulevard…)
Street direction (N, NE, E, S…)
Blocks & Block Groups
Postal codes within states
Months of the year

Unstructured Data—This is data found in e-mail, white papers like this, magazine articles, corporate intranet portals, product specifications, marketing collateral, and PDF files.

Metadata -This is defined as “data about the data.” These data are Typically Used as an abstraction layer for standardized descriptions and operations.

Analytical Data -These data are derivations of the business operation and transaction data used to satisfy reporting and analytical needs. In the organziation such data typically reside in data warehouses, data marts, and other decision support applications.

Big Data -Data sets whose size is beyond the ability of commonly used software tools to capture, manage, and process the data within a tolerable elapsed time.

Big data typically refers to the following types of data:

• Traditional enterprise data includes customer information from CRM systems, transactional ERP data, web store transactions, general ledger data.
• Machine-generated /sensor data – includes Call Detail Records (“CDR”¨), weblogs, smart meters, manufacturing sensors, equipment logs (often referred to as digital exhaust), trading systems data.
• Social data includes customer feedback streams, micro-blogging sites like Twitter, social media platforms like Facebook

Customer Hub: Its all about knowing the Customer ! Agree or disagree ?

Did you encounter situation where you have to answer these question on company’s customers and prospects ..

• Which of our services they are using and what they are NOT using?
• What do we cross-sell and up-sell to our existing customer base?
• What product bundles do sales propose that will increase the sale?
• Are we able to identify who are our top revenue generating top 10 customers?
• Are we able to identify who are most likely to churn out?
• Can we identify all the orders that have placed and what are their statuses?
• Are we billing for all the services that we are providing?
• Are we able to manage contracts with them both at divisional as well as corporate level?

In order to answer, you need Need a 360 degree view of the customer

Oracle CDH vs. Oracle-Siebel UCM

Oracle actually sells two products on customer Data hubs –Oracle CDH and Siebel UCM (Which is now Oracle UCM). But these products are positioned differently in the markets .

Both these products revolve around mastering of the “Customer” entity.

Oracle CDH or “Customer Data Hub” is a member of the Oracle Fusion Middleware family of products and has built-in integration capabilities with other Oracle E-Biz suite modules.

Siebel UCM, is the Siebel Customer mastering solution.

Oracle CDH is mainly focused on manufacturing, hi-tech, Retail and Distribution industries whereas Siebel UCM is targeted for telecommunications, media, financial services and government.

Enterprises implementing customer Data Hubs should evaluate these two products and choose from these based on their requirement.

UCM (Universal Customer Master) release 8.0 has more capabilities than CDH in terms of Data extensibility model, Data quality features and its strong interfaces to various third party tools like Trillium etc [Reference www].

On the weaker side, Oracle CDH and UCM are lacking in terms of dash boarding, reporting facilities, data steward facilities through web, registry-style implementations.

if you need more information, take a deeper dive.

 

Customer Hub: Its all about knowing the Customer -> Siebel UCM What is Oracle Customer Data Hub (Oracle CDH)

Following is a list of Business Events provided by Oracle Product Hub:

[This blog post is contributed by Hub regular Visitor who worked almost 8 years in MDM and PDM area. You can reach them to author via email]

As we aware, Oracle Product Information Management Data Hub is an enterprise data management solution that enables customers to centralize and master all product information from heterogeneous systems, creating a single view of product information that can be leveraged across all functional departments.

Oracle Product Hub provides a full set of business services and data services, both at granular level and at business object level. These include Items creation/update, item change management process support, Items data gathering and data federation.Following is a list of APIs/Web Services provided by Oracle Product Hub , feel free to add in case if anything missed out.

[This blog post is contributed by Hub regular Visitor who worked almost 8 years in MDM and PDM area. You can reach them to author via email]

Oracle Product Information Management (PIM) Data Hub is an enterprise data management solution that enables customers to centralize all product information from heterogeneous systems,creating a single view of product information that can be leveraged across all functional departments.

Oracle Product Data Hub (PDH) module formerly known as Advanced Product Catalog has now become part of Oracle’s master data management suite of products.

Oracle Product Information Mgmt Solution consist of three major products as:

• Oracle PIM Data Hub
• Oracle PIM Data Librarian
• Oracle Product Data Synchronization for GDSN and UCCnet Services (PDS)

Oracle PIM Data Librarian is a web-based application that extends the functionality of the Oracle Inventory,Bill of Materials, Engineering, and Project Management modules.

Oracle PIM contains its own set of tables under the EGO (Engineering Online) schema, but still uses the standard Oracle Inventory, Bill of Materials, and Engineering tables.

• The item master in PIM is the same item master used by Oracle Inventory.
• User-defined product attributes and change management data are stored in the EGO
  tables.

Licensing requirement for Oracle PIM Data Hub gives customers the right to use PIM Data Librarian (which is licensed separately) on an instance other than the instance where the company has deployed the Oracle E-Business Suite. Licensing Oracle PIM Data Hub Add – On gives customers the right to use PIM Data Librarian (which is licensed separately) on the same instance where the company has deployed the Oracle E-Business Suite.

PIM Data Hub Benefits

With Oracle® Product Information Management Data Hub customers can

• Consolidate all product information
• Cleanse: Includes a data import workbench to manage source system mappings and data loads
• Excel based Imports and Exports: Spreadsheet import for easy upload and maintenance
• Bulk Imports: Optimized bulk import through staging tables
• Service Oriented Architecture: Integrate using prebuilt, standards compliant business services and adapters
• Import data and synchronize multiple systems.
• Workflow based Collaboration: Highly configurable change management workflows with approval routing
• Securely access and search your information repository
• From Governance and Compliance prospective they can automate with the help of workflow based processes that can perform rule based validation and data correction

Who needs PIM Data Hub?

• Those who need a 360 Degree secured view of the part attributes and transaction data
• Those whose item master have extensive item attributes
• Those who want synchronize product data from and to multiple systems
• Product information is scattered across desktops, legacy systems and custom applications. Need product data consolidation and cleansing.
• Need to manage New Part Introduction, Issues and Change Control processes efficiently via configurable robust workflow-driven processes
• Manage Data Governance and Compliance: Government and industry regulations such as RoHS, WEEE), and FDA Compliance (21 CFR Part 11)

[This blog post is contributed by Hub regular Visitor who worked almost 8 years in MDM and PDM area. You can reach them to author via email]