1. © 2008 Oracle Corporation – Proprietary and Confidential 1

2. 2 Purpose: This document provides an overview of features and enhancements included in Oracle E-Business Suite Release 12.1. It is intended solely to help you assess the business benefits of upgrading to Release 12.1 and to plan your I.T. Projects. Disclaimer: This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement or other applicable contract with Oracle, with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without Oracle’s prior written consent. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. This 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 is always at Oracle’s sole discretion. This document is not considered part of the applicable program documentation. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.

3. Oracle E-Business Suite Release 12.1.1.01 Transfer of Information Oracle Demand Signal Repository Functional Overview Syndicated Consumption Data

4. © 2008 Oracle Corporation – Proprietary and Confidential 4 Agenda New and Changed Features Syndicated Consumption Data Description Setup and Process Dependencies and Interactions Additional Resources

5. © 2008 Oracle Corporation – Proprietary and Confidential 5 Syndicated Consumption Data Overview

6. © 2008 Oracle Corporation – Proprietary and Confidential 6 Syndicated Consumption Data Description Manufacturers purchase consumption data from Syndicated Data Providers (e.g., IRI or AC Nielsen) to analyze market penetration by: Retailer Geography Product Time Data includes: Sales Quantities and Amounts (various breakdowns) Markdowns ACV Measures

7. © 2008 Oracle Corporation – Proprietary and Confidential 7 Syndicated Consumption Data Description (continued) Data is purchased at various levels of aggregation. For example: Product Category, Sub-Category, Individual SKU Market Area Geographic Region or Sub-Region Customer Hierarchy Organization, Chain, Area, Region, District, Store The level purchased is based on: Budget Business need

8. © 2008 Oracle Corporation – Proprietary and Confidential 8 Syndicated Consumption Data Business Benefit Visibility into retailer sales that might not otherwise be available Allows the manufacturer to have insight into sales of its own, as well as competitor products

9. © 2008 Oracle Corporation – Proprietary and Confidential 9 Syndicated Consumption Data Example Data

10. © 2008 Oracle Corporation – Proprietary and Confidential 10 Syndicated Consumption Data Setup and Process

11. © 2008 Oracle Corporation – Proprietary and Confidential 11 Syndicated Consumption Data Setup and Process Load Syndicated Geography Key Cross Reference (optional) Load Syndicated Consumption Data Load Syndicated Product Key Cross Reference (optional) SET UP & PROCESS Load Look Up Master

12. © 2008 Oracle Corporation – Proprietary and Confidential 12 Step 1: Load Look Up Data

13. © 2008 Oracle Corporation – Proprietary and Confidential 13 Look Up Data Process Flow Description Valid look up values must be defined for Source (SRC_TYP) and Measure Set (MSR_SET). Source is used to identify the source of the data (e.g., IRI). Measure set is assigned to a set of up to 100 measures which can be increased in increments of 100 by having multiple measure sets (e.g., SET1, SET2). Process Flow Name: LOOKUP_DATA Source Table(s):Target Table(s): DDR_I_LKUPDDR_R_LKUP_MST Dependent Table(s): DDR_R_ORG DDR_R_LKUP_TYP

14. © 2008 Oracle Corporation – Proprietary and Confidential 14 Look Up Data Additional Details Required Fields Manufacturer’s Organization, Look Up Type Code, Look Up Code Key Validations Manufacturer’s Organization must be valid Look Up Type Code must be valid Additional Information Up to 100 measures can be loaded for each measure set. If more than 100 measures are required, you must load a new measure set value.

15. © 2008 Oracle Corporation – Proprietary and Confidential 15 Step 2: Load Syndicated Product Key Cross-Reference

16. © 2008 Oracle Corporation – Proprietary and Confidential 16 Syndicated Product Key Process Flow Description The Syndicated Product Key Process Flow loads data which is used to translate the syndicated provider’s product key to a specific value within the manufacturer’s item hierarchy. For example, a syndicated data provider’s product key of 1001 might translate to a Product Category called Bottled Water. Process Flow Name: SYND_PROD Source Table(s):Target Table(s): DDR_I_SYND_PROD_KEYDDR_R_SYND_PROD_KEY

17. © 2008 Oracle Corporation – Proprietary and Confidential 17 Syndicated Product Key Process Flow Description (continued) Dependencies: Source (Look Up Master) Manufacturer Item Hierarchy

18. © 2008 Oracle Corporation – Proprietary and Confidential 18 Syndicated Product Key Additional Details Required Fields Source, Product Key, Product Key Name, Manufacturer Item Hierarchy Level, Manufacturer Item Hierarchy Code Key Validations Source must be valid Item Hierarchy Level must be valid COMPANY, GROUP, DIVISION, CLASS, SUBCLASS, ITEM, SKU Item Hierarchy Level / Code combination must be valid Additional Considerations Partial and Simulation modes supported Changes to product key definition may require manual clean up or re-loading of consumption data Syndicated Product Key deleted when Process Action = ‘D’

19. © 2008 Oracle Corporation – Proprietary and Confidential 19 Syndicated Product Key Sample Data SourceProduct KeyProduct Key Description Mfr Item Hierarchy Level Mfr Item Hierarchy Code SDP10014002001001Anti-Perspirants & Deodorants CLASSDeodorants SDP10014002001002Body Wash & Bath Soaps CLASSBody&Bath SDP10014002001003Shaving ProductsCLASSShaving SDP10014002002001Disposable RazorsSUBCLASSDisposables SDP10014002002002Refillable Systems & Replacement Cartridges SUBCLASSRefillable Systems SDP10014002002003Shaving GelSUBCLASSShaving Gel

