Oracle Fusion Product Hub Overview, Technical Architecture & Data Model Siva Dirisala Senior Director, Product Development.

Oracle Fusion Product Hub Overview, Technical Architecture & Data Model Siva Dirisala Senior Director, Product Development

<Insert Picture Here>
Agenda <Insert Picture Here> Fusion Product Hub: Reference Architecture Fusion Product Hub: Technology Components Fusion Product Hub: Integration Architecture Fusion Product Hub: On The Cloud Fusion Product Hub: Data Model Q&A Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential 2

Agenda <Insert Picture Here> What is MDM? Fusion Product Hub: Reference Architecture Fusion Product Hub: Technology Components Fusion Product Hub: Integration Architecture Fusion Product Hub: On The Cloud Fusion Product Hub: Data Model Q&A Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential 3

Master Data Management
Is the Ability to… Consolidate information into one master repository from disparate systems and business lines Cleanse and Enrich data centrally Distribute data as a single point of truth for a consistent enterprise view Leverage master data to service consuming applications, enterprise business processes and decision support systems Delivering Key Business Benefits So what does mastering data mean? It is the ability to “Consolidate, Cleanse/Enrich, Distribute and Leverage” in a centralized environment –single source of truth or system of record. So as as example, Master Customer Entity means consolidating the following Customer Attributes Improve Governance Manage & Avoid Risk Attain Compliance Streamline Processes Decrease Costs Improve Customer/Distributor Service Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Implementation Styles of MDM
Tactical Guideline: Note that desired implementation style changes over time, as your MDM strategy evolves and broadens to take account of more master data domains in your business. Revise technology selection routines accordingly. Registry Low control, autonomous environments Nonintrusive of edge applications Emphasis is on remote data and application to application integration (lots of real time network access) Distributed governance Faster to implement then coexistence and centralized Consolidation Ideal for reporting or analytics that reside in a BI/data warehouse Nonintrusive to the business BI is the business platform Any industry Benefits dependent on success of BI strategy No attempt to clean up source data Coexistence Centralized Large-scale distributed model Largest change to information infrastructure Greatest need to mirror data Global and local governance Greatest risk over control, security Focused on shared services High control, top down environments Largest change to application infrastructure Hugely invasive to the business Centralized governance Greatest control over access, security Focus on common services There are different architectural styles for MDM systems. Each style provide different capabilities, require different levels of architectural commitment and organizational change, and are applicable to different situations. The "consolidation" style brings a view of the master data (most often using metadata to describe the master data) in the confines of a data warehouse separate to the operational source systems. The "registry" style maintains a central key of global identities, links to master data in source systems and holds transformation rules. At runtime, it accesses the source master data and assembles a point-in-time view. This style is a relatively noninvasive layer and tends to be used for identity management. The "centralized" style, previously referred to as "transactional" is where the enterprise has decided to centralized authorship, governance, and storage of the actual master data in a single hub for all purposes. The "coexistence" style is a hybrid style that reflects aspects of all the other styles, and more generally recognizes that authorship, governance, and storage, are distributed across disparate sources in varying degrees of complexity — which has to be catered to by a lot of data duplication and synchronization. Action Item: Understand the various MDM architectural styles, and decide which one is required for your MDM of product data implementation. Note that over time you may end up mixing and matching styles for product, and other master data types. Courtesy : Gartner - Where is MDM Going in the Next 5 Years Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Oracle Enterprise MDM: Fusion V1
Tactical Guideline: Note that desired implementation style changes over time, as your MDM strategy evolves and broadens to take account of more master data domains in your business. Revise technology selection routines accordingly. Data Governance & Compliance Analytical MDM Apps Operational Systems Operational MDM Apps Analytical Systems Customer Supplier Employee Product Financial Analytical Asset Location Siebel DW EBS BI &Datamarts SAP Planning Custom Apps MDM Platform Foundation Enterprise schema & Common services Financial Consolidation Oracle Fusion Middleware External Apps Budgeting Integration Architecture There are different architectural styles for MDM systems. Each style provide different capabilities, require different levels of architectural commitment and organizational change, and are applicable to different situations. The "consolidation" style brings a view of the master data (most often using metadata to describe the master data) in the confines of a data warehouse separate to the operational source systems. The "registry" style maintains a central key of global identities, links to master data in source systems and holds transformation rules. At runtime, it accesses the source master data and assembles a point-in-time view. This style is a relatively noninvasive layer and tends to be used for identity management. The "centralized" style, previously referred to as "transactional" is where the enterprise has decided to centralized authorship, governance, and storage of the actual master data in a single hub for all purposes. The "coexistence" style is a hybrid style that reflects aspects of all the other styles, and more generally recognizes that authorship, governance, and storage, are distributed across disparate sources in varying degrees of complexity — which has to be catered to by a lot of data duplication and synchronization. Action Item: Understand the various MDM architectural styles, and decide which one is required for your MDM of product data implementation. Note that over time you may end up mixing and matching styles for product, and other master data types. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion MDM: Technology Differentiators
Tactical Guideline: Note that desired implementation style changes over time, as your MDM strategy evolves and broadens to take account of more master data domains in your business. Revise technology selection routines accordingly. Native SOA Based Hubs Best in class standards based J2EE applications leveraging latest Fusion Middleware technology providing technical adaptability Single Tech Stack for Multi Domain, Multi Form MDM Needs Single code line for On- Premise and On-Demand with support for multi-domain, multi form MDM on single platform featuring common services reducing total cost of ownership Comprehensive Embedded Data Intelligence/Governance Proactive monitoring, governing of critical data, trends, with integrated dashboards; advanced ad hoc analytic capabilities using embedded Oracle Business Intelligence Applications Pervasive and Proactive Data Quality Management Leverage best in class native Data Quality solutions to reduces data quality problems at point of entry & continuously monitors data issues Standard Based Integration Framework Comprehensive Web Service/Java API, ODI based batch framework with what-if analysis capability to reduce implementation effort/cost Embedded Enterprise Search, Web 2.0 Features Enhanced information retrieval and sharing, Interactive and efficient rich Web 2.0 User Interface to improve end user productivity and enhance collaboration End to End Business Process, Policies Support Business process orchestration using BPEL, governance/ approval via AMX, declarative specification of data policies, and improved manageability and upgradability There are different architectural styles for MDM systems. Each style provide different capabilities, require different levels of architectural commitment and organizational change, and are applicable to different situations. The "consolidation" style brings a view of the master data (most often using metadata to describe the master data) in the confines of a data warehouse separate to the operational source systems. The "registry" style maintains a central key of global identities, links to master data in source systems and holds transformation rules. At runtime, it accesses the source master data and assembles a point-in-time view. This style is a relatively noninvasive layer and tends to be used for identity management. The "centralized" style, previously referred to as "transactional" is where the enterprise has decided to centralized authorship, governance, and storage of the actual master data in a single hub for all purposes. The "coexistence" style is a hybrid style that reflects aspects of all the other styles, and more generally recognizes that authorship, governance, and storage, are distributed across disparate sources in varying degrees of complexity — which has to be catered to by a lot of data duplication and synchronization. Action Item: Understand the various MDM architectural styles, and decide which one is required for your MDM of product data implementation. Note that over time you may end up mixing and matching styles for product, and other master data types. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Product Hub: Product Differentiators
Tactical Guideline: Note that desired implementation style changes over time, as your MDM strategy evolves and broadens to take account of more master data domains in your business. Revise technology selection routines accordingly. Enterprise Common Product Model Single Product Data Model with extensibility leveraged by all Fusion Apps eliminating complex integrations and administration overhead associated with disparate data models Integrated Catalog Management Model functional and business categorization of products with master catalogs and shareable categories allowing reuse of hierarchies and reducing maintenance Pervasive and Proactive Data Quality Management Natively integrated Real time and Batch data cleansing services reduces data quality problems at point of entry Configurable and Auditable Governance Process/Policies Dynamic rule based routing, approval and orchestration for product data across internal/external systems enforces policies and speeds up product definition cycle times Streamlined Release Management Process Version management for tracking and auditing granular data changes allows for effective concurrent product administration and release management Intuitive, Interactive UI with Contextual Actions Rich interactive UI with Web 2.0 features for product administration and governance that significantly improves productivity Comprehensive Embedded Product Data Analytics Integrated Product Dashboard provides proactive monitoring of critical product data, status, trends and actionable insight for all data management tasks. There are different architectural styles for MDM systems. Each style provide different capabilities, require different levels of architectural commitment and organizational change, and are applicable to different situations. The "consolidation" style brings a view of the master data (most often using metadata to describe the master data) in the confines of a data warehouse separate to the operational source systems. The "registry" style maintains a central key of global identities, links to master data in source systems and holds transformation rules. At runtime, it accesses the source master data and assembles a point-in-time view. This style is a relatively noninvasive layer and tends to be used for identity management. The "centralized" style, previously referred to as "transactional" is where the enterprise has decided to centralized authorship, governance, and storage of the actual master data in a single hub for all purposes. The "coexistence" style is a hybrid style that reflects aspects of all the other styles, and more generally recognizes that authorship, governance, and storage, are distributed across disparate sources in varying degrees of complexity — which has to be catered to by a lot of data duplication and synchronization. Action Item: Understand the various MDM architectural styles, and decide which one is required for your MDM of product data implementation. Note that over time you may end up mixing and matching styles for product, and other master data types. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Product Hub: Reference Architecture
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Product Hub: Solution Architecture
Custom/ 3rd Party/AU Applications Enrich & Access Local DB Integration Architecture Web Services Multichannel Commerce ERP Sell Side Product Hub Sales Catalog * Sales/Marketing * Lead/Oppty Mgmt * Pricing/Promotions Quote/Order Capture Configurator PLM Product & Catalog Management POS DOO * Inventory * Costing * Logistics * Manufacturing In Side Cleanse & Consolidate 3rd Party Catalogs Web Product Model Procurement Catalog * Supplier Portal * Buy Side CRM PIM Kiosks Web Services Syndicate & Publish *V1 Products Data Pools Collateral Print Catalog Reports Trading Partners Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Product Hub: Technical Architecture
Fusion ADFui Fusion ADFdi Oracle Enterprise Repository (OER) Open Interface CSV Upload Web Services Groovy Fusion IDM Product Data Quality BPEL/AMX Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Product Hub: Technology Components

