R12.

1UpgradeisEasy
Thatwhichwepersistindoingbecomes easier,notthatthetaskitselfhasbecome easier,butthatourabilitytoperformithas improved. RalphWaldoEmerson(1803 1882)

BuytheBook
thelittler12.1 upgradeguide StepbyStep guideto upgrading11i toRelease12.1 www.trutek.com

Agenda
FunctionalUpgrade UpgradeDrivers ReasonstoUpgrade
CostSavings
HardwareandMaintenance

Simplify,Standardize,SharedServices

KeyR12NewFunctionality UpgradeTeam UpgradeRolesandResponsibilities SteeringCommittee UpgradeSuccessFactors Customizations GapAnalysis

Agenda
AlignBusinessprocesseswithOracleApplications Testing FunctionalandLoad Assessments R12.1UpgradeCategories:
1. 2. 3. 4. PlantoUpgrade PreparetoUpgrade PerformtheUpgrade FinishtheUpgrade Testing

UpgradePaths TechnicalUpgrade UpgradebyRequest VerificationTasks ReducingDowntime

WhoCares?
Managers SuperUsers DBAs Developers QualityAssurance Testing HardwareArchitects

R12.1.2FunctionalUpgrade
TheR12Upgradeisnotjusta technicalupgrade Thefunctionalupgradeconsists ofmappingnewbusiness requirementswithnew functionalfeaturesinR12.

UpgradeDrivers
Compliance CostSavings
HardwareStandardization

CompetitiveAdvantage Integration NewFunctionality

Capability MaturityModel
Efficiency drives Cost Savings

Shared Services Standardize Simplify

Technology&ProcessConvergencelead toSimplification,Standardizationand SharedServices

HardwareUpgradeBenefits
Simplify and Standardize Migrate to more cost-effective 64-bit Linux servers Migrate Application Servers to 64-bit Hardware
Support more users with more addressable memory

Utilize Virtualization to help standardize Implement a SAN with block virtualization capabilities, aka snapshots

ApplicationUpgradeBenefits
Simplify and Reduce Maintenance Costs with: Real Application Testing Automate Patching & Provisioning Automate Diagnostics and Tuning Automate Change and Configuration Management Implement Transparent Data Encryption for better security

SharedServices
Drivecostsavingsandincreaseinformationquality. Consolidatenonrevenuegenerating,administrativetasksin SharedServiceCenters.
Eliminateredundantprocesses Utilizeselfservice, Automateprocesses, Standardizecommonbusinesspracticesreducescosts.

Helpscreateaconsolidatedviewofessentialglobaldecision makinginformation Enhancesthetimelinessandaccuracyofdata.With consistentbusinessprocessesthroughouttheenterprise, informationcanbegathereduniformly,withconsistent quality.

KeyR12Functionality
AME IntegratedFinancials SubLedgerAccounting SubLedgerCurrencyViews MultiOrgAccessControl UserManagement ApprovalManagement

Advanced Global Intercomp any

UMX

KeyR12 Factors
MOAC SLA

GRC

UpgradeTeam
FIN DedicatedTeamMembers TheUpgradeTeamshould beindependentfromdaily operations TeamMembersare selectedfromthebusiness asdeterminedbythe upgradeprojectmanager

HR

MFG

Upgrade Team
CRM PA

IT

UpgradeRoles&Responsibilities
TestingManager FunctionalManager CustomizationManager TechnicalManager LearnNewFeatures Testing GapAnalysis VerifyUpgrade

ProjectManagers

FunctionalSuperusers
GapAnalysis Customizations: Identify Eliminate MigratetoSOA

IdentifyPatches UpgradeTechstacks MeasureDowntime ManageTechnical UpgradeSteps

DBAs

Developers

UpgradeManagerResponsibilities
Managethefollowingmanagers:
DevelopmentManager Customizations DBAManager TechnicalUpgrade SystemsManager HardwareUpgrade FunctionalSuperusers DevelopProcessAlignment TestingManager

ManagetheSteeringCommittee

SteeringCommittee
SteeringCommitteeResponsibilities: MaintainExecutiveSupport GatherUserRequirements DocumentUserSuccessFactors OrganizeUserstoExecuteTestScripts PrioritizeGoals/Issues DocumentUsersIssues MeasureProgressagainstUserSuccessFactorsand ReporttotheExecutiveteam.

TechnicalUpgradeResponsibilities DBAsandDevelopers
Technical Testing Improve the Technical Foundation, hardware, software Understand existing Customizations Understand how new requirements affect the customizations Perform the Technical Upgrade Modify and implement new customizations and extensions Reduce downtime

FunctionalUpgradeResponsibilities
Functional Testing Understand AS IS Model Understand TO BE Model Document the gap between the business process and OA processes Align the Business and Oracle Applications Understand existing Customizations Understand how new requirements affect the customizations Investigate, Improve and Implement Setups Train the Users for example, iProcurement Reduce downtime Verify Upgrade

CompetingPriorities
ReimplementversusUpgrade HardwareMigration DataCleanup ImplementNewModules Customizations
Eliminate
Replacewithnewfunctionality MigratetoSOA

MinimizeRisk
1. 2. 3. 4. 5. TestingProficiency TestScriptsshouldberunaftereach

patchorclone

EnableFastBackupandRestorewithblockvirtualizationor snapshots LettheDBAsandDeveloperspracticetheirpieceofthe upgradeinanindependentenvironment Decoupleotherprojectsfromtheupgrade:newmodules,fix customizations,hardwaremigration,newbusinessprocesses PerformLoadTestingifthereisanyquestionaboutcapacity

ManagersViewofUpgradeSuccess
Teamwork Theupgradewillnot succeedwithout TEAMWORK. Communicationis essential. Time&Money 3monthsto1year $1000peruser+$500 peruser(iusers)with $150Kminimum IncludesCustomizations Doesnotinclude implementingnew modules,hardware migration,etc.

Time & Money

Upgrade Success

Teamwork

Skills

Skills Augmentmissingskills RentaConsultant UpgradeSpecialistsare worththemoney

Budget
Training Functional Analysis Technical Upgrade Customizations Testing 10% - 20% 20% - 30% 20% - 30% 0% - 60% 30% - 40%

Categories and range of the percentage of the total budget

TeamObstacles
Infighting ShirkingofResponsibilities LackofTrust CriticalSkillGaps

CriticalSuccessFactors
GapAnalysisrequires: Superusersthat understandthenew featuresofR12.1& understandthe customizations Testingisthebasisof successforupgrades Testingrequires practice Testingrequires Management Testingrequiresthe bestandmost knowledgeableusers

Testing
Upgrade Success

Gap Analysis

Customizations
Customizations Identify Document Eliminate MigratetoSOA

Customizations
CEMILIs SoftwareFrameworkforExtensions, Customizations,Extensions,Modifications, Internationalizations,Localizations,and Integrationframework. 19classesofextensions Oraclespublishedguidelinesfordeveloping andimplementingcustomextensionstoOracle Applications.

