Microsoft PowerPoint - Product Hub - Presentation
Microsoft PowerPoint - Product Hub - Presentation
Microsoft PowerPoint - Product Hub - Presentation
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-2
Identifying Product Hub Capabilities
Product Hub enables you to store and manage product information and provides you the
capabilities to:
• Capture product form, fit, and function information with structures, user-defined attributes
and attachments
• Control business functions and operations using predefined industry standard
operational attributes
• Organize items into user-defined item classes, catalogs and categories
• Import product information using multiple file formats
• Publish product information in custom data sheets, collateral and reports
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-3
Product Hub and Product Hub Portal Cloud Service
Product Hub
Extended Style/SKU Item Class
Items & Revisions Attributes Hierarchy
Operational Attributes
Product Structures Product Rules/ Audit Trail
(BOMs)
Functional Catalogs
Analysis Product Model Publication
Import
Relationships/Trading Items & Revisions Framework
Partner
Workbench
Operational Attributes
Multiple Organizations Analytics
Product Structures
Attachments Import Maps Mass
(BOMs)
Functional Catalogs Browse Items Updates
Change Relationships/Trading
Management Packs Partner
GDSN
Multiple Organizations
Data Quality Infrastructure
Attachments
Advanced
New Item
Request
Source System Item Supplier Catalog
Product Hub Portal Workflow
and GTIN
Cross
Association
Reference
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-4
Enabling Data Governance Enforcement and Analytics
• Orchestrate collaborative product definition through a flexible workflow that meets your
organizational structure and business needs.
• Implement changes through a streamlined review and approval process.
• Enforce business and governance policies via rules and perform what-if analysis and
perform mass changes.
• Schedule product changes for a future date through Change Orders.
• Control view and edit privileges through role based and data level security.
• Monitor key product and governance related information with embedded product data
analytics.
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-5
Key Business Benefits of Product Hub
Product Hub:
• Serves as an enterprise-wide single source of truth
• Consolidates product information from multiple sources
• Provides high quality product information
• Governs product information by providing data governance
• Shares product information by publication, reporting
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-6
Enterprise-Wide Single Source of Truth
• Attributes
• Attachments
• Catalogs Consolidate Cleanse
• Relationships
• Trading Partners Product
Hub
• Organizations
• Product Classification Govern Share
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-7
Consolidating Product Data from Multiple Sources
Data Consolidation
• Spoke Systems
Product
• Import Maps Hub
• Data Pools
Govern Share
• Web Services
• Suppliers
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-8
Data Cleansing
Data Cleansing
• Item Templates
Product
• Data Quality Hub
Standardization
Govern Share
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2-9
Data Governance
Data Governance
• New Item Requests
Product
• Change Orders Hub
Govern Share
Data Sharing
• Reporting
Product
• Web Services Hub
Govern Share
Firewall
File‐Based Upload Print Catalog Publication
Import Maps Rich catalogs and reports
Product Hub
Supports CSV and XML Staging Area using Adobe InDesign based
Base Tables
ETL Based DI templates
Supports CSV
Excel Based ADFDI BI Publisher and OTBI
Supports XLSM Data extraction and reporting
in multiple formats
Web services
Staging load services Web Services
Production load services System to system real‐time
publication of product
Data Quality information
Standardize, cleanse,
de‐duplicate
Validate import batch process
Items # Description
Item
Item Mass
Rules
Changes (UI Item
Based) Import
Catalogs
Item Batches
(Spreadsheet ,
CSV, XML)
To learn about Security for SCM, please refer to the recorded lesson titled, SCM Security
Overview, available at
http://oukc.oracle.com/static14/public/video_review_bc_streams_1280x720.html?id=540501
5013001.
Oracle Supply Chain Management Cloud documentation, available in the Oracle Help
Center
• Browse through the relevant Product Hub topics in the following guides:
– Using Product Development: https://docs.oracle.com/en/cloud/saas/supply-chain-
management/18c/faupd/using-product-development.pdf
– Using Product Master Data Management:
https://docs.oracle.com/en/cloud/saas/supply-chain-management/18c/fapim/using-
product-master-data-management.pdf
– Implementing Product Management: https://docs.oracle.com/en/cloud/saas/supply-
chain-management/18c/faipr/implementing-product-management.pdf
You can configure Product Hub to support multiple organizations with the following usages:
• Item organization:
– Maintains product information excluding transaction related information, for example,
Ordered Quantity, On-hand quantity
– Does not support inventory transaction tracking. It is associated to a physical location
and does not require any association as a legal entity.
• Inventory organization:
– Maintains product information including the transaction related information
– Tracks the inventory transactions using the Fusion Material and Logistics and
Procurements applications.
– Is associated with business units and legal entities
• Definition organization:
– A definition organization is an organization that stores the item attribute values.
– You can edit the attributes.
– You can define the definition organization on the Manage Inventory Organization
Parameters setup page.
• Reference organization:
– A reference organization is an item organization that references the item attribute
values from the definition organization.
– You only can reference the items attributes and not edit them.
– You can define the reference organization using the Item Grouping Behavior
attribute on the Manage Inventory Organization Parameters setup page.
Concept of
Definition Organization
• Item organizations:
– Can be arranged in a single level
master-child relationship
– Make item data maintenance easy
– Make item administration easy
• Units of Measure are created using the Manage Units of Measure task within the Define
Items task list.
• Because units of measure with similar characteristics are grouped together into UOM
Classes, you need to plan your units of measure.
• Item lifecycle phases are used as an indicator of the stage for an item within the lifecycle
process.
• Each item must have a lifecycle phase associated with it.
• Each item class has a list of lifecycle phases that are available for items.
• Item class is a way of grouping items that share common attributes , administrative and
governance needs. For example, an item class called Office Machines is defined to
classify all items that represent office machines ,such as , computers, printers, and
shredders.
• Item classes:
– Can be arranged in a multi-level tree hierarchy. For example, an item class called
Printers may have laser printers and 3D Printers as child item classes.
– Inherit all attributes and administrative controls from their immediate parent class.
For example, if Model No. and Pages per minute are attributes of Printer item class ,
then the child item classes (Laser printers , 3D printers) inherit those attributes as
well.
• Item classes:
– can have incremental attributes and administrative controls defined in addition to the
inherited ones from the parent item class.
• Root item class:
– Is a pre-defined item class provide by Product Hub. Users can add attributes and
controls depending on the Fusion Product (Product Model or Product Hub) they are
licensed to use.
– Is the top node in the item class hierarchy
y
• Gather the unique types of specifications
required for each type of classification.
Resistors Capacitors
Part # Part #
____ ____Inherited
Manufacturer Manufacturer
____ ____Attributes
Price Price
____ ____
Attribute N Attribute N
____ ____
Ohms Microfarads
____ ____
The following actions can be assigned to a user or group for a given organization:
Extensible User-defined attributes that need Item: Specifications tab. Each page
Flexfields require organization, possibly into is listed as a link
categories or hierarchies
Use extensible attribute group security to secure the data of attribute groups by allowing
only certain groups or users to have access.
Create and apply extensible flexfield security as follows:
1. In Security Console, create the data grant for the user or role.
2. In the Manage Item Attribute Groups and Attribute page, assign the data grants to the
attribute group.
3. Assign data grants to specific groups or users.
• When adding an existing or new attribute group to an item class or item class hierarchy.
• When removing an attribute group assignment to an item class or item class hierarchy.
• When adding a new item class to an item class hierarchy where attribute groups are
inherited from parent item class.
• Item
• Item
Attribute
• Formatted
Description
• Item
Revision
• Item relationships
• Item associations
When you create, copy, or change a structure, the following key validation rules are applied:
You cannot add:
• A component to a structure where the component item is the same as the parent.
• A component to a structure where the same component, with the same effective date
range already exists on the structure.
• A component to a structure that is being referenced as a common structure from another
organization, where the component does not exist in the other organization.
• An item may be transacted by itself (Ex: Soda can as single unit) or in a “pack” of
multiple units (Ex: A case of 18 soda cans or a box of soda cans where each box is
made up of 24 cases).
• For transaction purposes, each level of the pack is represented as an item differentiated
by the Pack Type attribute.
• The pack hierarchy is modeled as a special type of structure that captures the
composition of the pack.
• You need to create a pack structure to define the hierarchy of the pack items.
• Each level of the hierarchy specifies the quantity of the lower level of the pack items
contained it.
Pallet
Case
Item attributes can be rolled up from base items to higher pack items. This enables you to
calculate the dimensions of higher pack items from lower pack items.
The attributes for which rollups are performed are:
• Quantity
• Weight
• Catalogs:
– Provide a mechanism to identify a collection of items that share a business purpose
– Contain categories. Categories can be organized in a single level catalog or in
hierarchy in the catalog.
— For example, an E-commerce catalog may be made up of multiple categories,
such as Office Products and Gloves. While the Office Products may include
desktop and printers, the Gloves category may include various types of gloves.
• Categories:
– The items are assigned to categories in a catalog.
– For example, items representing printer products can be assigned to the printer
category in a catalog.
• Item category assignment: Represents the relationship between a category and an item.
• Reference category: A category that is shared as a reference category from a source
catalog.
• Leaf-level category: The lowest level category in a hierarchy.
• Browsing category: Categories that you add to the category hierarchy for the purpose of
classification and do not have items assigned to them.
• Category hierarchy: The organization of categories using a parent category that has one
or more child categories. Catalog can also have a single level organization.
• You can:
– Manage catalogs easily using the simple or complex category organization. Product
Hub provides user-defined catalog and category codes that simplify the creation of
catalogs.
– Enable category sharing from multiple catalogs by referencing content from other
catalogs or copying content from other catalogs.
– Implement data-level security for catalogs and categories
– Search for catalogs efficiently using the Autosuggest functionalities
– Publish catalog reports to share catalog information.
– Use social networking to share and comment on catalog and category content.
– Track and audit changes to an item catalog by automatically recording the changes
made along with the details of who made the changes and when.
• Public Catalog: The content in the catalog can be viewed and edited by all users and
groups.
• Private Catalog: Access to the content in the catalog is determined by data grants that
allow the catalog to viewed, viewed and maintained and administered.
• Public catalogs are catalogs which all users and groups can access. The user have full
view and maintain rights to the catalog and categories.
• Private catalogs are catalog that have access restricted to a set of user or group. Only
the users or groups that are granted access to the catalog and categories have view,
maintain or administer rights to the catalog and categories.
• Grants are used to provide access to catalogs or categories by specifying which users or
groups have which privileges.
• The privileges are:
– View – user can view the content in read only format
– Maintain – user can edit the content, user must have view privilege as well.
– Administer – user can grant other user or groups access
• Data security enablement is controlled with the Public check box in the user interface.
– When the checkbox is checked, the catalog and its content is public
– When the checkbox is unchecked, the catalog and content is private.
• Data security can be enabled for catalogs during the following processes:
– Catalog Creation
— The catalog and any content added to the catalog will have data security enabled. The
catalog level data security grants will be inherited by all new categories.
– Editing a Catalog
— The catalog and its content will have data security enabled. The grants for the owner will
be inherited by all categories in the catalog.
• When a catalog data security is enabled, the user that is logged in will become the
owner to the catalog and categories within the catalog.
• The owner will have View, Maintain and Administer privileges.
• If the catalog has existing categories the owner data grant will be inherited by all
categories in the catalog. The owner data grant will be read only at all categories in the
catalog.
• A person or group with Administer privilege can add grants for additional user or group
for the catalog and/or any category in the catalog.
• Data grants added at parent category level in an hierarchy will be inherited by any child
categories in the catalog and will be read only at the child category level.
• Data grants can be added at the catalog or category level.
MB7 Second bullet- This content was previously in the next slide. I have moved it here as the second bullet.
Meenal Bhardwaj, 9/18/2018
Product Changes Across the Enterprise
Supply Supply
Sales Marketing Chain
Regulatory Chain
Attributes Attributes Attributes
Attributes Attributes
Step 1: Sales Step 2: Marketing Step 3: Regulatory Step 4: Supply Chain Step 5: Review & Approve
A change order:
• Orchestrates item attribute data changes across the enterprise
• Enforces attribute validation
• Provides traceable reviews and approvals
• Can be enforced on any item
• Propagates structure changes in one organization to multiple organizations
• Synchronizes tasks associated with item change
• The system has five seeded change order types from which you can create specific
types for your business process.
– Change Order without Revision Control
– Change Request
– Commercialization Change Order (Product Data Hub)
– Deviation Change Request
– Engineering Change Order
• Duplicate a seeded type and name it as desired to create a new change order type.
Configuring workflow
The following table shows how automatic promotion or demotion is provided for the status
types.
Scheduled No Yes No
Completed No No No