Technology Components: Comparison
Tactical Guideline: Note that desired implementation style changes over time, as your MDM strategy evolves and broadens to take account of more master data domains in your business. Revise technology selection routines accordingly. EBS Product Hub Fusion Product Hub Fusion Description OA Framework ADFui Fusion Application Developer Faces (user interface) BC4J ADFbc Business components for ADF Workflow, XML Gateway BPEL, BPM, AMX Human workflow and Approvals management WebADI ADFdi Microsoft Office Excel 2007 and above (support matrix) Concurrent Program Manager ESS (Enterprise Scheduler Service) Concurrent jobs and background processes UDA (User Defined Attributes) EFF (Extensible Flex Fields) User defined attributes FND Attachments, Files Online UCM (Universal Content Manager) Attachments for products FND_XXX tables Identity Manager, JAZN User and role provisioning Secure Enterprise Search (SES) Enterprise search for business objects PIM Rules Groovy (PIM) / OBR (Customer Hub) Expression based validation/assignment rules Web Center (Personalization, Collaboration) Personalization and collaboration There are different architectural styles for MDM systems. Each style provide different capabilities, require different levels of architectural commitment and organizational change, and are applicable to different situations. The "consolidation" style brings a view of the master data (most often using metadata to describe the master data) in the confines of a data warehouse separate to the operational source systems. The "registry" style maintains a central key of global identities, links to master data in source systems and holds transformation rules. At runtime, it accesses the source master data and assembles a point-in-time view. This style is a relatively noninvasive layer and tends to be used for identity management. The "centralized" style, previously referred to as "transactional" is where the enterprise has decided to centralized authorship, governance, and storage of the actual master data in a single hub for all purposes. The "coexistence" style is a hybrid style that reflects aspects of all the other styles, and more generally recognizes that authorship, governance, and storage, are distributed across disparate sources in varying degrees of complexity — which has to be catered to by a lot of data duplication and synchronization. Action Item: Understand the various MDM architectural styles, and decide which one is required for your MDM of product data implementation. Note that over time you may end up mixing and matching styles for product, and other master data types. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Applications: Technology
Color Key: Fusion Applications: Technology UI Layer Web Based UI Web Services Framework Tooling Product Dashboard CPUI Product Hub Configuration Extensibility Admin Jdeveloper/ADF Web Services Interfaces Data Extensibility Logic Layer EO VO Validations Extensibility Schema Data Quality Services UI Fusion Middleware Integration Layer BPEL/AMX Rules Scripting Groovy ESS Fusion Schema DQ Schema 3rd Party Schema Data Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Key Technology Components
ADFbc Metadata driven validators EL expression support ADFui Metadata driven control logic Model abstraction through data bindings ADFdi Works closely with ADFbc & ui Requires Microsoft Excel 2007 or above UCM Store attachments for a business object Web Center WYSIWIG personalization Web 2.0 features like Tagging, Group Spaces for fast searching and Collaboration Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