CEMLI
Configurations,Extensions,Modifications,Localizations,and IntegrationsCEMLI. TheCEMLIUpgradeincludesdeterminingtechnicalimpactofOracleE BusinessSuiteRelease12.1onCEMLIs,upgradingCEMLIstothenew technologystack,retrofitofCEMLIsforcompatibilityandusabilityon OracleEBusinessSuiteRelease12.1. Identifyallcustomizations Checkinallcustomizationsintoconfigurationmanagement DeterminecustomizationsthatarereplacedbynewR12.1 functionality ReCodecustomizations PrepareCustomizationUpgradeImplementationPlan CustomizationConfigurationManagement

Customizations,Extensions, Modifications, Testingisthebasisof successforupgrades

Modifications

Modifica tions
Extensions

R12.1Upgrade Customizat ions

Testingrequires practice Testingrequires Management Testingrequiresthe bestandmost knowledgeableusers

Extens ions

Customizations Identify Document Eliminate MigratetoSOA

Vanilla
StartswiththepresumptionthatOOTB processes*willwork80+%ofthetime Timeisspentfocusingonthetruegaps(<20%) requiringcustomization

Customize
Significanttimespentunderstanding currentprocessflows moststaffare notgoodatabstractthinking Createaframeworkforfutureprocess flows.Unrealisticwishlists while developingfutureprocessflows,can makethegoalsunattainable. SimplificationandAlignmentaremore difficultwithoutCustomizations

CustomizationCosts
Customizationinflateslifecycleeffort(cost)by atleast70%,basedonaveragecomplexity assumptionsinthismodel Actualcomplexityandrequiredeffort(cost) maybemuchhigher

CumulativeBusinessValueofSmall BusinessProductivityImprovements
Evensmallimprovementsinbusinessprocessperformancecanyieldlarge
businesssavingsovera5yearperiod

Thisexampleillustratesthe5yearbusinessvalueofvariouslevelsof
productivityimprovement

Every2%improvement 10minutesperdayofworkerproductivity yields

$17millioninsavingsover5years
Assumptions Numberofaffectedemployees Avg.AnnualFullyBurdenedCost/Employee Est.AnnualEmployeeCostInflation EmployeeHoursWorkedperYear TimeFrame(Years) 10,000 $81,000 3% 1,960 5

Customizations BPI
Cost BenefitAnalysisforBusinessProcessImprovement AnnualOperationCosts BPICostsImplement&Upgrade AnnualCustomizationMaintenanceCosts 10%loweroperatingcostswithBPI 1,000,000 1stYear 300,000 60,000 100,000 260,000 60,000 100,000 40000 60,000 100,000 40000 60,000 100,000 40000 2ndYear 3rdYear 4thYear 5thYear 150,000 60,000 100,000 110,000 250,000

AnnualOperationCosts BPICostsImplement&Upgrade AnnualCustomizationMaintenanceCosts 20%loweroperatingcostswithBPI

1,000,000 1stYear 300,000 60,000 200,000 160,000 60,000 200,000 140000 60,000 200,000 140000 60,000 200,000 140000 2ndYear 3rdYear 4thYear 5thYear 150,000 60,000 200,000 10,000 250,000

CriticalSuccessFactors
GapAnalysisrequires: Superusersthat understandthenew featuresofR12.1& understandthe customizations Testingisthebasisof successforupgrades Testingrequires practice Testingrequires Management Testingrequiresthe bestandmost knowledgeableusers

Testing
Upgrade Success

Gap Analysis

Customizations
Customizations Identify Document Eliminate MigratetoSOA

UpgradeIterativeCycles
Align Technology withBusiness Processes Modifyor CreateCEMLIs Improve Business Processes RealizeCost Savings

Added Value

Improvethe Technology Foundation

Implementation/UpgradeLifecycle

GapAnalysis AlignBusinesswithOracleApplications
Integrating the Business with Oracle Applications New Functionality is Iterative
Integrate business changes with Oracle Applications new functionality How has R12.1 changed? Is there new functionality that could improve the process model? Understand Oracles long term strategy?

Business Process
Has my business changed? What are the new business requirements? What is the long term strategy for the business?

Application
Develop new process models. Retire/modify customizations that are replaced by new functionality

35

35

GapAnalysis
FunctionalFinancialR12.1NewFeatures
MultipleOrganizations GlobalAccounting FinancialEnhancements Release11iGLSoB Release12Subledgers MultiOrgAccessControl(MOAC) SubledgerAccounting(SLA) SubledgerAccountingModel SubledgerCurrencyViews LedgerSets IntegratedFinancials SubledgerArchitecture MultipleReportingCurrenciesSharedServices MultiOrgAccessControl(MOAC) EBusinessTax Payments

GapAnalysis
ReviewBusinessProcessBestPracticesforR12.1 Identifybusinessareasthatshouldadoptbestpracticesthatmay differfromcurrentbusinesspractices Furtherinvestigatethefunctionalgapbyexaminingthefollowing: Reasonsforthechangeandareasthatbenefitfromnew functionality Functionalitythatistemporarilydisabledorhasbeenmade obsolete Changestouserinterfaces,terminologyorconcepts,andmenu options

TestManagement
Thelackofeffectivetestingisthesinglemostfrequent causeoffailuretoGoLive.Testingisadedicatedjob. Mostcompaniesonlylendaresourcetoatestinitiative. TheTestManagershouldbeadedicatedresource.The TestManagerstasks:
MentortheTesters Stresstheimportanceoftestingontheorganization Ensureadequatetesting MonitorandimprovetheTestDevelopmentprocess Coordinatetestingwiththetechnicalandfunctionalstaff

TestingMethodology
FunctionalTesting DevelopTest Scripts ExecuteTest Scripts PerformUnitand IntegrationTests Test Customizations Test11irowsin R12.Functional testingcenterson newR12 transactions. Makesure transactionsthat wereenteredin 11icanstillbe usedinR12. TechnicalTesting IdentifyPotentialIssues UnderstandR12Architecture

Technical
LoadTesting Characterize theWorkload Identify Bottlenecks Improve Performance

Functional

Load

TestEnvironments
ThefollowingR12.1testinstancesmaybe required: Developmentinstanceforthedevelopers Testinstanceforeachnewmodulebeing implemented PatchinstancefortheDBA Traininginstancefortraining Moreinstancescanleadtocloningnightmares

FunctionalTesting
FunctionalTestingincludes: UpdatingexistingEBusinessSuitetest scriptstoreflectvalidnavigationpathsfor OracleEBusinessSuiteRelease12.1 DevelopnewOracleEBusinessSuiteRelease 12.1testscriptsandincorporateany customizations. Performregressiontesting

R12.1UpgradeCategories
1. PlantoUpgrade 2. PreparetoUpgrade 3. PerformtheUpgrade 4. FinishtheUpgrade

