02 - HCM Cloud Service Overview2

Partner Boot Camp
Fusion HCM Global HR

HCM Cloud Service Overview

Instructor Guide

August 12, 2013

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Disclaimer

This document contains proprietary information and is protected by copyright and
other intellectual property laws. You may copy and print this document solely for
your own use in an Oracle training course. The document may not be modified or
altered in any way. Except where your use constitutes "fair use" under copyright law,
you may not use, share, download, upload, copy, print, display, perform, reproduce,
publish, license, post, transmit, or distribute this document in whole or in part without
the express authorization of Oracle.

The information contained in this document is subject to change without notice. If
you find any problems in the document, please report them in writing to: Oracle
University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This
document is not warranted to be error-free.

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using
the documentation on behalf of the United States Government, the following notice
is applicable:

U.S. GOVERNMENT RIGHTS
The U.S. Governments rights to use, modify, reproduce, release, perform, display,
or disclose these training materials are restricted by the terms of the applicable
Oracle license agreement and/or the applicable U.S. Government contract.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other
names may be trademarks of their respective owners.

i
CONTENTS
Lesson 1: HCM Cloud Service Overview ....................................... 1
Objectives ................................................................................................. 1
Oracle Fusion HCM Cloud Service ................................................................. 2
Oracle Cloud .............................................................................................. 3
Common Infrastructure Services ................................................................ 5
Customer Cloud Service Lifecycle (OC Release 13.2/FA Release 7) ................... 6
Key Differences between Cloud Deployment and On-premise ........................... 7
Oracle Cloud Security Practices and Policy Documents .................................... 8
Fusion Applications Cloud Service Options ..................................................... 9
Oracle Cloud Change Management ............................................................. 10
Oracle Fusion HCM Cloud Service Patching and Upgrades .............................. 11
Upgrades .............................................................................................. 13
Customer Benefits of Oracles Cloud Upgrade Solution ................................ 15
Upgrade Cadence Model .......................................................................... 16
Upgrade Cadence Model: Worked Example .............................................. 17
Special Upgrade Considerations ............................................................... 18
Recommended Customer Upgrade Validation Procedures ............................ 19
Oracle Cloud Environment Management ...................................................... 21
Available Environments ........................................................................... 22
Environment Management Services and Tools ........................................... 23
Content Migration Solutions..................................................................... 24
Test-to-Production Migration ................................................................. 25
Production-to-Test Migration ................................................................. 26
Setup Migration through FSM .................................................................. 27
HCM Setup Migration ............................................................................ 28
Extensibility Migration ............................................................................ 29
HCM Implementation Lifecycle ................................................................. 30
Content Migration within the HCM Implementation Lifecycle ...................... 31
Initial Implementation .......................................................................... 32
Initial Implementation Process .......................................................... 33
Add-on Implementation ........................................................................ 34
Add-on Implementation Process ........................................................ 35
Oracle Cloud Backup Policies ..................................................................... 36
Oracle Cloud Disaster Recovery Objectives .................................................. 37
Know How to Work with Oracle SaaS .......................................................... 38
There are no demonstrations or activities for this lesson ............................... 39
Lesson Highlights ..................................................................................... 40

Lesson 1: HCM Cloud Service Overview

Copyright 2013, Oracle and/or its affiliates. All rights reserved. 1
Objectives

This lesson introduces you to Oracle Cloud and Oracle Fusion HCM Cloud
Services.

In this lesson you will learn about:
Oracle Fusion HCM Cloud Service
Oracle Cloud (OC)
OC framework and common infrastructure
Customer Lifecycle with OC
Key differences between OC and on-premise deployments
OC security practices and policy documents overview
Oracle Fusion HCM Cloud Service patching practices
Oracle Fusion HCM Cloud Service upgrade practices
Oracle Fusion HCM Cloud Service environment management guidance
OC backup policies and disaster recovery objectives

2 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Oracle Fusion HCM Cloud Service

