Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
January 2017
Revised: April 2017
TABLE OF CONTENTS
REVISION HISTORY ............................................................................................................................................. 4
OVERVIEW ......................................................................................................................................................... 5
Give Us Feedback ............................................................................................................................................................... 5
2
Automated Post-Load Processing for Worker.................................................................................................................. 54
HCM COMMON FEATURES ................................................................................................................................. 55
Deep Links ........................................................................................................................................................................ 55
Initiate Tasks Quickly From The Quick Actions Page ........................................................................................................ 55
HCM EXTRACTS ............................................................................................................................................... 57
Use WebCenter Content Delivery Option ........................................................................................................................ 57
ORACLE TRANSACTIONAL BUSINESS INTELLIGENCE .................................................................................................... 59
OBIEE Answers Enhancements: Subject Area Search ...................................................................................................... 59
OBIEE Answers Enhancements: Save a Column ............................................................................................................... 60
3
REVISION HISTORY
This document will continue to evolve as existing sections change and new information is added. All
updates are logged below, with the most recent updates at the top.
The new functionality referenced in this document may not be immediately available to you if your
organization has chosen not to receive optional monthly updates. Rest assured you will receive the new
functionality in the next quarterly update which is required and cumulative. Quarterly updates are
applied in February, May, August, and November. As a one-off exception the February 2017 Quarterly
update will be applied in March 2017.
4
OVERVIEW
This guide outlines the information you need to know about new or improved functionality in Oracle
HCM Cloud Release 12. Each section includes a brief description of the feature, the steps you need to
take to enable or begin using the feature, any tips or considerations that you should keep in mind, and
the resources available to help you.
Oracle HCM Cloud release documents are delivered in five functional groupings:
HCM Cloud Common Features (This document pertains to all HCM applications. It is the
base human resource information for all products and HCM Tools.)
Global Human Resources Cloud (Global Human Resources contains the base application in
which other application use for common data such as workforce structures and person
information. Regardless of what products you have implemented you may want to see the
new features for Global Human Resources that could impact your products.)
NOTE: Not all Global Human Resource features are available for Talent and Compensation products.
Optional Reading for HCM Products (Depending on what products are in your cloud service):
Common Technologies and User Experience (This documents the common features across
all Cloud applications and is not specific to HCM)
NOTE: All of these documents can be found on the Oracle Help Center at:
https://cloud.oracle.com/saasreadiness/hcm under Human Capital Management Release Readiness.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at
oracle_fusion_applications_help_ww_grp@oracle.com. Indicate you are inquiring or providing feedback
regarding the Global HR Cloud Whats New for Release 12 in the body or title of the email.
5
RELEASE FEATURE SUMMARY
Some of the new Release 12 features are automatically available to users after the upgrade and some
require action from the user, the company administrator, or Oracle. The table below offers a quick view
of the actions required to enable each of the Release 12 features.
6
Action Required to Enable Feature
7
HCM COMMON FEATURES
APPLICATIONS SECURITY
Oracle Fusion Applications Security provides a single console where IT Security Managers and
Administrators can perform various functions including user lifecycle management, role definition,
security policy management(both functional and data), role hierarchy maintenance, username and
password policy administration, and certificate management. The console also enables users to simulate
the effect of security changes, to run security reports, and download a connector for integration with
Microsoft Active Directory.
In Release 12, Oracle Fusion Applications Security offers several new capabilities that offer customers
the following benefits:
A Simplified User Experience for the IT Security Manager - Prior to Release 12, security
administration functions were distributed across Oracle Identity Management (OIM) and
Authorization Policy Manager (APM). In Release 12, these functions are delivered through a
single interface the Security Console. OIM and APM are no longer available in R12.
Easy Integration with Identity and Access Management (IDM/IAM) Systems New
capabilities to synchronize user account information with Identity and Access Management
(IDM/IAM) systems. This synchronization enables the delivery of a Single Sign-On
experience through these systems.
For Microsoft Active Directory (AD) and Oracle Identity Management (OIM), customers can
download and install connectors that will automatically synchronize user account
information between Oracle Fusion Applications and these IDM systems. As in R11,
customers must continue to log a Service Request (SR) to set up federated Single Sign-On
8
(SSO) between these systems. Once the federation is enabled, the connectors will
synchronize information.
Release 12 also delivers a REST API based on the SCIM (System for Cross-Domain Identity
Management) standard. Customers can use this API to create user accounts, modify user
attributes (e.g. email), enable/disable users, and fetch user account and role information.
Upgrade-Safe Reference Role Model - Starting from Release 12, pre-defined roles that are
shipped with Oracle Applications Security will be locked down. Customers will not be able to
modify the functional and data security policies that are associated with these roles. They
can, however, add new data security policies to these pre-defined roles. In addition,
privileges and resources are protected. Users cannot create or modify these artifacts
Locking down these security artifacts enables safe upgrades to pre-defined roles, since the
possibility of conflict with customer introduced changes to these roles is now eliminated.
This, in turn enables customers to safely adopt new enhancements that may be delivered
with pre-defined roles in future releases. As in R11, customers can make copies of pre-
defined roles and freely customize these copies.
Please refer to your R12 Security Upgrade guide for any steps that may be required to
prepare for and adopt this feature.
Enhanced Self-Service Capabilities - Administrators are able to manage the entire user
lifecycle. They can customize how notifications are generated and sent for various user
lifecycle events including user account creation, and password management.
Administrators can also tailor username and password generation by choosing from a list of
shipped policies.
Please refer to your R12 Security Upgrade guide for any steps that may be required to
prepare for and adopt this feature.
You can now create and manage implementation user accounts within Oracle Fusion Applications
Security. You can assign roles to these user accounts using the following navigation: Tools > Security
Console > User tab. You can also search, retrieve, and manage user accounts automatically created for
employees, contingent workers, supplier contacts, or partner contacts
9
Search User Accounts Page
STEPS TO ENABLE
10
ROLE INFORMATION
The following function security privileges are required for this feature.
KEY RESOURCES
For more information on the Security Console, go to the Help Center for the following guide:
As an administrator, you can manage passwords of other users using the Security Console. You can
auto-generate or manually enter a password for a user account. You can also define password lifecycle
and complexity policies. Passwords will be automatically validated against these policies.
11
STEPS TO ENABLE
KEY RESOURCES
For more information on the Security Console, go to the Help Center for the following guide:
You can now manage your own user account password using the Security Console. The password will be
automatically validated against the defined password lifecycle and complexity policies.
STEPS TO ENABLE
As an administrator, you can now lock user accounts. If you lock a user account, you will be temporarily
preventing the user from logging in with that user account. You can also unlock a locked user account.
12
Lock User Account in Edit User Account Page
STEPS TO ENABLE
You can now view only certain components of a role in the graphic visualizer. You can view only the
privileges, aggregate privileges or roles assigned to a role. You can also view the graph in full screen
mode and pan over a specific region in the graph.
For complex roles, these features enable you to reduce the amount of information visualized and to
focus on the area within the role hierarchy that requires your attention.
13
View Only the Privileges for a Role
14
View Only the Inherited Roles for a Role
15
Pan and View Top Left Region of the Graph
STEPS TO ENABLE
16
TABULAR ROLE HIERARCHY VIEW
You can now view role hierarchies in a tabular view. You can switch between the graphic visualizer view
and the tabular view. You can also export the data displayed in the tabular view.
17
Tabular View of Direct and Indirectly Assigned Privileges for a Role
18
Tabular View of Direct and Indirectly Assigned Users for a Role
19
Export of Direct and Indirectly Inherited Privileges for a Role
STEPS TO ENABLE
20
SEARCH IN ROLE HIERARCHY VISUALIZATION
You can now search and quickly locate security artifacts (nodes) in the role hierarchy visualization. You
can search for privileges, roles or users in the visualization.
STEPS TO ENABLE
You can now define the user name generation rules used to auto-generate the user name in Oracle
Fusion Applications Security. User name generation rules can be based on the users first and last
names, e-mail or person number. You can also choose to use a system generated user name if the rule
fails to generate a user name.
21
User Name Generation Rules Region in the Administration Page
STEPS TO ENABLE
If your company submitted a service request for Oracle to set up a custom username generation rule,
review the Validate User Lifecycle Settings topic in Upgrading Applications Security in Oracle HCM
Cloud.
PASSWORD POLICIES
You can now define policies for password management. These policies can define the duration for
various password lifecycle events like password expiration and password warning generation. You can
also set the complexity of generated passwords by choosing from a pre-defined list of rules.
22
STEPS TO ENABLE
If your company submitted a service request for Oracle to set up a custom password policy, review the
Validate User Lifecycle Settings topic in Upgrading Applications Security in Oracle HCM Cloud.
ROLE INFORMATION
NOTIFICATION TEMPLATES
You can now define custom notification templates for user account life cycle events. You can also use
pre-defined notification templates.
These templates will be used to generate notifications for events like user account created, user
password reset and user password expiry warning.
23
Edit Notification Template Page
STEPS TO ENABLE
If your company submitted a service request for Oracle to set up a custom notification template, review
the Validate User Lifecycle Settings topic in Upgrading Applications Security in Oracle HCM Cloud.
You can now identify a predefined (factory shipped) Oracle role when viewing the role. Predefined
Oracle roles are locked and you cannot customize the Oracle delivered functional and data security
policies associated with these roles. You can, however, add data security policies to these roles.
Predefined Oracle roles are displayed in a different color in the graph visualizer.
24
Predefined Role Indicator in the Edit Role Page
STEPS TO ENABLE
25
BRIDGE FOR MICROSOFT ACTIVE DIRECTORY
Simplify Single Sign-On with Microsoft Active Directory by downloading and installing the Active
Directory Bridge from the Security Console. Automatically synchronize user account information
between Oracle Fusion Applications Security and Microsoft Active Directory.
26
Active Directory Bridge User Attribute Mappings Page
27
STEPS TO ENABLE
You can now generate a report that lists password changes made by users. The report can be generated
for changes made by specific users or for all changes made during a specific period.
STEPS TO ENABLE
28
ROLE INFORMATION
You can now optionally Integrate with your Identity Management solution for user and role
management using industry standard System for Cross-domain Identity Management (SCIM) REST APIs
and ATOM feeds.
STEPS TO ENABLE
PASSWORD RESET
The password reset flow has been changed in Release 12. A notification email will be sent to the user
who requests a password reset. The user will be required to click on this link, within a specific period of
time, to change the password. This replaces the previous flow where users were required to answer a
series of challenge questions to reset the password.
29
User Reset Password Page
STEPS TO ENABLE
SECURITY CONSOLE
The unified security administrator interface, combined with the ability to safely upgrade the reference
security implementation will result in the following changes in functionality in the Security Console.
IT Security Managers manage all User Account information including password changes and
lock/unlock status are managed in the security console.
IT Security Managers manage roles directly in the Security Console. They no longer use
Oracle Identity Manager or Authorization Policy Manager.
IT Security Managers can view, create or modify roles without first selecting an application.
IT Security Managers cannot create or modify privileges. They can continue to grant
privileges to roles
IT Security Managers cannot create or modify resources.
IT Security Managers cannot grant resources directly to role. Resources are now only
granted to privileges.
STEPS TO ENABLE
30
NEW FUNCTION SECURITY PRIVILEGES FOR APPLICATIONS SECURITY
This section provides product-specific information that you need when implementing new Release 12
features in your existing roles.
If you are not using the predefined reference roles, then you need to add the function security privilege
to relevant custom job roles.
This table identifies the required function security privilege and the predefined role that automatically
inherits the privileges during the upgrade.
31
HCM SECURITY
Release 12 includes enhancements to person security profiles, new-person task flows, role mappings,
the Retrieve Latest LDAP Changes process, predefined job and abstract roles, and security setup.
Prior to Release 12 you could secure access to person records based on areas of responsibility, but you
had to provide custom SQL, which could be complex. Nonetheless, as security performance is enhanced
when person records are secured by area of responsibility, this approach was always encouraged.
In Release 12, you no longer have to provide custom SQL to secure person records by area of
responsibility. The person security profile pages have been completely redesigned to incorporate a new
Area of Responsibility section where you select the responsibility type, a single responsibility scope, and
the workers to whom it applies. If a person becomes responsible for workers in a different instance of
the same scope (for example, a different department), then you need only to update that persons area
of responsibility. The person security profile remains valid without update. You can also create a single
HCM data role to include a person security profile of this type and assign it to multiple representatives.
The Basic Details section of the Create Person Security Profile and Edit Person Security Profile pages
now includes a Description field where you can provide a description of the security profile.
32
Description Field in the Basic Details Section of the Create Person Security Profile Page
Creating a person security profile is now a two-step process. Once you have defined your security
criteria, you click Next to open the Create Person Security Profile: Preview page. You can review the
automatically generated SQL predicate for your security criteria on the SQL Predicate tab on this page.
You can also test the access provided by the security profile before you save it. On the Person Access
Preview tab of the Create Person Security Profile: Preview page, you can select a user and click Preview
to see the number of person records that this security profile allows the user to access. You also see the
name and type of the users areas of responsibility, if any.
33
Person Access Preview Tab on the Create Person Security Profile: Preview Page
You can then identify individual person records to which the security profile provides access by
searching for them. The search is based on criteria such as department and location and is performed
within the set of person records that was returned by the Preview action.
For example:
The person security profile secures access by area of responsibility, the responsibility type is
Human Resources Representative, and the scope is Department.
The selected user has the Human Resources Representative responsibility for the Sales
department.
In this case, the search on the Person Access Preview tab is performed within person records in the
Sales department.
Note that the results from the Person Access Preview are based on the current person security profile
only. Users may have many roles that provide access to other person records.
STEPS TO ENABLE
Existing person security profiles are unaffected by these enhancements. Customers upgrading to
Release 12 continue to see all sections of the person security profile pages, plus the new Area of
Responsibility section, when managing existing person security profiles. If upgrading customers select
the Area of Responsibility section in an existing person security profile, then the Manager Hierarchy,
Person Types, Workforce Structures, and Global Name Range sections become unavailable. These
criteria are incompatible with securing by area of responsibility.
34
Customers who are new in Release 12 see the new person security profile pages only, which include the
Basic Details, Area of Responsibility, Manager Hierarchy, and Custom Criteria sections. Upgrading
customers see the new page when creating new person security profiles.
When you create person security profiles in HCM data roles, you can now secure access to person
records using areas of responsibility. The Person and Public Person sections of the Create Data Role:
Security Criteria and Assign Data Role: Security Criteria pages now include the option to secure access
by area of responsibility.
The Assign Security Profile to Role: Person Security Profile page includes the Area of Responsibility
section if it was selected on the Create Data Role: Security Criteria page.
STEPS TO ENABLE
Existing HCM data roles are unaffected by these enhancements. Customers upgrading to Release 12
continue to see all options on the security criteria pages, plus the new Secure by Area of Responsibility
option, when managing existing HCM data roles. If upgrading customers select the Area of
Responsibility option in an existing data role, then other security criteria, apart from Secure by Custom
Criteria, become unavailable. The removed criteria, such as Secure by Manager Hierarchy, are
incompatible with securing by area of responsibility.
Customers who are new in Release 12 see the Secure by Area of Responsibility, Secure by Manager
Hierarchy, and Secure by Custom Criteria options only.
35
ROLE PROVISIONING SUPPORTS AREAS OF RESPONSIBILITY
Role mappings now include a Responsibility Type option in the Conditions section. You can set this
option to provision roles based on a users assigned areas of responsibility.
Responsibility Type Option in the Conditions Section of the Create Role Mapping Page
STEPS TO ENABLE
When you create a person security profile, you can now allow access to future-dated person records by
selecting the option to include future people. This option is deselected by default. If you select the
option when creating or editing new person security profiles, then users can access all person records
that satisfy the security criteria, including any that are future dated. If you leave the option deselected,
then users cannot access person records with future start dates that otherwise satisfy the security
criteria.
Include Future People Option on the Create Person Security Profile Page
36
STEPS TO ENABLE
The Include Related Contacts option is no longer needed and is removed from the person security
profile pages for new person security profiles. In existing person security profiles, the option continues
to appear only if it is currently selected.
Users who can view a worker in the Manage Person work area and access the Contacts tab can see the
workers contacts, provided that the contacts are not also workers. If a contact is a worker, then access
to the contacts details is secured by person security profile.
Personally identifiable information (PII), such as phones and e-mails, is not visible unless the user
inherits the Manage Contact Person PII aggregate privilege.
STEPS TO ENABLE
When you perform any of the new-hire task flows, such as Hire an Employee or Add a Contingent
worker, you will see that the Roles page has been removed. Instead, role information for new person
records now appears in the Role Requests section on the Compensation and Other Information page.
The role information itself is unchanged; only the location is different.
37
The following screen capture shows the Role Requests section on the Compensation and Other
Information page in the streamlined new-hire task flows.
STEPS TO ENABLE
Role mappings now include a Contact Role attribute so that Oracle Sales Cloud customers can provision
roles automatically to Oracle Service Cloud external contacts. Oracle HCM Cloud customers can ignore
this attribute. It has no effect on role provisioning for Oracle HCM Cloud users.
Contact Role Attribute in the Conditions Section of the Create Role Mapping Page
STEPS TO ENABLE
38
REDUCED FREQUENCY FOR THE RETRIEVE LATEST LDAP CHANGES PROCESS
Until this release, the recommendation was to schedule Retrieve Latest LDAP Changes to run daily. From
Release 12, you no longer need to run the process regularly. The new recommendation is to run the
process if you become aware of data integrity issues, for example. Otherwise, the process is not
required. You still need to schedule Send Pending LDAP Requests to run regularly, preferably daily, to
process future-dated employment transactions, such as new hires.
STEPS TO ENABLE
In this release, we have tidied the role definitions of the Human Resource Specialist and Line Manager
predefined roles. Both roles inherited the Copy Personal Data to LDAP and Send User Name Request to
LDAP privileges directly. They also inherited them indirectly from the Manage User Account and Link
User Name to Person aggregate privileges. The directly inherited versions of the privileges are therefore
redundant and have been removed in Release 12. The function access of the Human Resource Specialist
and Line Manager roles is unaffected by these changes.
STEPS TO ENABLE
You now specify the default format of user names for the enterprise by setting User Preferences on the
General tab of the Security Console Administration tab. The Default User Name Format option has been
removed from the User and Role Provisioning Information section of the Manage Enterprise HCM
Information page.
The default user name format is now the workers work e-mail. Before Release 12, the default format
was as specified in Oracle Identity Management. In addition, two formats that were previously available
in Oracle Identity Management can now be selected on the Security Console. The formats are
FirstName.LastName and FLastName (the initial of the first name concatenated with the last name).You
can also specify that a system user name is to be generated if the selected generation rule fails.
39
User Preferences Information on the Administration Tab of the Security Console
You now control the mailing of sign-in details to users by setting Notification Preferences on the
Notifications tab of the Security Console Administration tab. The Send User Name and Password option
has been removed from the User and Role Provisioning Information section of the Manage Enterprise
HCM Information page.
You manage notifications using notification templates. The New Account Template and the New
Account Manager Template are two of several predefined templates for notifying users of events
related to their accounts. The New Account Template controls notifications sent to users themselves,
and the New Account Manager Template controls notifications sent to their managers. Notifications in
general are enabled by default.
Although you can edit the text in predefined templates, your text will be overwritten on upgrade.
Therefore, you are recommended to create custom templates for events related to new accounts if the
predefined text is not suitable.
40
Add Notification Template Page on the Security Console
You can disable individual templates as necessary. For example, you may want to disable some
templates while loading person records in bulk to control when new users receive their sign-in details.
STEPS TO ENABLE
If you are upgrading from a previous release, then we have migrated the current setting of the Send
User Name and Password enterprise option. If Send User Name and Password was set to Yes, then the
New Account Template and its associated event are automatically enabled. Otherwise, they are
automatically disabled. Review these settings and change them if appropriate.
The User Notification Preferences section of the Create User page includes an option to send users their
user names and passwords. You select this option if you want the new user to be sent his or her user
name and password when the user account is created.
41
From Release 12, the availability of this option is controlled by settings on the Security Console. If
notifications are enabled on the Security Console and enabled notification templates exist for at least
one of the New User Created and New Account Created - Manager event types, then the Send user
name and password option is enabled. If notifications are disabled on the Security Console, then the
option is disabled and cannot be selected.
STEPS TO ENABLE
When a user account is created or a password reset is requested, the user must sign in and set a new
password. From this release, the notification e-mail contains a Reset Password link so that the user can
access that function directly. Temporary passwords are no longer generated.
STEPS TO ENABLE
A user credentials e-mail is typically sent for new users and contains the user name and a reset
password link. A user credentials e-mail can be sent once only for any user. When the e-mail is sent, the
Credentials Sent indicator is set automatically.
From this release, the Credentials Sent indicator is set when an attempt is made to send the user
credentials e-mail for a user, regardless of whether the mail is successfully sent or received. If an
attempt is made to send the e-mail at a time when notifications are disabled on the Security Console or
no notification template is available for the event, then the Credentials Sent indicator is still set. This
situation may occur when Send Pending LDAP Requests processes requests for future-dated user
accounts. Therefore, you must ensure that notifications are enabled and notification templates are
available when user accounts are likely to be created if you want user credentials e-mails to be sent.
STEPS TO ENABLE
When you loaded workers using HCM Data Loader in releases prior to Release 12, the enterprise HCM
options Generate User Account and Send User Name and Password controlled whether:
42
In Release 12, the enterprise HCM options are ignored when you load workers in bulk. To give you
greater control, the GeneratedUserAccountFlag and SendCredentialsEmailFlag attributes of the Worker
object are now set to N (No) by default. When loading workers using HCM Data Loader, you must set
the GeneratedUserAccountFlag attribute to Y (Yes) for any worker for whom you want a user account to
be created automatically. You must also set the SendCredentialsEmailFlag attribute to Y (Yes) if you
want the account credentials to be sent. If you omit these attributes, then their values are N (No) by
default.
As a result of these changes, unwanted user accounts will no longer be created automatically when you
load historical data in bulk for workers whose work relationships are terminated, for example.
STEPS TO ENABLE
If you set SendCredentialsEmailFlag to Y for any Worker object, then you must ensure that a valid
notification template is both defined and enabled for this event. You manage notification templates on
the Security Console. The Send User Name and Password option is removed from the Manage
Enterprise HCM Information page in Release 12.
The alternate contact e-mail address is an enterprise-wide address to which all sign-in details for new
user accounts can be sent. In Release 12, the Alternate Contact E-Mail Address option is no longer in the
User and Role Provisioning Information section of the Manage Enterprise HCM Information page.
User and Role Provisioning Information on the Manage Enterprise HCM Information Page
43
The Default User Name Format and Send User Name and Password options have also been removed.
From Release 12, you manage those two settings on the Security Console.
STEPS TO ENABLE
44
ROLE INFORMATION
For some Release 12 functions, new aggregate privileges, function security privileges, and transaction
analysis duty roles have been added to predefined roles, such as Employee and Human Resource
Specialist.
If you are not using the predefined roles, then you need to add the new security privileges to your
custom roles. Details of this step are provided for each function.
If you are using the predefined roles and plan to use the new functions, then you must regenerate the
relevant predefined roles to update their data security policies. You need to perform this step for:
Predefined abstract roles, such as Employee and Line Manager, to which aggregate
privileges have been added.
HCM data roles that include job roles to which aggregate privileges have been added.
Any job roles to which aggregate privileges have been added and to which HCM security
profiles are assigned directly. You do not need to regenerate job roles to which HCM
security profiles have not been assigned.
KEY RESOURCES
For instructions on regenerating roles, see the Securing Oracle HCM Cloud guide on the Oracle Help
Center.
45
HCM DATA LOADER
HCM Data Loader provides a flexible and efficient method of bulk loading business object data for data-
migration and on-going incremental updates to Oracle Human Capital Management Cloud. Release 12
includes enhancements to monitoring of data loads and support for loading data from spreadsheets.
When loading data using HCM Data Loader, you can now monitor the progress of the load for each
business object. In the Details section of the Import and Load Data page, you see a status icon in the
Loaded (Progress) column for the selected business object. When you click the icon, a dialog box opens
containing summary data for the load.
For in-progress loads, this dialog box shows both the percentage and the number of objects already
processed and the estimated time for the load to complete. The information in the dialog box for in-
progress loads is refreshed automatically every 15 seconds.
STEPS TO ENABLE
46
SPREADSHEET DATA LOADING
HCM Spreadsheet Data Loader now enables you to define a template to suit your business case for
loading specific business objects, such as jobs or workers. You can specify the column order for ease of
data entry, configure column prompts, specify default values, and configure the display type for lists of
values. Business users can now generate spreadsheets from templates with the required set of
attributes for a selected object.
To access spreadsheet-template-creation tasks, you use the Initiate Spreadsheet Load task in the Data
Exchange work area. You can also use the Initiate HCM Spreadsheet Load task in the Setup and
Maintenance work area. Both tasks open the Manage Spreadsheet Templates page.
To perform data upload tasks, you use the Load Spreadsheet Data task in the Data Exchange work area.
HCM Spreadsheet Data Loader uses HCM Data Loader to perform the data upload.
When you create a new spreadsheet template, the Create Template dialog box opens.
47
Create Template Dialog Box
You specify name and code values for the template. When you click OK in this dialog box, the Manage
Template Definition page opens. Manage Template Definition is a three-step process:
1. Define
2. Design
3. Review
Some of the information on this page is prefilled from the Create Template dialog box. On the Define
page, you can:
Select a locally defined category (for example, to group templates for easy retrieval).
Provide a description of the template.
Set the status of the template. Draft templates are not available to business users and are
not accessible from the Load Spreadsheet Data task in the Data Exchange work area. The
template status must be Active before the spreadsheet is accessible from the Load
Spreadsheet Data task.
48
In the Design step, you select the business-object attributes to include in your template from a list of all
available attributes.
You can:
Search for individual attributes or display those for a specific component of the object.
Click on the Information icon for an attribute to see its type and length, its user key name,
and whether it is required.
Display the attributes in a tree structure so that the object hierarchy is clear.
You select each attribute that you want to include in your template and move it to the Selected
Attributes section. When you move the first attribute, other attributes that are always required move
automatically to the Selected Attributes section. Attributes that are required conditionally or only for
new objects are not moved automatically. You must move those attributes explicitly if you plan to use
them. Icons identify all required attributes.
49
Selected Attributes Section of the Design Page
You can:
Specify the order of the attributes in spreadsheets generated from the template.
Edit the information that will appear in the spreadsheet for individual attributes. You can
change the column heading, make optional attributes required, specify a default value, and
provide a description to appear as help text in the spreadsheet.
You can also edit all attributes at once by selecting the Configure - Advanced action.
50
Once you have selected the attributes for your business case, arranged them in the appropriate order,
and edited them as required, you can review the template.
As the template designer, you can generate a test spreadsheet from this template by clicking the Open
button on this page. The saved template can be reused and edited as required.
Business users perform the Load Spreadsheet Data task in the Data Exchange work area to search for
active spreadsheet templates.
51
Columns from the Generated Spreadsheet
Users enter data in the generated spreadsheet and upload it from the spreadsheet by clicking the
Upload button on the Spreadsheet Loader tab toolbar.
Search for an existing data set. You can retrieve all records from the data set or only those
that failed to load. You can add records to the data set and edit those that failed to load.
Create a new data set to load. Any records in the spreadsheet belong to this data set. A
name is generated automatically, but you can overwrite the generated name.
Upload data from the spreadsheet to Oracle HCM Cloud.
Refresh the spreadsheet to review the current status of each line after an upload.
View current messages for the spreadsheet in the Status Viewer. Messages also appear on
the Messages worksheet of the spreadsheet.
When you upload data from a spreadsheet, any objects that are imported successfully to the stage
tables are loaded automatically to the application tables. Errors from both the import and load stages
are reported in the spreadsheet when you click Refresh. After correcting any errors, you click Upload
again to import the corrected data to the existing data set.
52
STEPS TO ENABLE
HCM Data Loader support for spreadsheets is available by default to new customers in Release 12.
For customers who are upgrading from an earlier release, the availability of HCM Data Loader
spreadsheet support depends on the setting of the HCM Data Loader Scope configuration parameter.
To enable access to HCM Data Loader spreadsheet support, the HCM Data Loader Scope
parameter must be set to Full. The default setting of the HCM Data Loader Scope parameter
for new customers has been Full since Release 10.
For customers who upgraded from Release 9 to Release 10, HCM Data Loader Scope is set to
Limited by default. This setting prevents access to the new HCM spreadsheet data loading
solution but enables access to its predecessor function. When HCM Data Loader Scope is set
to Limited, the Initiate Spreadsheet Load and Initiate HCM Spreadsheet Load tasks open the
Initiate Spreadsheet Load page, which provides a static list of predefined spreadsheets.
IMPORTANT: Once you set HCM Data Loader Scope to Full, you cannot set it back to Limited. When
HCM Data Loader Scope is set to Full, you can use neither HCM File-Based Loader nor the static
spreadsheet templates in HCM Spreadsheet Data Loader.
All users must set up desktop integration for Microsoft Excel to use HCM Data Loader spreadsheets.
KEY RESOURCES
For more information about the HCM Data Loader Scope parameter and how to set up desktop
integration for Microsoft Excel, see the Integrating with Oracle HCM Cloud Release 12 guide in the
Oracle Help Center at http://docs.oracle.com/
A new Source Key object is available with HCM Data Loader. Use this object to update existing source
key values, including default source keys. In the SourceKey.dat file, you supply just a reference to the
record that you want to update and the new source key value.
STEPS TO ENABLE
You can generate a template for the new Source Key business object and review its attributes on the
Initiate Data Load page in the Data Exchange work area.
53
JOB FAMILY CODE ATTRIBUTE ADDED TO THE JOB FAMILY OBJECT
The Job Family object has been enhanced to include a new JobFamilyCode attribute, which allows you
to supply a code to identify your job family uniquely. You can use the job family code to identify the job
family when maintaining it. As the JobFamilyCode attribute is not translatable, it remains the same for
all translations of the job family name. If you do not supply a job family code, then a unique code is
generated automatically.
STEPS TO ENABLE
You can review the structure of the Job Family business object, including the new JobFamilyCode
attribute, on the Initiate Data Load page in the Data Exchange work area.
When you load worker data using HCM Data Loader, the process HCM Data Loader Worker Post
Processing is initiated automatically to submit these processes:
You no longer have to run these processes in the Scheduled Processes work area. You can disable this
automatic post-load processing. To disable all automatic post-load processing, include the following SET
command at the top of the Worker.dat file:
SET INVOKE_POST_PROCESS N
To disable an individual process, you include the SET DISABLE_POST_PROCESS_TASKS command with
the process name. This table shows the SET command to disable each process.
STEPS TO ENABLE
KEY RESOURCES
54
HCM COMMON FEATURES
DEEP LINKS
You can now use deep links to open pages without navigating through the menu structure. This
capability is most useful if you have corporate internal portals and you want to enable direct navigation
from the portals into the Fusion HCM Application for your employees. For example, you can enable
direct navigation to Payslips, Personal Information, Absence Entry, Directory search, My Team page, and
other pages.
To view a complete list of the available Deep Links, use the HCM Deep Link task in the navigator. The list
of deep links that appear in the page is based on your functional and data security.
As an application implementation consultant, HR specialist, or line manager, you can copy a deep link
and paste it in another application.
STEPS TO ENABLE
You can quickly access different tasks from the Quick Actions page, which is available for the predefined
employee and contingent worker roles. You can view and access actions available to you according to all
55
your roles (for example, employee, line manager, and human resource specialist). This means that if you
are an employee and an HR specialist the quick actions will include actions for both roles. This feature
eliminates the need for you to be familiar with the work area organization and searching for tasks.
STEPS TO ENABLE
ROLE INFORMATION
You must have the Access Quick Actions (PER_ACCESS_QUICK_ACTIONS) privilege that can be added to
any custom role to access this page.
56
HCM EXTRACTS
Use the updated delivery option name of WebCenter Content which replaces the HCM Connect delivery
option to create extracts with encrypted or non-encrypted data and transmit them to Oracle WebCenter
Content.
The following screen capture illustrates the Delivery Type field with the WebCenter Content option
highlighted.
57
STEPS TO ENABLE
There are no steps necessary to enable this feature. (This is the standard statement if no steps are
need.)
ROLE INFORMATION
If you are not using the predefined reference roles, then you need to ensure that the transaction
analysis duty role that secures the new subject area is mapped to relevant job roles. This table identifies
the required transaction analysis duty role and suggests target job and abstract roles. You can add the
duty role to different roles if you prefer.
See the Upgrade Guide for Oracle HCM Cloud Applications Security (My Oracle Support document ID
2023523.1) for instructions on implementing new features in existing roles.
58
ORACLE TRANSACTIONAL BUSINESS INTELLIGENCE
Oracle Fusion Transactional Business Intelligence is a real time, self service reporting solution offered to
all Oracle Fusion application users to create ad hoc reports and analyze them for daily decision-making.
Oracle Transactional Business Intelligence provides human resources managers and specialists, business
executives, and line managers the critical workforce information to analyze workforce costs, staffing,
compensation, performance management, talent management, succession planning, and employee
benefits.
You can search in the subject area pane in OBIEE Answers. To use Search, click the Search icon on top of
the pane, enter the text you are seeking, and click the search icon next to the text you entered.
The folders and columns matching the search word in the selected subject area are displayed.
STEPS TO ENABLE
59
OBIEE ANSWERS ENHANCEMENTS: SAVE A COLUMN
You can save a column to the catalog for reuse in other analyses. Save the column to the Subject Area
Contents folder.
STEPS TO ENABLE
60
TIPS AND CONSIDERATIONS
You can also save a column with a formula and reuse the formula column in other analyses by dragging
and dropping it from the Catalog pane.
---
61
Copyright 2017, Oracle and/or its affiliates. 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 and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
12.04
62