SWIFTSuite R12 Upgrades And Options Final

Lifecycle Tools for your Oracle E-BusinessSuite SFS INTL.

Introduction Presentation Objectives Introductory Comments – R12 UpgradesR11 –>R12 Traditional UpgradeProcess

Traditional Method Using SwiftSuite For An Upgrade SWIFTSuite OptionsUpgrade Process Flow and Demo

Scott Jackson – President, SFS International Phillip Martin – CEO RapidSolutions & Consulting Julie Russo – Sr. Project/Solution Manager

Meeting Objectives• To Gain a Better Understanding of SWIFTSuite Software Process Used For An Upgrade From 11i To Release 12• Current Options Available for the Customer including the Pros and Cons of Each, as Well as the Timing and Associated Costs

Understand the Business Reason Answers will come in the form of . . . Oracle is They want to going to They want to fix thediscontinue use problems insupport for functionality their existing 11.5.10.2 that R12 instance offers

Introductory Comments• Estimates for upgrade tasks noted in this presentation are based on feedback from our existing customer base and ongoing discussions within the market• 11i to R12 is not just a technical upgrade •R12 design is fundamentally different• Now involves technical team/ user team/ functional teams• All History will be maintained• Upgrade must be planned around business events.

Introductory Comments (cont.)• Upgrade disrupts business for many months as the system and the business MUST be frozen until the upgrade is complete. – Upgrade is more like a new implementation because it is going to involve every area of the business. – Avg. five (5) day downtime for patching and data conversion.• If you want to use GAAP (multiple country), you can not do this with the R12 upgrade. Not all R12 functionality is going to be available by simply doing an upgrade.

8 Weeks or 80 FTE Days First 14 Steps Require two (2) Resources with DBA SkillsDetail on Steps 1-14 4 Weeks or 20 FTE Days Steps 15 – 17 Requires two (2) Full Time Employees Familiar with AP/AR/HRDetail on Steps 15-17 6 Weeks or 60 FTE Days Steps 18-20 Requires One (1) Consultant Familiar with E- Business Tax Detail on Steps 18-20

R11->R12 Traditional Upgrade Process R-11 –> R12 StandardTasks 1-14 Tasks 15 -17 Upgrade80 FTE Days Tasks 18 -20 Process 60 FTE Days Production 20 FTE Days System Upgrade2 Resources Grand Total 2 Full Time 50 FTE Days Resources 1 Full Time 210 FTE Resource 5 people x 5 Days days x 16 hour days or (42) Weeks

SwiftSuite Upgrade Option I.Extract configurations, Master Data and Open transactions for eachoperating unit (OU) and push them into the R12 instance.Here you can take the opportunity to: Improve the quality of the instance by leaving behind unwanted configurations Speed up the setup of future operating units by using the templates and process introduced by this option Standardization 1. Extract your existing configurations by using the Reverse tool 2. Create Global Master Templates (GMT’s) of your environment 3. Setup each operating unit using the GMT’s 4. Add in any specific country unit or country needs

SwiftSuite Upgrade Option I.Configuration and Data Migration to R12 FTE Days• Reverse First Operating Units 1.0• Validate the reversed data 2.0• Run Business Rules (1) [BUCC] 1.0• Modify template [BUCC] values as needed 1.0• Change COA/Other Configuration Values 5.0• Create Mass Change Template of Old/New Values 2.0• Load BUCC 1.0• Apply Business Rules (2) 1.0• Apply Mass Change template 1.0• Validate results/create new business rules as needed 3.0• Inject/Create new business rules as needed 5.0GRAND TOTAL FOR FIRST OPERATING UNITS 23.0 FTE Days

SwiftSuite Upgrade Option I.Configuration and Data Migration to R12 FTE Days• Reverse Subsequent Operating Units 0.5• Validate the reversed data: Data is now known 0.0• Run Business Rules (1) [BUCC] 0.5• Modify template [BUCC] values as needed 1.0• Change COA/other configuration values as needed 0.0• Have the business rules to automate this task from OU1• Create Mass Change Template of Old/New Values 0.0• Load BUCC 0.25• Apply Business Rules (2) -Cleans up unwanted data 0.25 based on BUCC values• Apply Mass Change template 0.5• Validate results/create new business rules as needed 0.0• Inject/Create new business rules as needed 2.0GRAND TOTAL FOR SUBSEQUENT OPERATING UNITS 5.0 FTE DaysNOTE: Usually there are multiple operating units• They can be setup in parallel• 5 consultants can configure 5 X operating units in one week.• The speed for the tasks noted above will increase as consultants become used to the steps, as the injection can ultimately get to be much less than one day.

SwiftSuite Upgrade Option II.Option II is similar to option I, but instead of extracting and injectingEach operating unit individually, it is understood/accepted that it is highly likelyThat about 80% of the configurations are the same for each Operating Unit.• When setting up new operating units, It is also highly likely that 80% of those future configurations will be the Same.• This scenario looks at the process of setting up a Global Master Template and using that as a model for all Operating units - while also Providing total flexibility and personalization of that Operating unit for country and company needs.• The same or similar steps have been shown in the following table for comparison

SwiftSuite Upgrade Option II. Configuration and Data Migration to R12 FTE Days Reverse 1 (the first ) X Operating Unit 1.0 Validate the reversed data 2.0 Run Business Rules (1) [BUCC] 1.0 Modify template [BUCC] values as needed 1.0 Change COA/other configuration values as needed using 5.0 HTML/BR100 interface Make business rules to automate change for other operating units Create Mass Change Template of Old/New Values 2.0 Load BUCC 1.0 Apply Business Rules (2) 1.0 Cleans up unwanted data based on BUCC values Apply Mass Change template 1.0 Create Global Master Template 5.0 Test injection for each type of template Inject/Create new business rules as needed 3.0GRAND TOTAL FOR THE FIRST OPERATING UNIT 37 FTE Days