20. © 2008 Oracle Corporation – Proprietary and Confidential 20 Step 3: Load Syndicated Geography Key Cross-Reference

21. © 2008 Oracle Corporation – Proprietary and Confidential 21 Syndicated Geography Key Process Flow Description The Syndicated Geography Key Process Flow loads data which is used to translate the syndicated provider’s geography key to dimension values (market area, region, etc.) that are meaningful to DSR. For example, a syndicated data provider’s geography key of 114001 might translate to the Kroger – Atlanta Market Area. Process Flow Name: SYND_GEO Source Table(s):Target Table(s): DDR_I_SYND_GEO_KEYDDR_R_SYND_GEO_KEY

22. © 2008 Oracle Corporation – Proprietary and Confidential 22 Syndicated Geography Key Process Flow Description (continued) Dependencies: Customer organization hierarchy Market Area Geography region and/or sub-region Channel Source

23. © 2008 Oracle Corporation – Proprietary and Confidential 23 Syndicated Geography Key Additional Details Required Fields Source, Geography Key, Geography Name Key Validations Source must be valid Org Hierarchy Level must be valid ORGANIZATION, CHAIN, AREA, REGION, DISTRICT, BU Channel Type, Market Area, Geography Region, Geography Sub-region (if populated) must be valid Org Hierarchy Level / Code, Market Area, Geography Region, Sub-region cannot all be null Market Area, Geography Region, Geography Sub-region are mutually exclusive Additional Considerations Partial and Simulation modes supported Changes to geography key definition may require manual clean up or re- loading of consumption data Syndicated Geography Key deleted when Process Action = ‘D’

24. © 2008 Oracle Corporation – Proprietary and Confidential 24 Syndicated Data Geography Key Sample Data 1 2 3 4 5

25. © 2008 Oracle Corporation – Proprietary and Confidential 25 Step 4: Load Syndicated Consumption Data

26. © 2008 Oracle Corporation – Proprietary and Confidential 26 Syndicated Consumption Data Process Flow Description The Syndicated Consumption Data Process Flow loads external aggregated consumption (e.g., sales) measures received from syndicated data providers. By default, the measures do not have any aggregation rule and can only be viewed at the level they were loaded. Process Flow Name: SYND_CNSMPTN_INF_STG_TO_TGT Source Table(s):Target Table(s): DDR_I_SYND_CNSMPTN_DATADDR_B_SYND_CNSMPTN_DATA

27. © 2008 Oracle Corporation – Proprietary and Confidential 27 Syndicated Consumption Data Process Flow Description (continued) Dependencies: Manufacturer item hierarchy Customer organization hierarchy Market Area Geographic region or sub-region Manufacturer Business Week Channel Type Measure Set Source

28. © 2008 Oracle Corporation – Proprietary and Confidential 28 Syndicated Consumption Data Additional Details Required Fields Record ID, Source Code, Measure Set, Week End Date Key Validations Source Code and Measure Set must be valid Syndicated product and geography keys must be valid (if populated) Either Syndicated Product Key or Item Hierarchy Level / Item Hierarchy Codes must be populated Either Syndicated Geography Key or one of the following combinations must be populated: Org Hchy Level / Org Hchy Code / Channel Org Hchy Level / Org Hchy Code / Market Area / Channel Geography Region or Sub-Region / Channel Market Area / Channel Week Code must be valid Source must be unique for the specified dimension levels

29. © 2008 Oracle Corporation – Proprietary and Confidential 29 Syndicated Consumption Data Additional Details Additional Considerations All (or None), Partial, and Simulation modes supported All consumption data is assumed to be at week level No currency conversion No allocation to lower dimensional levels Default aggregation rule is none

30. © 2008 Oracle Corporation – Proprietary and Confidential 30 Syndicated Consumption Data Sample Data Set 1

31. © 2008 Oracle Corporation – Proprietary and Confidential 31 Syndicated Consumption Data Sample Data Set 2

32. © 2008 Oracle Corporation – Proprietary and Confidential 32 Syndicated Consumption Data - Report

33. © 2008 Oracle Corporation – Proprietary and Confidential 33 Syndicated Consumption Data Report Description

34. © 2008 Oracle Corporation – Proprietary and Confidential 34 Dependencies & Interactions

35. © 2008 Oracle Corporation – Proprietary and Confidential 35 Syndicated Consumption Data Dependencies and Interactions There are no dependencies to other products

36. © 2008 Oracle Corporation – Proprietary and Confidential 36 Additional Resources

37. © 2008 Oracle Corporation – Proprietary and Confidential 37 Additional Resources For more release information on MetaLink https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocu ment?p_database_id=NOT&p_id=403259.1https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocu ment?p_database_id=NOT&p_id=403259.1 For more information about Oracle Applications http://www.oracle.com/applications/home.html For more information about Education http://www.oracle.com/education/index.html For more information about Support http://www.oracle.com/support/ For MetaLink information http://metalink.oracle.com/ For Oracle Product documentation: http://www.oracle.com/technology/documentation/applications.html

38. © 2008 Oracle Corporation – Proprietary and Confidential 38

39. © 2008 Oracle Corporation – Proprietary and Confidential 39