Microsoft PowerPoint - Product Hub - Presentation

1
Introduction to Product Hub

Product Hub Implementation
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.

Topics
• Features of Product Hub

• Key benefits of using Product Hub
• Product Hub functionality architecture
• Basics of navigation in Fusion Applications interface
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
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
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.
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
Enterprise-Wide Single Source of Truth
• Attributes
• Attachments
• Catalogs Consolidate Cleanse
• Relationships
• Trading Partners Product
Hub
• Organizations
• Product Classification Govern Share
Consolidating Product Data from Multiple Sources
Data Consolidation
• Item Batches Consolidate Cleanse
• Spoke Systems
Product
• Import Maps Hub
• Data Pools
Govern Share
• Web Services
• Suppliers
Data Cleansing
Data Cleansing
• Item Rules Consolidate Cleanse
• Item Templates
Product
• Data Quality Hub
Standardization
Govern Share
Data Governance
Data Governance
• Item Rules Consolidate Cleanse
• New Item Requests
Product
• Change Orders Hub
Govern Share
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 10

Data Sharing
Data Sharing
• Publication Consolidate Cleanse
• Reporting
Product
• Web Services Hub
Govern Share

Product Hub Integrations
Oracle Product Hub Cloud

DATA ON-BOARDING DATA PUBLICATION
Secure Secure
Product Hub Portal Content Content Product Data Publication
Third‐party product Repository Repository Publish taxonomy (item class,
information hierarchy, attributes, attribute
& digital assets in CSV and valid values) and item data in
XML XML format
Firewall
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

Product Hub Item Entities
Associations Item Relationships

‐‐ Item Organization ‐‐ Cross‐Reference Item Relationships -- Related item Relationships
‐‐ Item Supplier Organization ‐‐ Trading Item Relationships ‐‐ GTIN Relationship
‐‐ Spoke System Item Relationships
Items: Operational Attributes, Extensible Attributes
Structures Security Item Category

Attachments
‐‐ Item Structures ‐‐ Data Assignments
‐‐ Packs ‐‐ Functional

Product Hub Functionality Concept
External
Systems
Manage
Items (UI Data NIR/CO
Based) Quality
Items
Items # Description
Item
Item Mass
Rules
Changes (UI Item
Based) Import
Catalogs
Catalog Name Description Category
Item Batches
(Spreadsheet ,
CSV, XML)
ADFDI Product Hub Portal GSDN Publications ** Legends

(Spreadsheet ( CSV,XML) Integration
Based) Data Modification Flow
Reference Data Flow

Planning an Implementation
To plan the implementation of your offering:

• Know the business processes that your organization performs or supports.
• Associate the business processes to the appropriate product offering and the functional
areas where you want to implement.
• Review all the relevant documentation for your product offering and prepare data you
require to configure it.
– You use the Functional Setup Manager to view the detailed reports for the relevant
product offering.

SCM Security
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.

Documentation Resources
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

Additional Resources
• Cloud Customer Connect Community
– Supply Chain Planning and Collaboration Forum
– Supply Chain Planning Idea Lab
– Supply Chain Management Events
• Supply Chain Planning Release Readiness Material
• White Papers
– https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=2150638.1

Customer Connect Training Replays
• Customer Connect Training Replays:

– SCM – Improve product data quality using Product Hub:
https://cloudcustomerconnect.oracle.com/posts/13c2786540
• Oracle Supply Chain Management Integration Lesson

Concepts of Organizations in Product Hub
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

Concepts of Definition and Reference Organization
• 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 Master-Child Relationship
• Item organizations:
– Can be arranged in a single level
master-child relationship
– Make item data maintenance easy
– Make item administration easy

Managing Units of Measure
• 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.

Setting Up Item Lifecycle Phases
• 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.

Overview of Item Classes
• 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.

Overview of Item Classes
• 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

Setting Up Item Classes
Steps for setting up of item classes are: Root Item Class
• Create a list of all items.

Electronic Item Class
• Classify or categorize these items (item H Components
i
classes). e
Part # ____
r
a Manufacturer ____ Attributes
• Define parent child relationships if any (item r Price ____
class hierarchy). c
h
Attribute N ____
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
____ ____