SwiftSuite Upgrade Option II. Configuration and Data Migration to R12 FTE Days• Reverse Subsequent Operating Units 0.0• Validate the reversed data 0.0• Run Business Rules (1) [BUCC] 0.0• Modify template [BUCC] values as needed 0.25• Change COA/other configuration values as needed 0.0• Create Mass Change Template of Old/New Values 0.0• Load BUCC 0.0• Apply Mass Change template 0.25• Validate results/create new business rules as needed 0.0• Inject/Create new business rules as needed 1.5 – 0.2GRAND TOTAL FOR SUBSEQUENT OPERATING UNITS 1.5 - 2.5 FTE Days NOTE: Usually there are multiple operating units • They can be setup in parallel • 5 consultants can configure 5 X operating units in one week. • The speed for the tasks noted above will increase as consultants become used to the steps, as the injection can reduce as much less than one day.

Savings Summary# OU’s In Traditional SwiftSuite SwiftSuite % SavingsUpgrade Upgrade Option I Option II10 210 days 1st OU = 23 days 1st OU = 37 days Option I = 67%Operating Subsequent OUs = 5 Subsequent OUs = Option II = 73%Units days X 9 = 45 FTE days 2 days X 9 = 18 FTE days Total FTE Days = 68 Total FTE Days = 5520 300 Option I = 60%Operating increases 23 + (19 X 5) = 118 FTE 37 + (19 X 1.5) = Option II = 78%Units Due to days 65.5 FTE days increased Data It is obvious from the above table that if the customer has many operating units Option II offers substantially more savings

Graphical Savings Summary 900 800 700 600FTE Days 500 Traditional 400 Swift Opt. I 300 Swift Opt. II 200 100 0 1 10 20 50 100 Operating Units

Oracle 11i Upgrade to Release 12 A High Level Introduction SwiftSuit e

KnowledgeBase Configurator Reverse Package 1. 2. Configuration in 11i Format Oracle EBS Applications REVERSE1. Reverse needs to know what configurations to extract from the Oracle EBS Instance. A package is obtained from CONFIGURATOR2. Reverse then extracts the configurations

Configuration in 11i Format Configuration in R12 Format Configurator KnowledgeBase1. Map the data to R12 format from 11i2. Load to the Knowledgebase

EBusiness Tax + Ledger Configurations Default rules add tax, One ledger for each SOB, One set of responsibilities for each Ledger These can be changed as needed KnowledgeBase

A further set of business rules produces a list of the Key values for an operating unit, such as but not limited to: 1 Enabling what currencies you require 2 The details of your organization chart [Business group, Legal Entity, Operating Unit, Primary Ledger Name, many more] 3 Accounting calendar generation – for as many years as you like 4 Loading your own value sets 5 Setting up account code segments and matching them to the value sets 6 Loading your own chart of accounts [if the default one is not acceptable] 7 Account Aliases 8 Mandatory account codes required to be able to complete the configuration 9 Workday calendars10 Responsibilities and Responsibility keys11 VAT’s and Withholding taxes12 AR Transaction types13 OM Transaction types14 Price Lists15 Sub inventory names16 Document sequences

Each sheet needs to reviewed and adjusted as needed. If it is required to change the operating unit before injecting into the target Instance - this is where it should be done [COLUMN C].There are many worksheets Accounting structure, names and segment sizes [and much more] can all be changed at this stage

1. Reload the amended BUCC into the project2. Action the BUCC to change all the values to the New OU Values

It may be the source contains some seeded data Or The target contains some configurations already ByReversing the target server and running a difference reportOnly the configurations that are not in the target will remain

So far the configurations have been changed in value, andcompared to the target server but Reverse extracts a lot ofinformation for the Operating Unit that was selected – includinginformation that may be related.That relationship is important if a report is needed but containsway too much data if all is needed is to inject a new Inventoryorganization.This second set of business rules removes unwanted configs.using the BUCC from the earlier step.

1. Perform the validation2. Review the errors and use consulting knowledge/skills tocorrect the issue generate a package to ensure all the convertedconfigurations will pass the generate package checks

1. Produce a configuration listing - Generate a BR100As shown in the video, you can change the configurations on screenor push to excel and then reload the excel sheet. Any configurationcan be changed this way.2. Perform another VALIDATION and correct any errors3. Generate a package for injection

Start BUILD -A parameter file with environment details is neededThe server is then checked and validatedThe package in the previous step is then loaded and runThe configuration will proceed automatically and configurethe new R12 instance

SFS International3867 West Market Street Suite 165 Akron, OH 44333 (330) 461-9406SFSINTL.

•••••••••••••••••••••••••••Require 2 x Resources with DBA Skills ••••••••••••••••••••••••••• Tasks 1-14 requires two (2) resources ••••••••••(8) weeks (80 FTE Days) with DBA skills and will take eight Exit First 8 Elapsed Weeks or 80 FTE Days

•••••••••••••••••••••••••••Requires 1 Consultant Familiar with E-Business Tax Tasks 15-17 requires two (2) full time employees familiar with AP/AR/HR and will take 6 weeks or 60 FTE Days Exit 4 Elapsed Weeks or 20 FTE Days

•••••••••••••••••••••••••••Requires 2 x Full Time Employees Familiar with AP/AR/HR Tasks 18-20 requires one (1) consultant familiar with E-Business Tax in multiple modules and will take 4 weeks or 20 FTE Days Exit 4 Weeks or 20 FTE Days

SWIFTSuite R12 Upgrades And Options Final

by SFS International on Apr 11, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 8

Statistics

SWIFTSuite R12 Upgrades And Options Final — Presentation Transcript