Release12.1UpgradePaths
PathA DB9iR2,10gR2Apps11.5.7or11.5.8 DBUpgrade&AppsUpgradeneedto becompletedduringthesame downtimewindow. IftheDBalreadyat11gR1,Apps 11.5.9.2or11.5.10.2 OnlyupgradetheAppsStack UpgradetheDB&Appsindifferent phases

PathB

PathC

Release12.1UpgradePaths
Ifupgradingfromareleasepriorto11.5.7,theupgrade pathmayrequireaninterimupgradetoRelease11.5.10.2. Becauseofthesignificantdowntimerequiredtoupgrade fromRelease11.0toRelease12,itmaybemorefeasibleto firstupgradetoRelease11.5.10.2andthensometimelater upgradetoRelease12. ThisrequiresthefunctionaluserstolearnRelease 11.5.10.2,andperformallthetestingforanotherupgrade. Theamountofworknecessarytoperformtworoundsof systemacceptancetestingmayjustifyanotherdayortwo ofdowntime,sothattheupgradefromRelease11.0to Release12.1canbecompletedinonelongerperiodof downtime.

UpgradePaths
11.0 11.5.10.2 11.5.9.2 11.5.10.2

11.5.1 11.5.6 11.5.7 11.5.8

12.0

12.0.4

12.0.6

11.5.9.2 11.5.10.2

12.1.1

12.0.6

12.1.1

Release12.1UpgradePaths
InitialRelease 11.0,11.5.1 11.5.6 11.5.7.11.5.8,11.5.9*or11.5.10* 11.5.7,11.5.8,11.5.9.2,11.5.10.2 11.5.9*,11.5.10* InterimRelease FinalRelease Release11.5.10CU2Release12.0.0 Release12.0.0 Release12.0.4 Release12.1 R12Patch 4440000 4440000 6394500 6678700

12.1.1 Release12.1.0.27303033 *includesCU1andCU2(consolidatedupdate) Figure4indicatesthatadirectupgradepathexistsfromRelease11.5.7toRelease12.0.0.

DatabaseUpgradeRequirements
Release CertifiedDatabaseVersionsonSolaris

12.1 12.0 11.5.10.2 11.5.9.2

10gR2,11gR1andthe64bitversions 10gR2,11gR1andthe64bitversions 10gR2or11gR1andthe64bitversions 10gR2andthe64bitversions

11.5.7

8.1.7,9.0.19.2,and9.264bit

Wecanseethatthereisnocertifieddatabaseversionthatis certifiedwithboth Release11.5.7andRelease12.1. Therefore,wecantdothedatabaseupgradebeforethe downtimewindow.

DatabaseUpgrade
Thedatabaseinstalledbythe11.5.10.2RapidWizisVersion 9.2.0.6.ThisdatabaseversiondoesnotsupportDaylight SavingsTime(DST).Therefore,wehavetwochoices: UpgradethedatabasetoVersion9.2.0.8,whichhas supportforDST,andthenupgradetoVersion11.1.0.7,or UpgradethedatabasetoVersion10.2.0.3,usingthe databaseOracleHomeprovidedwiththe12.0.4EBSinstall. Since,werequireaninterimstep,andwealreadyhavethe 12.0.4DVDsstaged,itiseasiertousethe10.2.0.3Oracle Homethantodownloadthe9.2.0.8patchandapplyallthe EBusinessSuitespecificdatabasepatches.

Start DB Upgrade

Apps Version at Least 11.5.10.2

DB version >= 9.2.0.8 & DST P4

No

DB version at Least 9.2.0.6

Yes
Upgrade Database directly to 11.1.0.7

Yes
Upgrade Database to 10.2.0.3 Use the OH from the 12.0.4 RapidWiz

This guide assumes we start with EBS version 11.5.10.2 and 9.2.0.6 of the database. We upgrade to 10.2.0.3 as an interim step to 11.1.0.7, because this home comes with the 1204 install, The OH that comes with the RapidWiz install has all the necessary database patches already applied.

DB Upgrade Finished

Use the OH from the 12.1.1 RapidWiz install

Post DB Upgrade Steps For R12.1 Fix Korean lexers Run adgrants.sql Grant to CTXSYS Validate Workflow Run AutoConfig Gather Stats for SYS Grants and Synonyms Fix Syn for Trade Mgmt

Fix Daylight Saving Time Patch 4

Upgrade Database to 11.1.0.7 Use the OH from the 12.1.1 RapidWiz install

OverviewofTechnicalUpgrade
No Start 11.5.9 Or 11.5.10 Yes OATM Enabled Yes Recommended: Convert to OATM Perform steps in Chapter 1 and Chapter 2 Except DB migration DB at 10.2.0.4 or 11.1.0.7 Yes Perform steps1 and 2 In Chapter 3, stop at Step 3 Migrating the DB Downtime starts here Yes Yes Finish Chapter 3 Perform the Upgrade Apply 12.1.1 patch Finish the Upgrade Finish Chapter 4 Post Upgrade Steps On-line Help patch Downtime ends here Upgrade DB to 10.2.0.4 or 11.1.0.7 Use the Rapidwiz 11.1.0.7 Oracle Home Apply DB Patches Upgrade Finished No Recommended Option to Upgrade DB To 11.1.0.7 Upgrade to 11.5.10.2 This guide assumes we start with 11.5.10.2

No

DB at 10.2.0.4 or 11.1.0.7 No

All DB patches are applied

OATM Enabled? No Yes Required: Convert to OATM

No

UpgradeTimeframe
Typically,theupgradetoRelease12.1from11.5.10.2willrequirea 3to4dayweekendfordowntime,startingatthecloseofbusiness onWednesdayorThursday,fora3or4daydowntimewindow. Thedatabaseupgradegenerallytakes8to12hours,Ifthedatabase upgradeiscompletepriortoupgradeweekend,itspossibletodoa 2dayapplicationsupgradefrom11.5.10.2. Thedatabaseupgradecanbecompletedindependentofthe Release12.1applicationsupgradeandifpossible,shouldbe completedweeksormonthsbeforetheRelease12.1.1Upgrade. TheApplicationsportionoftheupgradewilltake14to32hours dependingonthespeedoftheserverandtheamountofdatato upgrade.Testingwilltake812hours,aftertheupgradeis complete. Backupscanbetimeconsumingandrecoveryshouldbetested beforetheupgradeweekend.

UpgradeDowntimewDBUpgrade
Thursday 8AM Friday 9206 10203 Database Upgrade 10203 11107 Database Upgrade Saturday Sunday Backup Monday

12Noon R12.1 Upgrade

Destructi ve Testing

GoLive!

5PM

12Midnight

Cloneto Upgrade Machine Start Database Upgrade

Start R12.1 Upgrade

Restore fromthe Backup ApplyOn lineHelp Patch

UpgradeDowntimewoDBUpgrade
Friday 8AM Saturday Sunday Backup Monday

12Noon R12.1 Upgrade

Destructive Testing Cloneto Upgrade Machine StartR12.1 Upgrade

GoLive!

5PM

12Midnight

Restore fromthe Backup ApplyOn lineHelp Patch

