Fusion Product Hub Training - Oracle · 2015-06-05 · •Rule 1 (Validation): For Green_Server items containing ZYour Initials in the Item Description, the Number of USB Ports Attribute

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |

Fusion Product Hub Training Data Governance: Business Rules and Impact Analysis

July 2014

Oracle Confidential – Internal/Restricted/Highly Restricted



Business Rules and Impact Analysis

Oracle Confidential – Internal/Restricted/Highly Restricted 4


Example Data Integrity Challenges

Unit Weight = 2Kg, Total Weight = 1Kg Length = 2m, Width = 2m, Height = 3m, Volume = 10m3

First Order Date = Jan 1, 2014, Last Order Date = Jan 1, 2013 Product Relationship: Substitute Product B (Status = Obsolete) for Product A (Status = Active) Product Dropped Shipped from Supplier is associated to Internal Warehouse Product Sold Exclusively in Stores is assigned to Web Catalog Category


• Validate product data at any point during consolidation, enrichment or publication

• Receive immediate remediation feedback

• Assess impact of new or modified

business rules prior to adoption

Enforce Data Integrity via Robust Business Rules Enrich Product Data While Consistently Applying Rules

Examples of Product Data Rules

• Lifecycle Phases: Products must have a ‘manufacturer’ attribute populated prior to being in a commercial phase

• Catalog Assignments: All ‘Web Enabled’ Products must be assigned to the ‘eCommerce Catalog’ • Internal Store Associations: Products that are drop shipped

cannot be assigned to internal stores

• Product Attributes: ‘Brand’ is a required attribute for all products

• Product Relationships: Products cannot have cross-sell or up-sell relationships with obsolete products or services


Rules Can: • Assign a value to an attribute

• Validate attribute value

• Generate Item Number and Descriptions

• Item Org and Item Category Assignments and Validations

• Enforce use of change order, and start CO creation

– attribute/attribute group changes

– Structure changes (by structure type)

• Validate Product Relationships

• Style/SKU Validations and Item Number/Description Rules

– Support for defining rules for SKU items referencing inherited attributes, Variant attributes and Style Item’s attributes;

– Ability to write SKU number/description Rules based on Style attributes such as Style Description

• Call External Java/SQL functions


Business Rule Impact Analysis

– Rule Sets can be authored in a Draft status and their impact analyzed prior to being made Active

– Graphical Summary shows Impact Analysis results broken down by various dimensions

– Data Stewards can initiate a mass update directly from the Analysis Results for a closed-loop remediation process

8


Hands-On: Business Rules and Impact Analysis



Hands-On: Business Use Case

• Scenario: A Retailer has a Data Governance Steering Committee that oversees data standards and policies for all enterprise product data. The Data Governance Steering Committee has introduced 2 new business rules for their product data targeted at items in the Green_Servers item class which the retailer sells on its website. The rules mandate that for all items in the Green_Servers item class:

1. The items must have a value for the ‘Number of USB Ports’ attribute 2. The items must be assigned to the ‘Servers – eCommerce’ Category in the eCommerce Catalog if they

are of Brand ‘Your Initials’ (The Brand in this example is provided in the Item Description).

• As a data steward working for this Retailer, you are responsible for authoring the business rules, analyzing their impact on existing items and phasing them in only after the appropriate assessment and remediation have taken place.


Hands-On: Outline • Section I: Create Items

• Create 6 Items with Item Numbers and Item Descriptions starting with ‘Your Initials’ • For 2 of the Items, provide a value for the Number of USB Ports attribute during item creation

• Section II: Define 2 Business Rules:

• Rule 1 (Validation): For Green_Server items containing ‘Your Initials’ in the Item Description, the Number of USB Ports Attribute must be populated

• Rule 2 (Assignment): For Green_Server items containing ‘Your Initials’ in the Item Description, they must automatically be assigned to the ‘Servers – eCommerce’ Category in the eCommerce Catalog

• Add the 2 Rule Sets to the Master Rule Set so they can be triggered

• Section III: Perform Impact Analysis and Mass Update

• Create an Analysis • Define the Scope for Your Analysis (The Scope is your 6 items) • Submit the Analysis • View Results broken down by multiple dimensions • Export the Catalog Assignment Rule results to Excel for off-line validation with the eCommerce team • Populate in excel the values for the Number of USB Ports attribute for the 4 items that have failed validation • Make both Rule Sets Active once the Impacts have been analyzed by the Data Governance Steering Committee and the eCommerce Team • Run the Analysis again after the Rule Sets are Active. Confirm there are no items violating the Validation Rule Set. Submit a Batch Process to

automatically assign the 6 existing items to the ‘Servers – eCommerce’ Category based on the Active Catalog Assignment Rule Set.



Safe Harbor Statement

The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 14

Documents

Fusion Product Hub Training - Oracle · 2015-06-05 · •Rule 1 (Validation): For Green_Server items containing ZYour Initials in the Item Description, the Number of USB Ports Attribute