EFF (Extensible Flex Fields)
Functionally Similar to UDA in R12 Uses ADF technology Uses requires deployment (Compilation) improves runtime performance provides seamless access of EFF to all Fusion Technology Components Out of the box integration in UI Search (Query Panel) ADFdi Web Services PIM Rules Approval Rules (OBR) Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

EFF and UDA differences
Reduced Data Levels Item Revision Supplier Controlled At Master vs Org Style vs SKU Translatable at Attribute Group level No data partitioning by attribute group No automatic index creation Dynamically generated web service makes them first class entities

Item Import Re-architected in Fusion to take advantage of Fusion Techstack Same business validation code used between UI and Interface Tables processing Pre-processing logic is parallelized and mostly uses database resources Processing logic is parallelized and mostly uses middle-tier resources (load on database is not as intensive as during pre-processing) Processing performance is controlled by Number of items per batch Number of threads to run in parallel

Domains, Servers and Web Apps
SCM Domain SCM Common Server Product Management Common Web App Product Management Server Product Management Web App UI Scale out Item Import Scale out

Topology

Fusion Product Hub: Integration Architecture

Oracle Enterprise Repository (OER)
Repository of components for Integration Some of the components listed are Data Model Diagrams Tables Views Web Services SOA Composites Topology

Comprehensive Web Services Repository
Easy to service enable ADF business components ADFbc generates SDOs for marshalling and unmarshalling data along with XSDs and WSDLs Comprehensive granular web services provided for master entities 26 Services, 350+ Service Operations available Supports CRUD Partial List of Entities with Public Web Services: Web service: does not go thru interface table, goes against base table directly Item Item Revision Item Relationships Item Associations Product Structures / BOM Product Catalog Item Batch Change Orders Item Class New Item Request Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Product Hub Trusted Product Data 26 Profile & Correct
Catalog Admin & Security Events & Policies Change Management Import Workbench Identification & Cross-Reference Source Data History Blended Record Parse Standardize Enrich Validate Match & De-Duplicate Attributes Policies Trading Partners Catalogs Documents … Publish & Subscribe Transports & Connectors Registry Reporting Access & Search Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential 26