UpgradeWeekend
StartUpgradeonFridayAfternoon CloneUpgradeinstancefromPROD 2hours PerformCategory1Steps 4hours PerformCategory2Steps 6hours PerformCategory3Steps 18hours PerformCategory4Steps 8hours
Customizations 4hours Setups 4hours iSupplier/SSL 4hours

PerformCategory5Steps 4hours
DeveloperTesting

BackuptheUpgradedinstance 2hours UserAcceptanceTesting 8hours RestoretheBackupifTestingwasdestructive

PlantoUpgrade
ProcureUpgradeHardware CreateUpgradedInstanceforGapAnalysis IdentifyCurrentIssues PerformUpgradeAssessments: Functional Customization Architecture Capacity

AssessmentMethodology
Investigate FunctionalApplication Tuning Systemsetupaffects performance ImproveFunctional Processes ReviewUserDefined Functions ReviewFastFormulas Audit IdentifyCurrentIssues DocumentAsIs Processes DocumentToBe Processes

Audit
Report Definethe Issues Recommend Solutions Summarize Improvements

Detailed Assessment

Investigate

Report

FunctionalAssessment
Audit UnderstandtheSystemArchitecture ModulesinUse ModulestobeImplemented IdentifyBusinessIssues Identify&PrioritizeBusinessGoals Clearlydefinedandmeasurable SetPerformanceTargets PrioritizeGoals

FunctionalAssessment Audit
Identifythegapsbetweenthecurrentreleaseandthenew R12.1releasetodeterminefunctional,platform,network andoperatingsystemgaps.Functionalexpertsarerequired tomapcustomprocessesfrom11itoR12.1.Becauseof newfunctionalityinR12.1,existingcustomprocessesmay bereplacedbynewfunctionalityinR12.1. Assessthedatabase,reportingandinterfacetransition issues Evaluatemanagementcontrolsrequired:timing,resources andtrainingissues Recommendanapproach(Upgradevs.ReImplementation)

PlantoUpgrade
OrganizeExecutiveSponsorsandSuperusers IdentifyandPrioritizeUpgradeDrivers:
Implementfunctionalnewfeatures, Moreefficientprocessing, ChangeChartofAccounts, Consolidationtoasingleglobalinstance

Understandthehardwarerequirementsand theupgradepath

R12.1UpgradeCategories
1. PlantoUpgrade 2. PreparetoUpgrade 3. PerformtheUpgrade 4. FinishtheUpgrade

PreparetoUpgrade
PracticeTesting DedicateTestingResources IdentifyandDocumentCustomizations GapAnalysis First,theSuperusersneedtraining WhenareweReady? YournotReadyuntilyourReady Anupgradeisaniterativeprocess

Arewethereyet?
Agoodplan,violentlyexecutedtoday,is betterthanaperfectplannextweek. GeorgeS.Patton Wearereadywhen:
BusinessprocessesalignwithOracleApplications Customizationssupportthebusinessprocesses Usersarefamiliarwiththenewfunctionalityand havebeentrained Testingindicatesallprocessesarefunctioning

The Evolution of the R12 Upgrade process Its an iterative approach

Evolve
Evolve IncorporateR12NewFunctionality ReplacecustomizationswithR12 NewFunctionality PerformBusinessProcessGap Analysis EnableEBSUsers

Manage

Optimize
Optimize ReduceDowntime ImproveUptime ImproveReporting ImproveResponse ReduceCosts ImproveVisibility IncreaseProductivity

Manage AlignBusinessProcesseswithOAR12 SetProcessExpectations ProvideTraining MigrateCustomizationstoSOA ImplementComprehensiveBusiness Reporting

UpgradeIterations
TEST
RapidInstall12.1AppsTier TestandFix

1st Pass

R12.1AppsTier

Customizations

Fixes

Test

2nd Pass

R12.1AppsTier+

Customizations

NewFixes

Test

Performance

R12.1AppsTier++

NoNewIssues

Upgrade Iterations

PreparetoUpgrade
MaintenanceWizard(215527.1)
Stepbystep,graphicaluserinterfacefor performingupgradetasks Consolidatesinstructionsfrommultiplesourcesto presentacomprehensiveupgradepicture Reducesupgradetasksbyfilteringoutthosethat donotapplytoyou(usingTUMS) Indicatescriticalpatchesthatyoursystem requires Canautomaticallyexecuteupgradetasksforyou

PreparetoUpgrade
Ifpossiblecompletethefollowingpriortothe R12.1upgradeweekend:
UpgradetheDatabaseto11.1.0.7 MigratetoOATM InstalltheR12.1software RunDowntimeReducingsteps Runpreupgradeverificationsteps

R12.1UpgradeCategories
1. PlantoUpgrade 2. PreparetoUpgrade 3. PerformtheUpgrade 4. FinishtheUpgrade

PerformtheUpgrade
PerformingtheUpgradeisnotiterative Theproductionupgradeshouldworkpredictably Whathappensifitfails? Testing,Upgradechecklists Planforasecondaryupgradeweekendcontingency IftheUpgradefails,youhaventpracticedenough. Lookatfailedupgradesasforcedpractice.
Thatwhichwepersistindoingbecomeseasier,notthatthetask itselfhasbecome easier,butthatourabilitytoperformithasimproved. RalphWaldoEmerson(1803 1882)

R12.1UpgradeCategories
1. PlantoUpgrade 2. PreparetoUpgrade 3. PerformtheUpgrade 4. FinishtheUpgrade

FinishtheUpgrade
PerformtheTesting

OverviewofTechnicalUpgrade
Start 11.5.9 Or 11.5.10 Yes No Recommended: Convert to OATM Perform steps1 and 2 In Chapter 3, stop at Step 3 Migrating the DB Downtime starts here DB at 10.2.0.4 or 11.1.0.7 No Upgrade DB to 10.2.0.4 or 11.1.0.7 Use the Rapidwiz 11.1.0.7 Oracle Home Yes All DB patches are applied No Downtime ends here Apply DB Patches Upgrade Finished Yes Finish Chapter 3 Perform the Upgrade Apply 12.1.1 patch Finish the Upgrade Finish Chapter 4 Post Upgrade Steps On-line Help patch OATM Enabled Yes Perform steps in Chapter 1 and Chapter 2 Except DB migration DB at 10.2.0.4 or 11.1.0.7 Yes No Recommended Option to Upgrade DB To 11.1.0.7 No Upgrade to 11.5.10.2 This guide assumes we start with 11.5.10.2

OATM Enabled? No Yes Required: Convert to OATM

CPCs,UPCs,CPUs,PSUs
SeeMyOracleSupportKnowledgeDocument 557869.1,EBS:R12OracleFinancialsCriticalPatches forlinkstothelatestCriticalPatchCollections(CPCs) andUpgradePatchCollections(UPCs). Anewtypeofpatchcollectionwasintroducedin July,2009calledPatchSetUpdates(PSUs).SeeMy OracleSupportKnowledgeDocument854428.1, IntrotoPatchSetUpdates(PSU) formoredetails aboutPSUs. OraclealsoreleasesquarterlyCriticalPatchUpgrades (CPUs)thatshouldbeappliedastheybecome available.

