fusion product hub training - oracle · 2015-06-05 · fusion product hub training data enrichment...

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

Fusion Product Hub Training Data Enrichment and Maintenance

July 2014

Oracle Confidential – Internal/Restricted/Highly Restricted


Agenda • Item Creation with Data Quality

• Enterprise Product Data Model

– Specifications

– Structures/Packs

– Attachments

– Associations

– Relationships

– Categories

• Style/SKU


Item Creation with Data Quality Pervasive Data Quality Across All Modes of Data Entry

Oracle Confidential – Internal/Restricted/Highly Restricted 5


The Data Quality Challenge

2. Non-standard, inconsistent, misspelt or poorly formatted descriptions

3. Duplicate products

1. Misclassified or mis-categorized products

Manufacturer Description Product Category

Size Storage Capacity

A.A. Digital Photo Frame, 10GB, HP Black12 In Digital Camera

12 In 10 GB

AA Inc. digital photo frame 16:9 Kodak Black 10 IN 8 GB

Digital Camera

10 IN 8

A.A. 16:9 Kodak Black digital photo frame 10 inches 8 gB

Digital Camera

10 inches

8 gB


Embedded Enterprise Data Quality for Product Data • Semantic Recognition

Input: Poor Quality Product Data from Suppliers or Internal Systems

• Pervasive across all points of data entry • Business User UI • Real-Time

• Non-Classified • Non-Standardized

• Misspelt • Abbreviated • Misformatted

• Potential Duplicate

• Classified

• Auto-Classified in appropriate Product Class

• Auto-Categorized in Alternate Catalogs

• Standardized

• Standardized Product Description

• Auto-populated attributes with standardized values

• Generated standardized short, medium, long descriptions

• De-Duplicated

• Identified and remediated matches and/or duplicates

Import Cleanse Receive

Review and

Import


Centralize Management of Enterprise Product Data

People who can view and edit product data

Sales bundles and configurations

Cross-sell, up-sell, warranty, and other seeded and user defined product relationships

Categorizations in eCommerce, Print, UNSPC, Merchandising, Financial Reporting and other alternate hierarchies

Associations to internal stores, suppliers, target markets and channels

Digital assets including images, videos, user manuals and other unstructured data

Extensible and Scalable Enterprise Product Data Model

Unlimited number of product attributes

Business user defined attributes to model marketing attributes, product features, design specifications, etc

Seeded attributes for the operational needs of the enterprise (Sales and Order Management, Planning, Inventory…)


User Defined Attribute 1

User Defined Attribute 2

Attribute N

Trans. Attribute 1

Trans. Attribute 2

Trans. Attribute 3

Item Class/Taxonomy

Extensible Attributes

• Define to meet enterprise needs

– Form / fit / function

– Sales and Marketing

• Create as many as required

• Support Multiple Types of Attributes:

• ERP Operational Attributes

• Transaction Attributes

• Support multiple data formats (e.g.,

number, date, string, multi-row)

• Tie to business rules

• Add easily via intuitive UI

for business process administrators

ERP Operational

Attributes

Base product attributes for

inventory, planning,

distribution, etc.

Extensible Class Attributes Add User-Defined Attributes to Capture All Product Information

Transaction

Attributes

Used to capture transaction

specific product information

used at time of sale


*Bill of Materials

Integrated BOM* Management Centralize Product Structures from Multiple Systems

Integrated BOM

Repository

Engr BOM

Sales BOM

Multiple Design Systems

Sales Configurations

Global Mfg Plants

Service Organizations

Mfg BOM

Service BOM

• Integrate product structures from all systems in one central place

• Manage complex attributes and documents associated to product structures

• Support collaboration on product configurations with extended product team

• Single place to manage changes to all the product configurations


Pack Hierarchies • Manage item packaging information to facilitate order

and inventory tracking

• Create homogeneous and heterogeneous packs configurations

• Create top-down/bottom-up packs in a single user interface

• Create multiple packs for SKUs of a style item and for multiple standard items in a single flow

• Assign packs to organizations to facilitate transactions

• Roll-up quantity, weight, volume, length, and height information for items within a pack

• Pack Type (Trade Item Unit Descriptor) validations (e.g. EA cannot be a higher level pack item than CASE)

Pallet: GTIN = 30001234001031

Case: GTIN = 20001234001034

Pack: GTIN = 10001234001037

Each: GTIN = 00001234001030


Digital Assets (Attachments)

– Define Item attachments based on the business requirements.

– Text, URL, file from Desktop or a file from a Server can be uploaded to Item Attachments.

– Enabled basic Document management capabilities –Check in/Check out.

– Define Attachments at Master Org level and Child Org levels

– Associate Multiple Images to an Item

– Advanced Image Visualization (Zoom, Pan)

– Onboard Digital Assets via Product Hub Portal, Excel, CSV

12

Spreadsheets

PDF documents

(data sheets)

Word documents

Images, Videos,

CAD drawings


Associations

Examples:

• Control Availability of Product by Store, Channel, Target Market