Item Class Inheritance

Managing Security for Item Classes
The following actions can be assigned to a user or group for a given organization:
Maintain Item Asset Maintenance Maintain Item Purchasing Group

Group Maintain Item Receiving Group
Maintain Item Attribute Maintain Item Revision
Maintain Item Basic Maintain Item Service Group
Maintain Item Costing Group Maintain Item Structure
Maintain Item General Planning Group Maintain Item Structure Group
Maintain Item Inventory Group Maintain Item Web Option Group
Maintain Item Invoicing Group Maintain Item Work In Process Group
Maintain Item Lead Times Group View Item Attribute
Maintain Item MRP And MPS Group View Item Basic
Maintain Item Order Management View Item Pack
Group View Item Structure
Maintain Item Pack Create Item Class Item
Maintain Item People Read
Maintain Item Physical Group Update
Maintain Item Primary Group
Maintain Item Process Manufacturing
Group.

Types of Attribute
Item Attribute Description Where It Appears

Type
Main Attributes common to all items. In Overview tab of the Create Item and
the item’s data model. Edit Item pages
Operational Determines behavior of item in Specifications tab of the Create Item

applications outside Product Hub and Edit Item pages
Transactional Captures values generated during Item: Transactional region of

transaction flows involving an item Specifications tab
Extensible User-defined attributes that need Item: Specifications tab. Each page
Flexfields require organization, possibly into is listed as a link
categories or hierarchies

Extensible Flexfields (EFF)
• EFFs are summarized as the following. EFFs:

– Are user-defined attributes for items, with the functionalities similar to pre-defined
attributes. For example, validations.
– Restrict access to the user-defined attributes
– Offer multi-row support
– Are added to item class displayed in user-defined pages
– Are inherited by child item class
– Can be added to item keyword search

Displaying Attributes and Attribute Groups
• EFF Attribute Group(single-row):
• EFF Attribute Group (Multi-Row):

Creating Item Attribute Groups and Attributes
• Creating the attribute group

Defining Data Security for EFF Attribute Groups
3
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.

Assigning Data Grant to the Attribute Groups

Deploying Your Extensible Flexfields
6
• After you associate the attribute groups and the pages with an item class, you must
deploy the EFF flexfields for the item class to complete the changes.
• To deploy, execute Deploy Item Extensible Flexfields task in Setup and Maintenance
Work Area and Manager and search for Item Extended Attributes in the Name field.
• Click Deploy Flexfield button or Deploy Offline.

Deploying Your Extensible Flexfields
Deployment Option Description
Deploy Flexfield Online incremental deployment. The

deployment process begins immediately, and
you can monitor it. Only the extensible flexfield
setup that changed is deployed.
Deploy Offline Offline, background process of incremental

deployment. You can continue working on the
session before deployment is complete.
Refresh & deploy offline Complete (forced) deployment of all available

extensible flexfields. Completion time depends
on number of flexfields.

When to Deploy Extensible Flexfields
• 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.

Mandatory Item Setup Tasks in Product Hub
The set up tasks you require to initially create items, include:

• Setting up units of measure
• Setting up item organizations
• Managing lifecycle phases
• Managing item classes

Item Terminology
• Item
• Item
Attribute
• Formatted
Description
• Item
Revision

Compare Search Results
• Use the Compare feature to place items side-by-side for comparison

• Select each item for comparison and then click the Compare button

Item Terminology
• Item relationships
• Item associations

Item Terminology
• Product structure/Bills of material:

– A list of components that are used to manufacture or assemble an item.
– Each component itself may have it’s own product structure.
— For example, a bicycle is made up of a frame , a handle bar , a set of pedals and two
wheels. Each wheel is made up of spokes , gears, and tire.
• Item catalogs:
– A collection of items that can be presented in a hierarchical category structure
representing a business purpose.
— For example, you may create a catalog for Father’s day specials and include categories
such as power tools and camping gear. You can then add relevant items to each
category.
• Packs: A hierarchical representation of items representing the logical structure of the
product packaging needs.

Overview of Structures

Overview of Structures
• A structure is a list of components that is used to manufacture or assemble an item. For