Identification & Cross Reference
Fusion Product Hub: Consolidate Consolidate Import Workbench Source Data History Blended Record Trusted Product Data CSV, Excel, SQL Loader Import Maps with expressions for CSV and XML Data Stage High Volume Batch & Real time Integration 1:M Cross-Referencing Cleansing and de-dup while importing Track all changes to Master Record Business Analytics Identification & Cross Reference Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential 27

Data Onboarding ... XML Excel CSV Batch Import Process
Validation Engine Seeded Validations & Customer Defined Rules (Groovy) Implementation Production Data Pending Stage SQL ODI EBS Agile Siebel 1SYNC Other ... Canonical Objects (EBO) SLIDE PRESENTER: Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Transports & Connectors
Fusion Product Hub: Share Provides commonly used functions as business services/events and web services Entity level business events for subscription by other apps Support multiple protocols and transport utilizing Fusion middleware, BPEL infrastructure 26 Services, 350+ Service Operations avalable (Item, Structures, Catalogs, Change Orders, Versions etc) Publication framework to validate, filter and propagate changes to spoke systems Share Web Services / Java API Trusted Customer Data Business Events Transports & Connectors Authorization Registry Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Sample Integration Fusion Product Hub Item ABM Siebel CRM Item EBM
Provide AIA Foundation Pack(Standard EBOs, services,standard SOA integration with EIL) Item Import Services Fusion Product Hub Item Publish /QueryService Prebuilt AIA PIP’s for end-to-end (*Post V1) Item ABM Item Class Siebel CRM Item Import Item EBM Agile Custom Connector EBS/PSFT/JDE Custom Connector Data Pools Item/Catalog EBM Item Item ABM Legacy/3rd Party Legacy/3rd Party Change Order Item Revision /Version Item Catalog Agile Item ABM Item EBM Item EBM Item ABM Siebel CRM AddtoBatch Product Structure EBS/PSFT/JDE ABCS Item EBS Item EBS ABCS Data Pools Key Benefits Provide an industry leading SaaS CRM solution to EnterpriseOne customers Provide a SaaS CRM solution with a reduced total cost of ownership appropriate for SMB customers Significantly reduce the loss of CRM sales to competitors Deliver on our public commitment to provide an EnterpriseOne to Siebel On Demand PIP Collaborate April Siebel CRM On Demand Integration Pack for Oracle's JD Edwards EnterpriseOne, which is planned to include support for the lead-to-order process, new account creation and maintenance process and product look up synchronization Legacy/3rd Party Legacy/3rd Party Item Specification Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Fusion Product Hub: On The Cloud