CriticalPatchCollections(CPCs)
OracleFinancialsRelease12.0CriticalPatchCollections (CPC)areconsolidatedcriticalpatchesthatallRelease 12.0OracleFinancialscustomersmust applytoensure properoperationsoftheirsystems.CPCsarespecifically targetedforOraclePayablesandReceivables,and includedependentfixesforSubledgerAccounting,Tax, andPayments.AdvantagesofapplyingCPCsoverone offfixesandRUPsareasfollows: CPCsarefullyqualityassuredagainstcurrentRUPlevels. Individualoneoffpatchesarenot.

CriticalPatchCollections(CPCs)
CPCsareconsolidatedandonlycontaincriticalpatchesthat applytobroadcustomerusages.Theyaresmallerinfootprint andthereforemucheasiertoapplyanduptakethanRUPs. CPCReadmeshavedetailedbusinessandfunctional informationaboutthefixesincluded.Customerscanleverage theReadmestodetermineimpactandtestingrequiredfor specificprocessflowsandsoftwarecomponentsinvolved. WedidnotspotanyCPCsforRelease12.1asofNovember, 2009,butyoushouldcontinuetocheckbeforefinalizingyour upgrade.IfaCPCbecomesavailableafteryoucompleteyour upgrade,youshouldresearchtheCPCandconsider implementingitatsomepointtoyourenvironment.

Release12.1FinancialsUpgrade PatchCollection(UPC)
ThelatestRelease12.1FinancialsUpgradePatchCollection (UPC) containsRelease12.1Upgradepatchesforthefollowingproducts:
Payables Receivables Tax SubledgerAccounting Intercompany FinancialsForIndia

TheRelease12.1FinancialsUpgradePatchCollectioniscreated specificallyforcustomerswhohaveyettoupgradetheirproduct environmenttoRelease12.1. ThisUPCcontainsimprovementsto theupgradeprocesstoRelease12.1.

Release12.1FinancialsUpgrade PatchCollection(UPC)
Thesefixesarenotrequiredtobeappliedto environmentsthathavealreadybeenupgradedto Release12.1. Thesepatchesarecriticaltotheupgradeprocessandit isessentialthattheyareappliedtoyourApplications CodeTree(APPL_TOP)priortorunningtheR12.1 UpgradeDriver. ThelatestpatchasofNovember,2009,isPatch: 8773483:R12 .FIN_PF.B,referencedinMyOracle SupportKnowledgeDocument880275.1. YoushouldlookforthelatestUPConMyOracle Supportandaddittoyourupgradeplan.

CriticalPatchUpdates(CPUs)
ACriticalPatchUpdate(CPU)isacollectionofpatchesformultiple securityvulnerabilities.Italsoincludesnonsecurityfixesthatare required(becauseofinterdependencies)bythosesecuritypatches. CriticalPatchUpdatesarecumulative,exceptasnoted,buteach advisorydescribesonlythesecurityfixesaddedsincetheprevious CriticalPatchUpdate.Thus,priorCriticalPatchUpdateAdvisories shouldbereviewedforinformationregardingearlieraccumulated securityfixes. CriticalPatchUpgrades(CPUs)arereleasedquarterly.Whenyou upgradetoRelease12.1.1,youshouldplantoapplythelatest availableCPU.ThelatestasofNovember,2009istheOct2009,Rev 1,20October2009.YoushouldlookforthelatestCPUonMy OracleSupportandaddittoyourupgradeplan.Werecommend applyingtheCPUpatchesonanotherweekendfollowingthe upgrade.However,iftimeallowsontheR12.1upgradeweekend,it ispossibletoapplythelatestCPU .

PatchSetUpdates(PSUs)
PatchSetUpdates(PSUs)aredatabasepatches.ThePSUstategyis todeliverlowrisk,highvaluecontentthathasalimitedscopeand isthoroughlytested. AccordingtoMyOracleSupportKnowledgeDocument854428.1, IntrotoPatchSetUpdates(PSU): PatchSetUpdates(PSUs)areproactivecumulativepatches containingrecommendedbugfixesthatarereleasedonaregular andpredictableschedule.PSUsareonthesamequarterlyschedule astheCriticalPatchUpdates(CPU),specificallytheTuesdayclosest tothe15thofJanuary,April,July,andOctober. ThePatchSetUpdatesforDatabase10.2.0.4andDatabase11.1.0.7 eachincludeaClusterReadyServices(CRS)patch.Likethe Databaseserverpatch,theCRSpatchisawelltested,lowrisk patchofrecommendedfixes.

DatabasePSUs
Oracle Database PSU Unix Patch 11.1.0.7.1 11.1.0.7.1 for CRS Patch 8833297 Patch 8287931 Originally released as CRS bundle #1 Comments

10.2.0.4.2 10.2.0.4.2 for CRS

Patch 8833280 Patch 8705958

PSUs
ThefollowingPSUsareplannedforthenext PatchSetUpdaterelease(January2010):
Database10.2.0.4.3 Database11.1.0.7.2 CRS11.1.0.7.2 EnterpriseManagerGridControl OMS10.2.0.5.2 EnterpriseManagerGridControl Agent10.2.0.5.2

ForthepurposesofourVisioninstanceupgrade, weneedtoaddeitherPatch8833297 forRDBMS Version11.1.0.7.1,orPatch8833280 forRDBMS Version10.2.0.4.2toourupgradeplan.

OptimalNumberofWorkers
Inourupgrademachinesthereare4CPUs.Withtimingdatafrommorethan30 upgrades,thetimesweremeasuredandthenumberofworkerswas varied from2to16.Thefastestupgradetimeswerefor3workers. SetthenumberofworkerstoCPUs 1 Foramachinewith16CPUs,then,wewoulduse15workers. Myreasoningforthisruleisasfollows: Patchesrunjobsthataredependent.Whentoomanyjobsarerunningin parallel,itiseasiertogetthejobsoutoforder,andmorejobswillbedeferred. Deferringjobscausesmoremanagementoverhead. Therefore,byrunningonelessworkerthanCPUs,theoperatingsystemCPU requirementsandotherCPUusageattributedtooverheadfordeferralsarefree torunontheavailableCPUandshouldnotdisturbtherunningworkers.

OptimalNumberofWorkers
OracleRecommends: Todetermineoptimalnumberofworkers,testwiththe followinggoals: Between1*CPUsand1.5*CPUs AverageIOresponsetimesbelow1015milliseconds AverageCPUusagebelow100%

Optimizeadpatch
UseTUMStoeliminatethetasksthatarenotrelevant foryoursystem UseSharedfilesystemforMultinode UseDistributedADforMultinode Estimatetablespacesizesfortestupgradeusing Note:399362.1 Chooseproperbatchsize Batchsize=10000