example, a bicycle.
• Each component in a product structure is an item which may have it’s own product
structure. For example, wheel assembly or a seat assembly of a bicycle.
• An item can have an unlimited number of user-defined product structures, one for each
business purpose. For example, production planning, engineering.
• An item must have a primary structure.
• Structures can be validated against the lifecycle.
• A structure is specific to an organization.

Setup Tasks for Structures
The key setup tasks for structures are:

• Manage Item Structure Type Details
• Manage Valid Component Type Rules
• Define descriptive flexfields

Product Structure – Create as New
Product structures can be created in one the following ways:

• Create as New

How Structures and Components Are Validated
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.

Overview of Packs
• 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.

Hierarchy of Packs
• 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
Base Unit or Each

Pack Types
A code is used to describe the hierarchical level of a trade item.

• Base unit or each: Lowest level of the item hierarchy intended or labeled for individual
retail sale.
– Cannot have child GTINs (Global Trade Item Number)
• Pack or inner pack: Logistical unit between case and each. This may be a consumable
inner pack. For example, a pack of 12 Shirts.
• Case: The standard shipping unit level.
• Pallet: A flat transport structure designed to support a variety of goods in a stable
fashion while being lifted by any mobile forklift or jacking device.

Pack Type Details
Pack Type Parents Parent Children Child

(TIUD) Instance Instance
Mixed None NA Case, pack or Inner Multiple
Module Pack, Setpack,
Multipack, Base Unit
or Each
Pallet None NA Display Shipper, Case, Single
Pack or Inner Pack,
Setpack, Multipack,
Base Unit or Each
Display Pallet Single Case, Pack or Inner Multiple
Shipper Pack, Setpack,
multipack, Base Unit
or Each
Case Pallet, Mixed Multiple Pack or Inner Pack, Single
Module, Display Setpack, Multipack,
Shipper Base Unit or Each

Pack Type Details
Pack Type Parents Parent Children Child

(TIUD) Instance Instance
Setpack Pallet, Mixed Multiple Pack, Base Unit or Multiple
Module, Display Each
shipper
Multipack Pallet, Mixed Multiple Pack, Base Unit or Multiple
Module, Display Each
shipper, Case
Pack or Pallet, Mixed Multiple Base Unit or Each Multiple
Inner Pack Module, Display
Shipper, Case
Base Unit or Pallet, Mixed Multiple NA NA
Each Module, Display
Shipper, Case,
Pack or Inner
Pack, Setpack,
Multipack

Item Attribute Rollup
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

Create Packs
• Assign items to pack

Overview of Catalogs and Categories
• 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.

Catalogs Terminology
• 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.

Features of Catalog Management
• 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.

Features of Catalog Management
• 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.

Creating Catalogs

Catalog Data Security
• 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

Enabling Catalog Data Security
• 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.

Catalog Data Security Details
• 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.

Catalog Data Grants

Mass Change Types for Items
- Implementing changes to large numbers of items using Product Hub and

spreadsheet based interface
- To make changes to a collection of items identified based on your criteria, use the
following options:
• Mass assign items to organizations.
• Mass assign Catalog and Categories
• Mass assign items to supplier organizations.
• Mass migrate Items to a different Item Class
• Mass create Structures from common
• Mass Reassign Catalog Categories
• Mass Unassign Catalog Categories
• Mass Edit Item Attributes using Spreadsheet Interface
• Mass Edit Item attributes

Performing Mass Changes
To perform mass changes, perform the following steps:

1. Query a list of items that require changes.
2. Choose the type of change.
3. Choose the change execution method:
a. Import it through item batches
b. Use spreadsheet to edit and then import it through item batches
• Review the item batches and make corrections.

MB7
Mass Assign Items to Organizations
• Assign a selected list of items to an

organization along with the
packs(optional) and structures (optional
with a choice of copy or common).
• Other considerations
– Only the selected structure names
will be copied or made common to
the target organizations.
– Editing in spreadsheet provides
more options for changes

Slide 67
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
Propagate product data changes via a Governed Workflow.
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
Collaborative Product Changes Workflow

Overview of Change Orders
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

Business Benefits
The benefits of change orders are:

