Technical Upgrade Guidance SEA->SIA migration

Transcription

1 Technical Upgrade Guidance SEA->SIA migration Oracle Siebel Customer Relationship Management Applications Siebel Industry-Driven CRM November 2011 This document is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle.

2 Purpose Statement This document provides an overview of the technical migration path available for customers to upgrade to Industry Applications in the and Siebel releases from an existing Siebel Cross- Industry Applications. 8.1 Release 8.2 Release Siebel Business Applications Release 8.1 was made Generally Available in November 2008 (version SIA 8.1.1). This product is based on the Siebel Industry Applications (SIA) repository. As of SIA 8.1.1, Siebel formally retired the Siebel Enterprise Applications (SEA) (variously referred to as Cross-Industry Applications, Horizontal and HOR ) repository. The SIA repository is a complete superset of the SEA repository. This change was made to reduce duplication in the development process, reduce costs associated with supporting two repositories, and simplify the implementation and upgrade process. A version of SEA was made available in February 2009 to facilitate customers migration from existing SEA implementations to SIA. Siebel Business Application Release 8.2 was made Generally Available in October This product is based on the Siebel Industry Applications (SIA) repository. It is primarily targeted to Public Sector and Loyalty for Retail, Travel and Transportation customers. To adopt any x or x release, Cross-Industry Application (i.e. SEA) customers will need to upgrade to a comparable industry-based offering. Siebel s industry-based offerings deliver robust capability comparable to SEA as well as the advantages of easier uptake of new Siebel CRM products. Cross-Industry functionality is available in every industry specific product line so customers have the ability to upgrade to their choice of industry application. Since SIA repository is a superset of SEA and SIA objects, customers will be able to benefit from a broader set of features and functionality.

3 Frequently Asked Questions 1. What if I have Siebel SEA today and need to upgrade to a Siebel 8.1x or 8.2x release? Siebel SEA is available for upgrading customers in the release. Customers may use SEA8.1.1 as a stepping stone to complete migration to SIA. New Siebel customers, as well as existing SIA customers, must deploy SIA.

4 2. What is the cost factor to migrate from SEA to SIA repository? The cost of a development upgrade primarily depends on the degree of customization. The cost of a production upgrade is driven by data volume and the upgrade path chosen. Due to the limited schema changes between SEA and SIA repository, the cost of SEA->SIA migration is fractional compared to the overall cost of a full upgrade. 3. What are the major schema changes between SEA and SIA applications? Siebel Enterprise Applications (SEA) Contacts/Accounts to Address data model is 1:M relationship Siebel Industry Applications (SIA) Contacts/Accounts to Address data model is M:M relationship The upgrade scripts from SEA to SIA ensure that the data from 1:M is converted to M:M. Figure 1 - Account Address Configuration in SEA Application (1:M)

5 Figure 2 - Account Address Configuration in SIA Application (M:M) 4. What additional effort is needed to migrate from SEA to SIA? Due to data model changes around Address objects between SEA and SIA, migration will result in obsoletion of some SEA objects. Customers must re-configure all Address-related business components that are in use. When migrating from SEA to SIA, the standard upgrade procedure needs to be applied. Migrating from SEA to SIA on the same version requires less effort then upgrading from one version to a higher version. Technical Sources: a) Refer to Upgrade Planning for Migrating Siebel Address Data section in Upgrade Bookshelf on how to manage Address migration b) Refer to Access Control Upgrade and Migration Guide for Siebel 7 (Doc ID ) on Metalink3 for steps on the following data migration: o Migrating data from S_ORG_REL and S_CONTACT_REL to S_PARTY_REL o Migrating data from S_PER_ORG_UNIT to S_PARTY_PER

6 5. What is the last 8.1.x release where SEA will be available to support upgrade? In order to help customers migrate from SEA to SIA repository, we will provide SEA build to customers until FP. Note that granting access is subject to approval from the Oracle Siebel team. Customers should log a service request if they need to access FP or SEA build. 6. Up until when can we still get SEA support on Siebel 8.1.x release? May 2012.

7 Statement of Direction Oracle Siebel Customer Relationship Management Applications Siebel Industry-Driven CRM November 2011 Author: CRM Product Strategy Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA U.S.A. Worldwide Inquiries: Phone: Fax: oracle.com Copyright 2011, Oracle. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle, Siebel, JD Edwards, and PeopleSoft, are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.