The Oracle Fusion HCM Cloud Service delivers a complete HCM solution which
includes the following:
Global HR
Payroll
Compensation
Benefits (included with a subscription to Global HR)
Workforce Predictions
Workforce Lifecycle Manager
Succession and Talent Review
Performance Management
Goal Management
Taleo Recruiting
Taleo Learn
This service helps drive better resource plans, employee alignment, and regulatory
compliance with integrated enterprise social networking tools, business intelligence, and
mobile data access.



Oracle Cloud

The Oracle Cloud (OC) is composed of three service types:

Application Cloud Service (SaaS)
HCM Cloud Service
Talent Management Cloud Service
CRM Cloud Service
ERP Cloud Service
Other services will be integrated into OC over time (For example, Taleo)

Platform Cloud Service (PaaS)
Java Cloud Service
Database Cloud Service
Infrastructure Cloud Service (IaaS)
Future Services: Messaging, Storage

All services within the OC are managed by a common infrastructure.


Common Infrastructure Services

Primary components of this framework include:
Cloud User Interface (cloud.oracle.com): Prospect/customer-facing UI up to
and including customer service activation

Cloud Portal (cloud.oracle.com): Customer-facing UI post service activation

Tenant Automation Service (TAS)/Service Deployment Infrastructure (SDI)
(internal Oracle systems, not exposed directly to customers): Management and
provisioning of customer environments

Shared Identity Manager (IDM): Management of logon credentials across all
Cloud Services

Enterprise Manager (EM) (internal Oracle systems, not exposed directly to
customers): Data center management of Cloud Services, used by CloudOps


Customer Cloud Service Lifecycle (OC Release
13.2/FA Release 7)



Key Differences between Cloud Deployment and On-
premise
No access to database to run SQL or any other db commands
No access to JDev or the Skin Editor
Cannot perform Application Development Framework (ADF) customizations
No direct access to Enterprise Manager and Application Server
No ability to develop and deploy custom Java or PL/SQL code
No access to Service-Oriented Architecture (SOA) Suite - ability to develop
/deploy Custom Composite Applications
No access to Oracle Business Intelligence Applications (OBIA) and Data
warehousing; however, users can use Business Intelligence Publisher (BIP) and
Oracle Transactional Business Intelligence (OTBI) for reporting
Cloud customers will not be able to configure new Data Sources and will not get
BI Administrator access
Cloud customers are provisioned two environments (Test and Production).
Additional Test environments can be purchased.