Cloud Cloud Enabled Starting Release 5
Enhanced interface tables to support external values in addition to internal ids Common CSV file upload framework to interface tables External Web Services (not in Release 5 to 7)

Cloud Limitations Oracle Public Cloud != Oracle OnDemand
Administration No direct database access No EM access Data Quality No integration with Oracle EDQ yet No support for co-location of non-FA servers No support for service callouts to integrate with on-premise EDQ server Reviewing options Data In CSV and Web Services in addition to UI and ADFdi No direct database dump using tools such as ODI Data Out Publication Framework (not in Release 5) SOA/BPEL/Events Reviewing options based on use cases

Cloud Item Import Oracle Public Cloud On Premise Create Batch
Get Batch Id Oracle Fusion PIM Data Hub Using batch id, create (manually or automated) csv data files one per entity Zip the files for upload Oracle Public Cloud Infrastructure Upload Zip file using SFTP Interface Tables Data Upload ESS Job Data Files In SFTP Folder Submit ESS Job For Upload Data Into Interface Tables Item Import ESS Job Submit ESS Job For Item Import Production Tables Query Batch Review Batch Details For Errors

Fusion Product Hub: Data Model

Terminology Item: An entity that represents products/services that a business manufacturers, stocks or sells Item Revision: Allows tracking changes to an item or its data over a period of time and generally represents a form/fit/function of the item at a given point in time. Item Version: allows tracking of granular change to item data(that typically does not constitute a form/fit/function change) within a given revision Item Attributes: Attributes describe a product or a service in terms of its characteristics, features or properties. Operational Attributes (pre-defined attributes) Transactional Item Attributes Extended or User Defined Attributes Item Relationships: Allows you to relate an item to another item for various contexts Item Associations: Allows you to associate items to different business contexts i.e. organization, supplier items, sites. These are also sometimes referred to as intersections Trading Partner Items: Items that represent products from external parties such as manufacturers, customers, competitors Item Class: A classification hierarchy to logical group products sharing similar characteristics to create a product taxonomy Item Catalogs: A hierarchy for categorizing products belonging to similar product families Product Structure/Bills of Material: A product hierarchy consisting of child items that make up an end item New Item Request: A formal workflow to orchestrate the definition and approval of an items Change Order: A formal workflow to define, manage, approve and implement product changes Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Items 38 Items can be associated with supplier/site
Attributes values can be maintained at an supplier/site level Manufacturer Part #’s Customer Items Competitor Items Related Items Cross References Trading Partner GTIN Source System Items can be associated with Organization Attributes values can be maintained at an organization level Item Revisions allow for tracking changes overtime Attributes values can be maintained at an item revision level Item Versions provide more granular tracking and managing of item related data Operational Attributes Extended Attributes Transactional Attributes Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential 38