TuningtheUpgrade
timeadpatch defaultsfile=$APPL_TOP/admin/VIS/adalldefaults.txt logfile=adpatch.logpatchtop=$AU_TOP/patch/115/driver workers=3interactive=yesoptions=novalidate, nocopyportion,nogenerateportion

Otheroptions: nocompiledb,nocompilejsp,noautoconfig

AutoConfiginParallelModeAcross MultipleNodes
TheabilitytorunAutoConfiginparallelacrossmultiplenodeswas introducedintheTXK12.1.1ConsolidatedPatch.Thisfeaturereduces maintenancedowntime. AutoConfigcanberunin'parallelmode'byissuingthefollowingcommand: OntheApplicationstier: perl<AD_TOP>/bin/adconfig.plcontextfile=<CONTEXT_FILE> [product=<product_top>]parallel OntheDatabasetier: perl<ORACLE_HOME>/appsutil/bin/adconfig.pl contextfile=<CONTEXT_FILE> parallel WhenrunningAutoConfigsimultaneouslyonmultiplenodes,the'parallel' optionmust bespecifiedwhilestartingAutoConfigonevery node. Otherwise,theexecutionofAutoConfigprocessesonindividualnodeswill notbesynchronized,andmayresultinaninconsistentfilesystemor database.

AD_TASK_TIMING
JOB_NAME adobjcmp.sql adobjcmp.sql adsstats.sql adstatrp.sql adpcpcmp.pls adpcpcmp.pls adobjcmp.sql adpcpcmp.pls invmenu.ldt ontmenu.ldt afoamadmmenu.ldt ozfmenu.ldt akdatsb1.drv oksmenu.ldt fndwfusermenu.ldt iexmenus.ldt PRODUCT ad ad ad ad ad ad ad ad inv ont fnd ozf ak oks fnd iex PROGRAM AutoPatch AutoPatch AutoPatch AutoPatch AutoUpgrade AutoUpgrade AutoPatch AutoUpgrade AutoPatch AutoPatch AutoPatch AutoPatch AutoUpgrade AutoPatch AutoPatch AutoPatch AutoPatch AutoPatch AutoPatch AutoPatch PHASE 27 79 346 346 12 12 346 12 41 41 41 41 20 41 41 41 41 25 41 2 elapsed time -hrs 5.652222222 2.133611111 1.908888889 1.908888889 1.842222222 1.768611111 1.758055556 1.656944444 1.288333333 0.978888889 0.870555556 0.806111111 0.802222222 0.783055556 0.598333333 0.523055556 0.4675 0.419166667 0.419166667 0.412222222

systemadministratormenu.ldt fnd fem_xdmi.odf oamdiagbasemenu.ldt bermind.sql fem fnd ben

TuningtheUpgrade
Makesureyouresetthefollowinginit.oraparametersaftercompletionofR12upgrade driver recyclebin parallel_max_servers job_queue_processes MergealltheNLSpatchesandapplythemassinglemergedpatch Isolatepostupgradeconcurrentprogramstoaseparatemanagerqueueas mentionedinthebestpracticesDocid:399362.1 Gatherstatisticsbeforeupgrade UseGatherAutooptionat10g Recordtimingforeachstepduringtestupgrade DropMRCschemabeforeR12upgrade AddPL/SQLnocompileoptioninR12upgradedrivertosavetimeduringupgrade Addextensionplsql_nocompileyes lineinupgradedriverfiletoenablePL/SQLno compileoption

Reducing Downtime
JOB_NAME facpupg.sql PRODUCT FA PROGRAM PHASE elapsed time -hrs AutoPatch AutoPatch 245 244 0.005277778 0.010833333

glrsgup2.sql GL

Fixed Assets has a potentially long running sql script, facpupg.sql. The script is run by AutoPatch (adpatch) and takes about 19 seconds to run. The script takes so little time to run that it should be run during the downtime window and would not save a significant amount of downtime if run in advance.

UpgradebyRequest
Upgradethemostimportantdata,thelastfiscalyear orotherperiods,duringtheupgradedowntimeand migratetherestofthehistoricaldatalater. TheproductsthatuseUpgradebyRequestare: CustomerRelationshipManagement(CRM) FinancialsandProcurement Projects SupplyChainManagement
SeeMyOracleSupportKnowledgeDocument604893.1,R12:FAQfortheSLA Upgrade:SLAPreUpgrade,PostUpgrade,andHotPatch.

UpgradebyRequest
Historicaldataupgradedependsonproduct.For someproductsonlySLAdatawillbeupgradedandfor others,bothtransactionsandaccountingdatawillbe upgraded. Implementationisatwostepprocess: 1. Setrangeofperiodsofthehistoricaldatatobe upgradedbeforeR12Upgradeandrunpre upgradeconcurrentprogram 2. RunSLApostupgrade(upgradebyrequest option)afterR12upgrade ReviewAppendixGinR12upgrademanualformore details

DefaultUpgradePeriods Minimum DowntimeUpgrade

Duringtheupgrade,existingaccountingdatafromthe subledgers(AR,AP,GL)isupgradedintothenew OracleSubledgerAccounting(SLA)datamodel. Bydefault,theupgrademigratesdataforthecurrent fiscalyearandtheperiodsofthepreviousfiscalyear thatarenecessarytoensurethereareatleastsix periodsintheupgrade(iftheupgradeisperformedin thefirsthalfofthefiscalyear).

InstalltheSLAPreUpgrade ConcurrentProgram
Tochangethedefaultnumberofperiodsofhistoric datatobeupgraded: ApplyPatch5233248 toyourRelease11iAPPL_TOP SubmittheSLAPreUpgradeConcurrentProgram

RuntheSLAPreUpgrade ConcurrentProgram
Whensubmittingthisprogram,enterthefollowingparameters: MigrateallSetsofBooks:
Yes(SLAPreUpgradeprogramupdatestheperiodsinallSetsofBooks) or No(SLAPreUpgradeprogramupdatestheperiodsthatbelongtothe selectedSetofBooks). SetofBooks:SetofBookstobeupgradedwhereyouhaveselectedto upgradeoneSetofBooks.

StartDate:Dateusedtodeterminethefirstperiodtobeupgraded.The
firstperiodisthefirstperiodtheStartDatefallsin;itdoesnothavetobe thestartingdateofthefirstperiod. Thestartdatecanbechangedtoadateearlierthanthe6months minimum,butnotshortenedtolessthanthedefault.

RuntheSLAPreUpgrade ConcurrentProgram
YoumayneedtoruntheSLAPreUpgradeprogramifyouare usingOracleGeneralLedgerandatleastoneofthefollowing subledgers: Assets CostManagement Payables Receivables Purchasing ProjectAccounting Thisoptionalprogramallowsyoutochangethedefault numberofperiodsofhistoricdatatobeupgraded.

RuntheSLAPreUpgrade ConcurrentProgram
TheRelease12SLAPreUpgradeprogramconsidersthe followingmodules: Payables Receivables Purchasing ProjectAccounting Inventory/Costing FixedAssets(FixedAssetsusesGLperiods)