Oracle Cloud Security Practices and Policy
Documents
Oracle Cloud Hosting and Delivery Policies
Oracle Cloud-SaaS Hosting and Delivery Policies
(http://www.oracle.com/us/corporate/contracts/cloud-hosting-delivery-policies-
1881437.pdf) (PDF)
Oracle Cloud-SaaS Enterprise Hosting and Delivery Policies
(http://www.oracle.com/us/corporate/contracts/cloud-ent-hosting-del-policies-
1881438.pdf) (PDF)
Data Processing Service Agreement
Data Processing Agreement
(http://www.oracle.com/us/corporate/contracts/cloud-processing-agreement-
1880936.pdf) (PDF)
Oracle Fusion Cloud Service Descriptions
Oracle Fusion Cloud Service Descriptions
(http://www.oracle.com/us/corporate/contracts/oracle-fusion-cloud-service-desc-
1843611.pdf) (PDF)
All documents are available on Oracle.com/Contracts.
Select Oracle Cloud Services
(http://www.oracle.com/us/corporate/contracts/cloud-services/index.html).
Review cloud specific documents as listed.
Direct questions regarding cloud policies to the global business practices team
for guidance.


Fusion Applications Cloud Service Options

Requested through My Oracle Support (MOS) as Service Requests (SRs)

For details about Fusion Cloud Service options and procedures, see MOS article
#1534683.1.


Oracle Cloud Change Management

Regular Maintenance
Oracle Cloud Operations reserves the following regular maintenance windows targeted
to occur during the statistically lightest utilization period for that deployment region.
Mandatory monthly application patching cycle (For example, Patch Bundles)
cadence is Test environment first followed by production two weeks later
Optional weekly as-needed one-off patching
Optional weekly accumulated one-off patching
4-6 month application upgrade cycle
1 year tech stack and infrastructure upgrade cycle (For example, Exadata,
Exalogic, OS, firmware, switches, load balancers, firewalls, hypervisor, database)
Most maintenance is applied Friday evening through Saturday morning (for each
time zone)
For more information on HCM patch bundles, see MOS article # 1554838.1.

Planned Maintenance
Schedules for planned maintenance may be viewed on the Oracle Cloud Customer
Portal. Oracle will endeavor to provide customers with five business-day advance notice
if a different maintenance window is required. Maintenance extension alerts will also be
posted on the Customer Cloud Portal.

Emergency Maintenance
Oracle will apply emergency maintenance as required to maintain the operation,
security, and performance of the Oracle Cloud services. Emergency maintenance may
include, but is not limited to, the application of patches, configuration changes,
hardware repair, or other required activities.



Oracle Fusion HCM Cloud Service Patching and
Upgrades
Patching
Patch Bundles are applied monthly: 1st Friday on Test and 3rd Friday on
Production
If necessary, technology stack fixes will be applied on the 2nd and 4th Friday of
the month

Oracle offers standard patching and release cycle for SaaS customers. First, patch
bundles are applied to Test environments on the 1st Friday of the month. Then on the
3rd Friday of the month, the same patch bundle is applied to Production instances.
There could be times (for a few weeks) when your Test instance and Production
instance will not be identical from a patch-level standpoint. Functional fixes are applied
during these patch windows.

Remember, though, that Oracle proactively patches. Sometimes the functional patch
window does not afford the opportunity to make non-functional fixes to the tech stack.
To avoid problems across the fleet, Oracle sometimes has to introduce patches to the
tech stack on the 2nd and 4th weeks of the month. We give notice, but the trade off
here is that you will have more reliable, stable environment, but may experience
additional planned outages. This is only done when technical patching cannot fit in the
functional patch windows shown on the slide.

In addition to the monthly patches, we may also have one-off weekly patches consisting
of fixes addressing your critical features, capabilities that impact your project timeline
drastically. We can work with you to identify the one-off patches you need to apply
based on your project needs and plan. If you choose to take up these aggregated one-
off patches, there will be downtime on Wednesday/Thursday to apply these patches in
your Staging environment.

Patching Guidance for Implementation Planning

Plan Go-Lives 1 2 weeks after Monthly Patch Bundle is applied to Production
- Latest fixes applied before Go-Live
- Sync up Prod and Test

Production to Test (P2T) refresh requires same patch level in Prod and Test
- Perform P2T after Monthly Patch Bundle
- Schedule, plan for P2T well in advance


Upgrades

Typically two upgrades are provided each year.
Cloud Fusion Applications release numbers are the same as on-premise.
A Cloud upgrade may include multiple releases.
Oracle communicates logistics and whats new before, during, and after the
upgrade in many forms.
Upgrading HCM Cloud customers occurs over several months:

- Oracle accommodates customers schedules and implementation status
when scheduling an upgrade.
- Customers may defer an upgrade, but must eventually accept it.

Upgrades are applied to Test environments first and, after customer validation, to
Production environments:

- Test environments are upgraded throughout the week.
- Production environments are upgraded during weekends

Customers must plan for and execute upgrade validation.




Customer Benefits of Oracles Cloud Upgrade
Solution
Provides return on customers investments in the HCM Cloud Service
Provides functional and technical enhancements and fixes
- Feature/function improvements
- Usability enhancements
- Technical updates
Re-establishes the baseline for future updates
Eliminates the conventional problem of being stuck with an obsolete software
version


Upgrade Cadence Model



Upgrade Cadence Model: Worked Example



Special Upgrade Considerations

Production-to-Test (P2T) Content Migration
If requested, a copy of Production will be taken and placed on the Test environment first
to simulate future Production upgrade. This will add an estimated 24 hours to the
downtime in Test, depending on the volume of data. Any data in Test will be overwritten.
Customers in production should always migrate their Production environment to the
Test environment as part of the upgrade, unless they have recently done this migration
and are confident that the two environments are closely aligned.

Language Packs
If more than one language pack is currently installed, customers must provide
authorization to apply any additional language packs at the time of the upgrade. There
will be an additional 3-hour outage required for each language pack for both Test and
Production.

Coexistence through HR2HR (for customers subscribing prior to April 2013)
If requesting a P2T as part of customers' Test upgrade, customers will need to
coordinate a copy of their E-business Suite/People Soft (EBS/PS) database as well and
change necessary configurations in the source system before resuming HR2HR use in
Test.

Patching During the Upgrade Window
Prior to starting upgrades for the HCM Cloud Fleet, restrictions will be put in place to
limit patching, to ensure consistency across all customer environments that are being
upgraded.


Recommended Customer Upgrade Validation
Procedures

Develop Upgrade Validation Plan
Review testing plans and scripts originally prepared for the implementation
project to test the same scenarios in the newly upgraded environment.
Review any communications or training materials and guides for feature/function
changes due to the upgrade, to incorporate them into the customer's validation
strategy.
Perform Post-upgrade Validation
Configuration: Review the setup for primary code values, such as Departments,
Locations, Jobs and confirm that all appear to be the same as they were prior to
the upgrade.
Employee Data: Create and run a few simple reports on employees showing
their personnel and assignment information prior to the upgrade. Then run the
same reports again after the upgrade to verify that the information appears the
same as prior to the upgrade.
Reports: Run a few regular reports and confirm they are working correctly.
Integrations: Run a test of each of the customer's integrations to confirm that
they are all working properly.
Security: Sign on to OIM and verify that you can query all of the customers
organizations. Create a new user and assign roles.
Special Considerations
Single sign-on: Verify that you are still able to sign in successfully using
Lightweight Directory Access Protocol (LDAP) accounts.
E-mail notifications: If you previously had email notifications turned off in Test,
you can control this as part of the customers user account settings. Make sure
that you have selected the Suppress User Account and Email Notifications
option in the Manage Enterprise HCM Information task.
Multiple languages: Verify that each of the language packs is still available and
working properly.
Upgrade Problem Reporting
Log a Service Request (SR) through My Oracle Support (MOS), providing as
much documentation as possible including pre-upgrade and post-upgrade
behaviors.
Oracle will provide problem reporting guidelines for each upgrade (For example,
SR naming conventions, problem categorization types to use).

Note: You can use the Oracle Product Features
(https://apex.oracle.com/pls/apex/f?p=24153:100:100491633520435) tool to compare
release features prior to an upgrade.


Oracle Cloud Environment Management

Cloud customers need to know the recommended approach to using the environments
provided to them.
Several factors contribute to recommending a strategy:
Cloud Service Level Objectives and Service Entitlements
Current Service capabilities
Customer project lifecycle: initial implementation versus subsequent
implementation
Customer size and complexity
The guidance will evolve as additional capabilities roll out.


Available Environments

A standard Fusion HCM Cloud Service subscription provides two environments -
Production environment and Test environment.
Production Environment: The production environment is intended to support
the ongoing management of your Fusion HCM Cloud Service applications in
production. Content should not be created in the production environment prior to
going live unless absolutely necessary. Use should be restricted to only
production.

Test Environment: The test environment supports all non-production related
activities for managing the HCM implementation lifecycle. Focus should be on
applying and testing implementation activities prior to putting them into
production. An exception to this is Conference Room Pilot(s).
Customers may purchase additional Test environments for other purposes (For
example, Payroll parallel runs, feature development, familiarization/training, and internal
demos).


Environment Management Services and Tools
P2T Content Migration Utility: Copies Production data to Test
Setup migration through Functional Setup Manager (FSM)
Flexfield Metadata Migration through FSM
Page Composer UI Extensions Migration through Fusion Middleware (FMW)
and/or CSM (Customization Set Migration, new with Release 7)
BI/Reporting Migration through Oracle Transactional Business Intelligence
(OTBI)/ Business Intelligence Publisher (BIP)
Refresh of Test environment: Provides the customer with a new Test
environment
Data load Delete Scripts: Removes bad/incomplete data from tables during initial
implementation (through Oracle Support)


Content Migration Solutions

During your implementation lifecycle, you will migrate content between the Production
and Test environments.

The Content Migration Solutions between Fusion HCM Cloud Service environments are
classified in terms of the direction from which content is migrated.
Test-to-Production (T2P) - Migrations occur for one type of content, such as
business intelligence or functional setup, at a time
Production-to-Test (P2T) - Typically migrates an entire production environment
to test and, in doing so, overlays the entire contents of the test environment



Test-to-Production Migration

The Fusion HCM Cloud Service supports migration of several of the most common
customer configurations from the test environment to the production environment. The
typical use case for such configurations is performing your configurations in the test
environment, validating that you configured them correctly, and migrating them to the
production environment.

Test-to-Production Solutions for Common Configurations



Production-to-Test Migration
Migrates database content from Production to Test
Overwrites Test environment which is unavailable for 1 day
Both environments must be at the same patch level
- Recommendation: Time the P2T right after monthly Production patch bundle
Service is on request
- Recommendation: Get on the P2T schedule well in advance
Production user definitions are migrated
- Typically, Production users should not access Test
- Test users must be recreated
Content Migrated
1. All transaction data and functional setup data in the Fusion Applications schema
2. File attachments (for example, agreements, orders) stored in Universal Content
Management (UCM)
3. Flexfield customizations
4. Metadata Services (MDS) customizations (for example, Oracle Composer
changes)
5. BI Web Catalog and Repository Definition (RPD)
6. Oracle Data Integrator (ODI) repository
7. WebCenter contents


Setup Migration through FSM
Migrates setup from one environment to another
- Typical use case is migration from Test to Production
Migrates all setup for a Logical Business Object (LBO)
- Scope, an FSM concept, allows row-level migration but is not enabled for many
HCM LBOs
Target to Source migration rules:
- Setup from target will be inserted into source if it does not exist in the source
- Setup rows from target that exist in the source will be updated with changes
from the source
- General Rule: Effective Start Dates must be the same to be considered as a
match

For more information, see FSM Help: Manage Export and Import Processes.


HCM Setup Migration

The following table identifies the Logical Business Objects (LBOs) for which FSM
migration is supported with Release 7.

Also Supported:
FSM Migration for Common and Shared LBOs (for example, Common Look-ups,
Flexfield Definitions, Business Unit)
Comp Plan Migration via XML Export/Import function on the Comp Plan Setup UI


Extensibility Migration

The following table identifies key enablers for migration extensibility configurations from
one environment to another.

For more information, see the white paper Managing Fusion HCM Cloud Service
Environments (MOS article # 1537461.1).


HCM Implementation Lifecycle

The final factor to consider when formalizing a strategy for managing Fusion HCM
Cloud Service environments is the typical lifecycle of HCM implementations.

The implementation lifecycle is divided into the following broad categories:
Conference Room Pilot(s): A conference room pilot (CRP) is a recommended
first step within an HCM implementation. Typically, the CRP follows predefined
business scenarios that, to varying degrees, allow the implementation team to
assess how well the application aligns with how the business operates, and how
the application can be configured to address these business requirements.

Initial Implementation: The initial implementation should focus on doing the bulk
of configurations and data loading in the test environment and migrating
configurations (after user acceptance testing) to the production environment to
go live.

Add-on Implementation: Add-on implementations follow the initial
implementation and can vary in scope from minor functional enhancements,
basic maintenance, and new BI and reporting development all the way to large
implementation projects introducing new applications and groups of employees.



Content Migration within the HCM Implementation Lifecycle



Initial Implementation

Minimizes impact on Production
P2T content migration refreshes Test, aligns it with Production for testing
Supports management of extensibility enhancements in Test and migration to
Production
Final people load occurs in Production after validating in Test


Initial Implementation Process

Note: Some customers may choose to combine the Set up and Test Configuration and
People Load Testing phases. If necessary, customers could delete tables with corrupt
data using Delete Scripts and rerun the scripts.


Add-on Implementation

P2T content migration copies Production environment for implementation work in
Test
Additional people load, if necessary, occurs in Production after validating in Test
Requires that any additional setup and extensibility work be validated in Test and
migrated or reapplied to Production


Add-on Implementation Process

Note: Some customers may choose to combine the Set up and Test Configuration and
People Load Testing phases. If necessary, customers could delete tables with corrupt
data through Delete Scripts and rerun the scripts.


Oracle Cloud Backup Policies

Online backup of the database, code tree, and archive logs are performed by
Oracle for Production environments.
Backup is for Oracle's sole use in the event of a disaster.
Backup is made to disk daily and copied to tape twice a week.
Backup is maintained at an offsite storage facility for 5 weeks.
The offsite tape storage vendor (PCI certified for tape vault mgmt) takes the
tapes offsite on a daily basis.
Data stored in the backup tapes for the service is encrypted using strong
cryptography (AES-256 bit) and a True Random Number Generator (TRNG) for
the generation of strong keys.
Restoration of data from the stored backup tapes is tested twice annually.


Oracle Cloud Disaster Recovery Objectives

Oracle provides a service option for customers requiring faster recovery
responsiveness than that Oracle already provides to its Cloud customers through
its business continuity plan and service level objective of 99.5% uptime.
The enhanced service provides contractual confirmation of DR efforts recovery
point of no more than one hour and a faster recovery time objective (no more
than 12 hours).


Know How to Work with Oracle SaaS

Understand key differences between On-premise, SaaS by other providers, and Oracle
SaaS.

Oracle SaaS offers several services and resources to help you perform successful
customer engagements.
First, understand how to work effectively with Oracle Support. They are the
primary team you should be contacting for any issues or guidance you might
need during implementation. There are few best practices to triage and escalate
the issues. Be aware of those and apply whenever situation arises.

Oracle Operations team is like the IT team performing technical operations on
your Cloud services. Be aware of how the team performs certain routine pro-
active tasks such as patching. Also know what specific cloud service-related
requests the Oracle Ops team will be performing on your behalf. Understand how
you, as an implementer need to request for these.

Oracle COE is available to assist and guide you during implementation.
Understand its function and leverage Oracle COE appropriately during or after
the implementation.


There are no demonstrations or activities for this
lesson



Lesson Highlights

Oracle Cloud (OC)
The Oracle Cloud is composed of 3 Service Models: Application Cloud Service (SaaS);
Platform Cloud Service (PaaS); and Infrastructure Cloud Service (IaaS). All Services
provided by OC are managed under a common infrastructure to support the entire
customer lifecycle for purchasing, using, and evaluating their Service.

HCM Cloud Service
The HCM Cloud Service is a complete suite of applications, Oracle Fusion and Taleo,
which collectively manage customers complete human resources and talent
management requirements.

HCM Cloud Service Maintenance
Oracle applies as-needed and recurring maintenance to customer environments on a
predictable, published cadence.

HCM Cloud Service Upgrades
Oracle performs upgrades to the customer environments as new service versions
become available. Typically two upgrades are provided each year. Oracle
communicates logistics and whats new before, during, and after the upgrade in many
forms. Upgrades are applied to Test environments first and, after customer validation, to
Production environments.

Oracle Cloud Environment Management
A standard Fusion HCM Cloud Service subscription provides two environments -
Production environment and Test environment. Customers may purchase additional
Test environments for other purposes (For example, Payroll parallel runs, feature
development, familiarization/training, and internal demos). The implementing customer
must define and adhere to a strategy for what work occurs in which environment and
how to migrate content from one environment to another. Oracle provides general
guidance on how to manage Cloud environments.

Content Migration Solutions
The Content Migration Solutions between Fusion HCM Cloud Service environments are
classified in terms of the direction from which content is migrated.
Test-to-Production (T2P) - Migrations occur for one type of content, such as
business intelligence or functional setup, at a time
Production-to-Test (P2T) - Typically migrates an entire production environment to
test and, in doing so, overlays the entire contents of the test environment


02 - HCM Cloud Service Overview2

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02 - HCM Cloud Service Overview2

Uploaded by

Copyright:

Available Formats

Partner Boot Camp

Fusion HCM Global HR

You might also like