Extended Flex Fields (EFF’s)
Allows grouping of Attribute groups for runtime display UI dynamically generated based on metadata Defined in context of Item Classes Values can be maintained at different lntersections Item, Item/Revision/Version Item/Supplier/Site/Organization Item/Organization Consumed by other transactions Attribute values specified during transaction Meta data controls behavior downstream Example: Monogram Logical Grouping of attributes Security maintained at this level Unlimited 3 Types: Single Row Multi-Row Variant – Drives SKUs Attribute is mapped to an existing database column May be Indexed Character, Number, Date, Translatable Text Poplist, Radio Button, Check Box,, Static URL, Dynamic URL Value Set (List of Values) Complex Validation & Defaulting Rules for 1 attribute or across many attributes Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Item Classes and Catalogs
Functional Catalogs to categorize products based on function Example Inventory, Purchasing etc Allows for categorization of products for reporting, rollup and other orthogonal categorization To aggregate external catalogs into a master production catalog Allows mapping of categories across catalogs Attribution & validation rules Number/Description Generation Security Workflow rules Templates Lifecycle Phases Primary Item Class Inheritance Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Product Structures/BOM’s
User Defined and provides naming for different structures of a similar type e.g. EBOM1,EBOM2 User Defined and allows for categorizing different structures User Defined and provides naming for different structures of a similar type e.g. EBOM1,EBOM2 Multi Level Parent-Child Hierarchy 9,99,999 Components per level Limited to 60 Levels Deep Allows to specify alternate components that can be substituted Allows for defining locator information for components Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Change Orders Items that have changes that need to be implemented
Revisions/versions can be created as part of the change Structure Components that have changes to be implemented Multi-Threaded discussions for collaboration as well as audit log of all actions performed on a change Change Tasks and Lines to represent changes that need to be implemented Mapping to propagate changes to multiple organizations Multiple participants(authors,reviewers,approvers for definition and approval workflow Change Statuses to represent the lifecycle of an change for example, open, approval,implement Definition Steps to allocation product definition to different users Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Item Batches Items in pending schema that are being imported/consolidated Staging Tables for populating data before importing into product schema Item Batches for grouping items being imported from external sources Source Systems from which product data is being consolidated or harmonized Items that have been rejected or excluded from being imported as part of the batch import Import Options allow for specifying how data needs to be processed Duplicate Items that have been matched by the data quality engine Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential

Questions & Answers

Oracle Fusion Product Hub Overview, Technical Architecture & Data Model Siva Dirisala Senior Director, Product Development.

Similar presentations

Presentation on theme: "Oracle Fusion Product Hub Overview, Technical Architecture & Data Model Siva Dirisala Senior Director, Product Development."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Oracle Fusion Product Hub Overview, Technical Architecture & Data Model Siva Dirisala Senior Director, Product Development.

Similar presentations

Presentation on theme: "Oracle Fusion Product Hub Overview, Technical Architecture & Data Model Siva Dirisala Senior Director, Product Development."— Presentation transcript:

Similar presentations

About project

Feedback