• Improve product data quality through review and approval of important changes
• Reduce the time to market by streamlining the approval process
• Comply with regulatory requirements by ensuring all required stakeholders have
approved the change

Change Order Process Overview

Change Order Process Overview
Change order process and workflow status is as follows:

• Prepare change order
– Draft status
– Open status
– Interim approval status
• Review
– Approval status
— User - defined approvals
— Approval Manager based approvals
• Scheduled
– Scheduling status
• Implemented
– Completed status

Item Changes Supported by Change Orders
Change orders can modify the following information:

• Item attributes
• Item structures
• Packs
• Associations
• Revisions

Seeded Change Order Types
• 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.

Configure Change Order Type
Specify change order default values and number generation.

Configure Change Order Type – Workflow
Configuring workflow

Configure Change Order Type – Approval Status
Configure workflow approval status

Configure Change Order Type – Propagation Rules
Propagation rules configuration

Configure Change Statuses
Change Statuses are user defined.

User
Defined Design Finance CCB
Create Scheduled Implemented
Change Review Review Approval
Statuses
Change Open Interim Interim Approval Scheduled Completed
Status Approval Approval
Types

Automatic Promotion and Demotion
The following table shows how automatic promotion or demotion is provided for the status
types.
Status Type User selection Default automatic CO can be set for

required promotion automatic
demotion
Open Yes No No
Interim Approval Yes No Yes
Approval No Yes Yes
Scheduled No Yes No
Completed No No No

Change Order Approval Workflow – Options
Below are the two approval choices for change orders:

• User-defined approvals: These are easy to manage.
• Rule-based approvals: These are for complex approval needs.
• Note: Both the approval types in the approval workflow have been implemented in the
same way as in new item request. Hence in this lesson we will address only the changes
relevant to the change orders.

User-Defined Approvals
• You can assign an individual or group

• You can set that all must approve or only one must approve
• Configure using the Workflow tab of the Edit Change Order Type page

Rule-Based Approvals
• You can assign an individual or group

• You can an approval sequence so that one approver must approver before another
• Set conditions that define when certain approvers are allowed to approve
• Configure using the Workflow tab of the Edit Change Order Type page and in the BPM
interface

Approval Groups and Rules
Use the Manage Approval Groups setup task to:

• Create sequential approval groups
• Conditional approval rules

Microsoft PowerPoint - Product Hub - Presentation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microsoft PowerPoint - Product Hub - Presentation

Uploaded by

Copyright:

Available Formats

1

Introduction to Product Hub

Copyright © 2018, Oracle and/or its affiliates. All rights reserved.

• Features of Product Hub

• Item Batches Consolidate Cleanse

• Item Rules Consolidate Cleanse

• Item Rules Consolidate Cleanse

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 10

• Publication Consolidate Cleanse

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 11

Oracle Product Hub Cloud

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 12

Associations Item Relationships

Items: Operational Attributes, Extensible Attributes

Structures Security Item Category

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 13

Catalog Name Description Category

ADFDI Product Hub Portal GSDN Publications ** Legends

Reference Data Flow

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 14

To plan the implementation of your offering:

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 15

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 16

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 17

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 18

• Customer Connect Training Replays:

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 19

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 20

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 21

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 22

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 23

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 24

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 25

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 26

Steps for setting up of item classes are: Root Item Class

• Create a list of all items.

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 27

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 28

Maintain Item Asset Maintenance Maintain Item Purchasing Group

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 29

Item Attribute Description Where It Appears

Operational Determines behavior of item in Specifications tab of the Create Item

Transactional Captures values generated during Item: Transactional region of

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 30

• EFFs are summarized as the following. EFFs:

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 31

• EFF Attribute Group(single-row):

• EFF Attribute Group (Multi-Row):

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 32

• Creating the attribute group

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 33

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 34

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 35

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 36

Deployment Option Description

Deploy Flexfield Online incremental deployment. The

Deploy Offline Offline, background process of incremental

Refresh & deploy offline Complete (forced) deployment of all available

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 37

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 38

The set up tasks you require to initially create items, include:

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 39

Copyright © 2018, Oracle and/or its affiliates. All rights reserved. 2 - 40