SLAPreUpgradeprogram
TheSLAPreUpgradeprogramusestheGL_PERIOD_STATUSES table.The MIGRATION_STATUS_CODEcolumnindicatesthe statusoftherecordintheGL_PERIOD_STATUSEStable: P=PendingUpgrade Thesystemispreparingtoupgradethe accountingperiodsinthistablethathaveastatusP.The accountingtransactionsinthesecorrespondingaccounting periodswillbeupgradedfromRelease11itoRelease12bythe Subledger products(i.e,AR,APetc). U=Upgraded Theaccountingrecordshavebeenupgradedfrom Release11itoRelease12 N=New OnlyusedbyGL <blank>=Theserecordsdonotmeetanyofthecriterion mentionedandwillthereforenotbeconsideredintheupgrade.

SLAPreUpgradeProgram
TheparametersfortheSLAPreUpgradeprogramare: UpgradeallSetsofBooks,or ThespecificSetofBooksandtheStartDate. TheRelease12SLAPreUpgradeProgramtagstheaccounting periodsintheGL_PERIOD_STATUSEStablewithPforpending upgradewhentherecordsareforAP,AR,ProjectAccounting,FA, Inventory/CostingandPOproductsonly. Nootherproductsareconsideredbythispreupgradeprogram

AdjustmentPeriods
TheaccountingperiodunderconsiderationmustbeaNON Adjustmentperiod. Adjustmentperiodsarenotupgradedbecausetheupgradethat wasdesignedbytheSubledger Productteams(AP,ARetc)catersto thetransactionscreatedbythoseproductsandpostedtoGL. Typically,theSubledger Productteamsdonotgenerate transactionsthatpostintoadjustingperiods.Giventhatadjusting periodsoverlapdateswithnonadjustingperiods,thelogicfor mappingatransactionintoanaccountingperiodistotaketheGL dateandfigureoutwhichnonadjustingperioditfallsinto. Theperiodhasastatusofclosed,open,future,andneveropened. Note:Never openedisonlyapplicabletotheInventory/Costing product.

SLAPostUpgradeProcessing
UpgradebyRequest Ifyoudonotperformacompleteupgradeoftheaccounting data,OracleSubledger Accountingallowsyoutoperforman additionalupgradeofthedatabyrunningtheSLApost upgradeprocessConcurrentProgramwheneverthemissing dataisrequired.

RunAccountingReports YoushouldruntheGlobalAccountingEngineaccountingreportsbeforetheupgrade andthecorrespondingSubledger accountingreportsaftertheupgradetoensurethat youhaveaproperaudittrailoftheupgradedaccountingdata.Thereportsareasfollows: GlobalAccountingEngine DailyJournalBook AccountLedgerbyAccount SupplierandCustomerSubledger byAccount SupplierandCustomerBalance Subledger Accounting DailyJournalReport Account AnalysisReport ThirdPartyBalancesSummary

GlobalAccountingEngineVerification Tasks

ThirdPartyDetailandBalancesbyAccountReport

EBusinessVerificationTasks
EBusinessTaxVerificationTasks TaxTransactionAuditandReconciliationReports Toensurethattransactiontaxinformationhasbeencorrectlyupgraded,run thePayablesTaxAuditTrailreportandtheReceivablesTaxReconciliation reportforthecurrenttaxperiodbeforetheupgradetosetabenchmarkof transactioninformation.Thenimmediatelyaftertheupgrade,run thesame reportsinthenewenvironmentforthesameperiodandcomparethe resultstoensurethatthetaxvaluesarestillthesame. PayablesandReceivablesTransactionQuery ForasampleofPayablesandReceivablestransactions,recordthedetailsof theassociatedtaxforthesetransactionsbeforemigration,andthenquery themagainaftertheupgradetoensurethatthetaxhasbeencorrectly upgraded.Duplicatethesametransactionsandretriggertoensurethatthe newEBusinessTaxbasedcalculationisconsistentwiththeprevious calculation.

PaymentsVerificationTasks
LegalEntityConfigurator VerificationTasks LegalEntitiesandEstablishments Youshouldperformareviewofalllegalentitiesandestablishmentsinyour systemaftertheupgradeiscompletetoensurethatthecorrectlegal structureisinplace.YoucanaccessthisinformationbyusingtheSearch PageintheLegalEntityConfigurator. RefertotheOracleFinancialsandOracleProcurementFunctionalUpgrade Guide:Release11itoRelease12. Ifyouneedtocreateorupgradelegalentitiesandestablishments,thensee theOracleFinancialsImplementationGuide forinstructions.

PaymentsVerificationTasks
PayablesVerificationTasks TrialBalanceReconciliation InyourRelease11i environment,runtheAccountsPayable TrialBalance,PostedInvoiceRegister,andPostedPayment Registerreports.Aftertheupgrade,runtheOpenAccount BalancesListingReport,PostedInvoiceRegister,andPosted PaymentRegisterinyourupgradedenvironmentand comparetheresults. Thereportsrunforaledgeroraledgerset,notwithinthe contextofasingleoperatingunit.TheRelease11iTrial BalanceandPostedInvoiceandPaymentRegistersrun withinasingleoperatingunit.Dependingonyoursystem configuration,youmayneedtosumseveralofthe11i reportstotietothenewversions.

PayablesVerificationTasks
PayablesVerificationTasks InvoiceandPaymentProcessing ToverifytheintegrationwithOraclePaymentsandtheupgrade ofexistinginvoices,submitapaymentbatchwithlimited selectioncriteriainordertopayafewinvoices. AccountingSetupandProcessing Queryaninvoicethatwasnotvalidatedpriortotheupgrade, thensubmitaccountingforthatinvoice.Queryaninvoicethat wasaccountedbeforetheupgrade,cancelit,payit,andthen accountforthepayment.AlsoseeGlobalAccountingEngine.

PaymentsVerificationTasks
PaymentsVerificationTasks ThesetasksapplyonlytoOraclePayments.Ingeneral,your planningforupgradeverificationshouldinvolvetestinginthe twopaymentprocessareas: FundsDisbursement IfyouusedOraclePayablesforissuing paymentsinRelease11i,youshouldplantotestthefunds disbursementprocessesequivalenttotheformerpayment batchflowtoensurethatyourupgradeddatacorrectlyreflects yourbusinessprocess.

PaymentsVerificationTasks
PaymentsVerificationTasks FundsCapture IfyouusedOracleReceivablesforelectronic paymentprocessingsuchasdirectdebitsorbillsreceivable remittances,youshouldplanontestingtheseareastoensure thatyourupgradeddatacorrectlyreflectsyourbusiness process. IfyouusedOracleiPayment forcaptureoffundsfromcredit cardsorbankaccountdebits,youshouldplanontestingthese processestoensurethattheupgradeddataresultsinthe processyouexpect.