• Maintain Order Lead Time by Supplier

Store 1 Store 2

Supplier 1: Address

Supplier 2: Address

Item

Item Organization & Item Supplier Address

Item Associations

Store 1 Store 2

Master Org

• Organization association allows contextual maintenance of product data enabling customers to control the visibility of an item in various internal or external organizations. For example, certain items may not be assembled, sold or purchased in a specific organization.

• Similarly customers can control specific attributes at organization levels. For example, an item can be sold in a specific organization (region) but not permitted to be sold in other regions.

Organization Associations

• Enables association of an item of a given organization to a supplier address. It indicates that for a given organization, the item is being supplied from the specific supplier address.

• Attributes can be maintained in the context of a specific Item Supplier Site (Address). During setup, the context usage of the relevant attribute groups must be defined as Item Supplier. (Other business contexts are Item and Item Revision)

• Item Organization and Item Supplier level attributes participate in Item Business Rules to ensure data integrity..

Supplier Address Associations


Item Relationships

Related

Items:

PIM Global ID: 128012

System 1: 340934

System 2: 45094

Source

System Item

X-Ref:

Maintain relationship between internal items • Cross-Sell • Up-Sell • Substitute • Warranty, etc

Related Items (Internal Items)

Maintain relationship between internal items and trading partner items • Customer • Competitor • Manufacturer • Supplier

Trading Partner Items

GTINs Maintain a formal cross-reference between an item and a Global Trade Item Number (GTIN) • Internal GTINs • Trading Partner GTINs

Cross-References

Maintain relationship between internal items and any other item identifier • Legacy Item Numbers • Service Catalog Numbers

Source System Items

Maintain relationship between internal items and Spoke System Items for Data Consolidation System 1: 340934 System 2: 45094


MPN 1: 23455

MPN2 : 67504

MPN:


GTIN: 00803857802342 GTIN


Legacy No: 34252 Cross-

Reference



Cross-Sell

Item to Item Relationships

Alternate Identifiers


Categories Allow Multiple Alternate Categorizations for a Product

By Department By Gender By Season By End-Use

Categorizations

T-Shirt

Clothing, Shoes and Jewelry Clothing &

Accessories Shoes

Women’s Tops Dresses

Men’s Kids

Summer Catalog Swimsuit T-Shirts

Spring Clearance

Professional Tops Skirts Pants

Eveningwear Bridal Maternity


Style/SKU Product Maintenance for Style/SKU Items



Product Range and Variations Add Data Complexity Just Two Attribute Variations Cause Significant SKU Proliferation

Variant Attributes Attribute 1: Color • Black • White • Red

Attribute 2: Size • S • M • L • XL • XXL

Product A: Women’s T-Shirt

Product SKUs • Black, S • Black, M • Black, L • Black, XL • Black, XXL • White, S • White, M • White, L • White, XL • White, XXL • Red, S • Red, M • Red, L • Red, XL • Red, XXL

Usually 1000s of product styles Usually 10s of Variant Attributes and Values Usually 100,000s or Millions of SKUs

1 Product Style 2 Variant Attributes • 3 Values for Color • 5 Values for Size

15 Unique Product SKUs

• Variability Across Geographical Locations, Stores, and Channels Adds to Complexity


Product Data Maintenance

• Define Product Styles and easily create multiple product variations (SKUs)

• Convert standard items to SKUs (product variations) of a Style Item

• Simplify product maintenance by defaulting/inheriting attribute values from a Style Item to Individual SKUs

• Maintain contextual product data that varies by organization, store, channel and target market

• Manage supplier associations and supplier level Attributes • Manage digital asset associations to products • Manage cross-sell/up-sell/accessory/warranty and other

product relationships • Manage Full Looks • Orchestrate new item introduction and ongoing changes via

governance workflows


Group Product Variations Under a Style Item

Multiple Product Variations (SKUs)

Style Item


Streamline Variant SKU Creation for a Style Item Select a Style Item (Product Grouping)

Select Desired Variations for Automatic SKU Creation

Review Automatically Generated SKUs with Real-Time feedback on any duplicate variant combinations

Enrich data for multiple SKUs in the same UI


Convert Standard Items to Variants of a Style Item Meet the Evolving Demands of Your Business

• Convert standard items to variant SKUs of a Style Item

• View a summary of existing SKUs while converting a standard item to a new variant SKU

• Enrich SKU data for a new variant in the same UI during conversion


Simplify Product Maintenance By Defaulting/Inheriting Attribute Values from Style Item to SKUs

Style Item

SKU 1 SKU 2

• Simple configuration to default or inherit attribute values from the Style Item to individual SKUs

• Optionally control attribute value maintenance at SKU level

• Define policy for each attribute group for maximum flexibility


Catalog Management



Catalog Maintenance

n

Clothing, Shoes & Jewelry Clothing & Accessories

Women Tops & Tees

n

Blouses & Button-Down Shirts

Knits & Tees

Dresses

n

Special Occasion