PaymentsVerificationTasks
PaymentsVerificationTasks SystemSecurityOptions OraclePaymentsprovidesthisnewpagewheresystemlevel settingsforencryption,masking,andcreditcardsecuritycanbe controlled.Whenyourupgradeiscomplete,youshouldplanon reviewingtheseededsettingsinthispagetoensuretheymeet yourbusinessneeds. Forexample,inRelease11i maskingofcreditcardvaluesis controlledindifferentwaysthroughouttheapplications.Inthis release,thecentralsettinginthispagecontrolsallmasking.You willwanttoreviewthesettinginthispageandmodifyitif needed.

PaymentsVerificationTasks
PaymentsVerificationTasks OraclePayablesImpact Youmaywanttorunreportsforuseinyourupgrade verificationtesting. Forexample,youmaywanttousetheSuppliersReportin OraclePayablestoverifythedataupgradeforpaymentdetails andbankaccountsonthepayeescreatedinOraclePayments. Youcanuseanyreportsthatyouranbeforetheupgradetohelp verifyupgradeddata.

PaymentsVerificationTasks
PaymentsVerificationTasks Inaddition,therearesomekeysetupentitiesthatshouldbe reviewedandusedintestingpaymentprocessing. PaymentProcessProfiles Youshouldplanonreviewingthe settingsfortheseededprofilescreatedbytheupgrade.These settingscomefromavarietyofsources,andsincetheprofile drivestheentirefundsdisbursementflowitisimportantto verifythatthesetupsupportsyourbusinessprocess.Youshould payspecialattentiontotheusagerulessetontheseeded profilesasthesecanbechangediftheupgradedvaluesdonot alignwithyourneeds.Itisrecommendedthatyourunatest paymentprocesswitheachprofilethatyouplantousein production.

PaymentsVerificationTasks
PaymentsVerificationTasks PaymentMethods Anewsetuppageisprovidedwhere paymentmethodscanbecreatedorupdated.Youshouldplan onreviewingthepaymentmethodsseededbyOraclePayments toensurethattheymeetyourbusinessneeds. PaymentSystemsandAccounts Youshouldplantoverify theseentitiesaftertheupgrade,andinparticulartherequired settings,values,andtheirlinkstothepaymentprocessprofiles. Thissetupcontrolsimportantpartsofthefundsdisbursement processsuchaspaymentfiletransmission,soyoushouldtest thisareatobesurethattheprocessisworkingasyouexpect.

Questions
Thanks Thepaper/presentationisavailableat: www.trutek.com mswing@trutek.com

SharedServices
Servicescanbesharedatmanydifferentlevels,and sharedservicecenterscanexistfordifferent reasons.
Orderdesks, ReportingCenters, GeneralLedgerCenters, DisbursementCenters, InventoryManagementCenters, ProcurementCenters.

Manyofthesecentersmaybecombinedasone center.

IntegratedFinancials
Thenewbankaccountanddisbursementmodelsfacilitatethepaymentof invoicesandotherpayablesoutofdifferentoperatingunits,froman appropriatebankaccount,andwiththeappropriateintercompany handling. Intercompanyprocessingisdramaticallyrevisedbyenhancementsinboth Financials intercompanymanagementandSupplyChainManagements EnhancedDropShipments.
RatherthanaGLonlysystem,FinancialsnowlinksintoReceivablesand Payablestogeneratematchingandtieddocuments(configurablethoughBill Presentment)andanewreconciliationscheme.

RelatedSCMproductsprovidetransferpricingmodelingand enforcement,inventoryconsignment(atsubsidiariesorotherwise),and trackingofprofitininventory. AllfeedbacktoGeneralledgerandtheFinancialConsolidationHubfor elimination.

Subledger Architecture
ASetofBooks(11i)becomesaLedgerwithitsown LedgerSet,inRelease12. SLAwillreturnthesameaccountingastheearlier accountingenginedid.OperatingUnitswillstill stripe yourtransactiondata. Benefits:
subledger accounting, XMLpublishingappliedtoreports, additionalDBIportlets andpages, ARAPnetting,and grossmarginanalyticsinAR.

Subledger CurrencyViews
Accountingforsubledger transactionsattheeventinastandardmanner withasingleaccountingengineallowsustoprovidemultipleaccounting representationsforasingleevent. Apurchasecanbesimultaneouslyaccountedforanincrementto inventoryforyourUSGAAPorIAS/IFRSaccounting,andasadebittothe P&Lforyournationalcomplianceaccounting. Theaccountingentityinvolvedcanmaintainmultipleledgers,each complyingwithadifferentsetofaccountingprinciples wecallthem accountingmethods,and,ofcourse,thetransactionsandledgerscanbe valuedanddenominatedindifferentcurrencies; Youcannowgeneratecurrencyviewsofaledgeratthesubledger transaction,generalledgertransaction,generalledgerbalance, or consolidationworkplacelevels.

MultiOrgAccessControl
MultiOrgAccessControlenablescompanieswithaShared Servicesoperatingmodeltoefficientlyprocessbusiness transactionsbyallowingthemtoaccess,processandreport ondataforanunlimitednumberofoperatingunitswithina singleapplicationsresponsibility. ThisincreasestheproductivityofSharedServiceCenters,as usersandprocessesnolongerhavetoswitchapplications responsibilitieswhenprocessingtransactionsformultiple operatingunitsatatime. Datasecurityandaccessprivilegesarestillmaintainedusing securityprofilesthatnowsupportalistofoperatingunits.

TeamObstacles
Infighting:Effectiveteamsdon'thavetobemadeup ofpeoplewholikeeachotherbuttheremustbe respectforeachother
misdirectedenergytobickeringandundermining colleagues membersmustbewillingtosetasidepettydifferences

ShirkingofResponsibilities Whenmembersavoid takingresponsibilityforbothprocessorrunningofa groupandforspecificassignments,ateambecomes a"pseudoteam";i.e.,teaminnamebutconsistently underperforming.

TeamObstacles
LackofTrust Iftrustislacking,membersare unabletodependoneachother. CriticalSkillGaps Whenskillsarelacking, teamsflounder,membershavetrouble communicatingwitheachother,destructive conflictsresult,decisionsaren'tmade,and technicalproblemsovercomethegroup

Teamwork
Teamwork istheconcept ofpeopleworking togethercooperatively,asinasports team. Manylarge,ambitiousprojectsusuallyrequirethat peopleworktogether,soteamworkhasbecomean importantconceptinorganizations. Industryhasseenincreasingeffortsthroughtraining andcrosstrainingtohelppeopletoworktogether moreeffectivelyandtoaccomplishsharedgoals, whethercolleaguesarepresentorabsent.

TeamDevelopment
Asteamsgrowlarger,theskillsandmethodsthat peoplerequiregrowasmoreideasareexpressed freely. Theintimacyofasmallgroupislost,andthe opportunityformisinformationanddisruptive rumorsgrows. Specifically,leadersmightencounterdifficulties basedonDaglow's LawofTeamDynamics:"Small teamsareinformed.Bigteamsinfer."