Night Out & Cocktails

Men Tops & Tees

n

T-Shirts Polos

Suits & Sport Coats

Sports Coats & Blazers Suits

n n

n

n

n

• Categorize products in multiple product categories • Maintain product catalogs for specific channels, locations,

trading partners, business operations • Define catalogs with flexible number of categories and

hierarchy depth • Auto-categorize products based on product attributes,

primary product taxonomy or other product categorizations • Maintain master and child catalog relationships • Empower business users to drive categorization options


Categorize products in Multiple Category Hierarchies Department Hierarchy

UNSPSC

Product Reporting

Web Hierarchy


Auto-Categorize Products Based on Different Criteria

Product SKU

1 Based on Product Attributes

2 Based on Primary Taxonomy

3 Based on Alternate Categorizations

Product Categories


Define Master and Child Catalogs – E.g. Seasonal Catalogs Direct vs. Reference Sharing

Child Catalog (Seasonal Catalog)

Reference Sharing

Direct Sharing

• Enforce governance and enhance productivity by maintaining products in the Master Catalog and propagating to Child Catalogs

• Visual Indicator is provided for referenced categories

• Categories referenced from the Master Catalog are not editable in Child Catalogs

• Localize maintenance and provide flexibility by adding/removing products directly in child catalogs

• Categories added directly to Child Catalogs are editable in Child Catalogs

Direct Sharing

Reference Sharing Master Catalog


Empower Business Users for Catalog Definitions Eliminate IT Reliance for Your Catalog Needs

Specify Catalog Name and Description

Specify Start and End Dates for Catalogs (E.g. Seasonal Catalogs)

Share Items and Categories from a Master/Source Catalog

Enforce Item Category Assignments at Leaf Nodes only or at All Levels

Enable Multi-Level Hierarchy and Option to Assign Items in Multiple Nodes in the Hierarchy

Control Catalogs at a Global Level or Individual Organizations


Streamline Catalog Definition and Maintenance Build Catalog Hierarchy and Assign Products in the Same UI

Build Catalog Hierarchy in the UI or Import from Spreadsheet

Mass Assign Products to a Category Node

View Products in a Specific Organization or Across All Organizations

Get Contextual Summary for a Product and Navigate to Product Details from the Same UI

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

Create Catalogs • Catalog Content

– Defines what content can be added to the catalog

– Values: Items at leaf levels, Categories only and Items at all levels

• Sharing Content

– Defines what content can be shared into the catalog from the Source Catalog

– Values: Items only, categories only, Items and categories

• Source Catalog

– Designates the catalog that the content can be shared

– Same Source catalog can be used with multiple catalogs

• Category Content

– Defines what content can be associated with a category

– Values: Items only, categories only, Items and categories


Catalog Content

C13

C131 C132

C11

C112 C113

Item C112

Note: If Enable Hierarchy Flag is True, then category to category association is allowed

C11

C112 C113

Item C112

Item C11

Category Only

Items at leaf level

Items at all level


Category Content

Note: If Enable Hierarchy Flag is True, then category to category association is allowed

C11

C111

C12

Item C121 Item C122

C12

Item C121 C111 C112

Items and categories

Categories only

Items only


Example: Catalog of Categories

Catalog A

A12 A13

A121 A111 A112 A113

A11

A131 A132

A1111 A1112 A211 A212

Enable Hierarchies for Catalog - Enabled

Catalog Content – Category only

Category Content – Category only


Example: Catalog With Items At Leaf Level Nodes

Catalog B

B12 B13 B11

Catalog Content –Items at leaf levels

Category Content –Items Only

B111 B112 B121 B122 B131 B132

Item B111 B1211 B1221 B1321 B1211

Item B211 Item B1321


Category Content – Category Only


Example: Catalog with Items at All Levels

Catalog C

C12 C13 C11

Category Content –Items and category

C112 C113

Item C112 C1111

Item C12 Item C11 C111

Catalog Content –Items at all levels


Category Content – Items only

Category Content – Category only


Direct Sharing vs Reference Sharing

Catalog A

Category C1

Category C3

Category C4

Item BSX7489

Catalog B

Category C5

Category C3

Category C6

Item WSX8499

Direct Sharing

Item SSX1367

Catalog A

Category C1

Category C3

Category C4

Item BSX7489

Reference Sharing Catalog B

Category C5

Category C6

Subcategory C3

Item BSX7489

Category C1

• Direct Sharing – Categories or category hierarchies from a

source catalog can be added to a catalog directly. The added categories can be edited in the new catalog (e.g. new categories added or items assigned).

• Reference Sharing – Categories or category hierarchies from a

source catalog can be added to a catalog as shared categories. The shared categories are references to the categories in the source catalog and can only be edited in the source catalog


What Can Be Shared Between Catalogs?

C12

Item C121 Item C122

C11

C111

C12

Item C121 C111 C112

Categories only

Items and categories

Items only


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.


fusion product hub training - oracle · 2015-06-05 · fusion product hub training data enrichment...

Documents