27 appendix

Partner Boot Camp –
Fusion HCM Global HR
Appendix
Instructor Guide
July 25, 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. Government’s 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: Appendix .....................................................................1
Getting Started with an Implementation........................................................ 2
Objectives............................................................................................... 3
Overview of Getting Started ...................................................................... 4
Initial Implementation Users ..................................................................... 5
Initial Activities........................................................................................ 6
Oracle Fusion Applications Terminology......................................................... 8
Data Sharing ........................................................................................... 9
Business Units ....................................................................................... 10
Effective Dates ...................................................................................... 11
Define Custom Enterprise Scheduler Jobs.................................................... 12
Instructor Note: Lesson Purpose .............................................................. 13
Objectives............................................................................................. 14
Enterprise Scheduler Job......................................................................... 15
Manage Job Definitions ........................................................................... 16
Manage List of Values Sources................................................................. 17
Example of Scheduler Job ....................................................................... 18
Reference Resources .............................................................................. 19
There are no demonstrations or activities for this lesson ............................. 20
Lesson Highlights................................................................................... 21
Lesson Highlight Details........................................................................ 22
Define Help Configuration.......................................................................... 23
Objectives............................................................................................. 24
Set Help Options.................................................................................... 25
Instructor Note: Set Help Options Demonstration .................................... 26
Demonstration: Set Help Options........................................................... 27
Reference Resources .............................................................................. 29
Highlights ............................................................................................. 30
Define Profile Options ............................................................................... 31
Profile Options....................................................................................... 32
Profile Option Categories......................................................................... 33
Profile Option Levels and Values .............................................................. 34
Define Lookups ........................................................................................ 36
Key Concepts ........................................................................................ 37
Manage Lookups .................................................................................... 39
Oracle Fusion Watchlist............................................................................. 40
Oracle's Cloud Architecture........................................................................ 41
Instructor Note: Oracle Cloud Terminology................................................ 42
Oracle Cloud Terminology ....................................................................... 43

Lesson 1: Appendix
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1
Lesson 1: Appendix
This appendix includes the following topics:
• Defining Help configuration
• Defining profile options
• Defining lookups
• Defining document sequences
• Oracle Fusion reporting and analytics
• Oracle Fusion Watchlist

Lesson 1: Appendix
2 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Getting Started with an Implementation

Lesson 1: Appendix
Objectives
After completing this lesson, you should be able to anticipate actions required before
beginning an implementation by understanding what is involved in:
• Setting up implementation users
- Preparing the Oracle Fusion Applications super user for user management and
configuration
- Preparing the IT Security Manager job role for user and role management
• Defining implementation users
This lesson does not cover:
• Generating a functional setup task list before implementing users
• Defining users after setting up basic enterprise structure

Lesson 1: Appendix
Overview of Getting Started
This lesson introduces the initial activities in an Oracle Fusion Applications
implementation:
• Preparing Oracle Fusion Applications for:
- User management
- Configuration
- Role management
• Synchronizing users and roles in the Lightweight Directory Access Protocol
(LDAP) with Oracle Fusion Human Capital Management (HCM)
• Creating implementation users
_______________________________________________________
NOTE: These steps are performed after installation and provisioning, and before setting
up enterprise structures and implementing projects. Between preparing users and
synchronizing users and roles from LDAP, your enterprise needs to configure offerings
and set up task lists. Between synchronizing users and roles from LDAP and setting up
enterprise structures, your enterprise needs to create initial implementation users.
In Oracle Fusion Applications, you manage users and security through Oracle Fusion
Human Capital Management (HCM) user management flows, which are included in
each of the offering task lists. However, the HCM task flows require that enterprise
structures have been set up, and yet to add users who can set up enterprise structures
you need to have set up HCM. Therefore, you need to create one or more initial
implementation users who have the access needed for.
• Implementation project management
• Initial enterprise structures management
• User management

Lesson 1: Appendix
Initial Implementation Users
In Oracle Fusion Applications, you manage users and security through Oracle Fusion
Human Capital Management (HCM) user management flows, which are included in
each of the offering task lists. However, the HCM task flows require that enterprise
structures have been set up, and yet to add users who can set up enterprise structures
you need to have set up HCM. Therefore, you need to create one or more initial
implementation users who have the access needed for.
• Implementation project management
• Initial enterprise structures management
• User management

Lesson 1: Appendix
Initial Activities
For a standard, full implementation of Oracle Fusion Applications, the initial activities
are as follows:
1. The Oracle Identity Management System Administrator user prepares the Oracle
Fusion Applications super user for user management and configuration tasks.
2. The Oracle Identity Management System Administrator user provisions the IT
Security Manager job role with roles for user and role management.
3. The Oracle Fusion Applications super user synchronizes LDAP users with HCM
user management so that users can be provisioned with roles through HCM.
4. The Oracle Fusion Applications super user signs in to Oracle Fusion Applications
and performs the Create Implementation Users task to create one or more IT
security manager and administrator users provisioned with security
administrative entitlement.

Lesson 1: Appendix
5. The newly created IT Security Manager user signs in to Oracle Fusion
Applications and performs the Create Implementation Users task to create
implementation project managers.
6. The newly created IT Security Manager user signs in to Oracle Fusion
Applications and performs the Create Implementation Users task to create users
for enterprise structure setup, and creates a data role for HCM setup and
provisions that role to the enterprise structure setup users.
The procedures named in this lesson for getting started are presented in Getting Started
with Oracle Fusion Applications: Common Implementation. You can find this document
(ID: 1387777.1) on My Oracle Support, https://support.oracle.com.

Lesson 1: Appendix
Oracle Fusion Applications Terminology
This topic discusses the following Oracle Fusion Applications terminology:
• Data sharing
• Business units
• Effective dates

Lesson 1: Appendix
Data Sharing
You can set up data sharing across your organization using sets. Sets are:
• Used for partitioning reference data into smaller portions, or sets
• Can be assigned to different business units (organizations within your enterprise)
• Also known as Reference Data Set
The Oracle Fusion HCM objects that are set enabled are:
• Departments
• Locations
• Jobs
• Grades

Lesson 1: Appendix
Business Units
Business Units:
• Offer your organization a flexible structuring device through which you can
implement Oracle Fusion HCM, based on how your business is organized
• Are always associated with a SetID, which determines values in control tables to
which a business unit has access

Lesson 1: Appendix
Effective Dates
Effective dates:
• Enable the system to maintain history on data
• Specify when data goes into effect
• Ensure that data is valid at a given point of time

Lesson 1: Appendix
Define Custom Enterprise Scheduler Jobs
This section describes the tasks under the task list Define Extensions for
Workforce Deployment > Define Custom Enterprise Scheduler Jobs for Workforce
Deployment.

Lesson 1: Appendix
Instructor Note: Lesson Purpose
The purpose of teaching this lesson at this point is to make students understand what
are custom jobs and processes, since we talk about scheduling and running processes
in the subsquent lessons.

Lesson 1: Appendix
Objectives
After completing this lesson, you should be able to:
• Describe what enterprise scheduler job definitions are.
• Identify the purpose of list of values sources.

Lesson 1: Appendix
Enterprise Scheduler Job
An Oracle Enterprise Scheduler job is an executable that users can run to process
data, for example to validate invoices or create journal entries. Some jobs also provide
report output, for example tax reports used for reporting to tax authorities.
Related concepts include:
• Process or Scheduled Process
• Job Definition
• Parameters

Lesson 1: Appendix
Manage Job Definitions
• Process or Scheduled Process: A unique submission or run of a job. For
example, users can run a process for a specific job to post journal batches for
one accounting period, and submit another process for a different accounting
period. Each run of the same job has a unique process ID.
• Job Definition: The metadata for the job that allows it to be run, for example the
job type, location of the executable, and parameters available to users.
• Parameters: Filters that users can set when they submit a process, for example,
a date range for document creation date. The process then includes only records
with a creation date within the specified range.
Predefined jobs are used in various Oracle Fusion applications. Your technical
administrators can create custom jobs and job definitions based on Java, PL/SQL, or
any other supported technology.
You can optionally update aspects of these custom jobs, including:
• Editing job display names, for example to use terms that are more familiar to
your users.
• Editing parameter display names, using the Prompt field.
• Using the Tooltip Text field to add parameter help text that appears when users
focus on the parameter. For example, you can provide restrictions or
considerations specific to your company's needs.
To edit custom job definitions, access the Manage Job Definitions page from either:
• The Setup and Maintenance work area. You must select the task that contains
the name of the Java EE application to which the job definition belongs. For
example, use the Manage Custom Enterprise Scheduler Jobs for Payables and
Related Applications task for Oracle Fusion Expenses job definitions.
• Oracle Enterprise Manager Fusion Applications Control.

Lesson 1: Appendix
Manage List of Values Sources
A list of values source:
• Determines where a list of values comes from and what the specific values are.
• Are used for job parameters so that users can select a value for the parameter.
Your technical administrator can create lists of values sources, for example, one for
country names to be used for a Country parameter in a job definition. When users
schedule a process based on this job, they can select a country as a value for this
parameter.
The Manage List of Values Sources page is accessed using the same Manage
Custom Enterprise Scheduler Jobs tasks.

Lesson 1: Appendix
Example of Scheduler Job
Maintaining Person Keywords
Several attributes of person, employment, and profile records are used as person-
search keywords. Keyword values are copied automatically from the originating records
to the PER_KEYWORDS table, where they are indexed to improve search
performance.
Whenever the value of a keyword attribute changes (for example, if a person acquires a
language skill or a different phone number), an event is raised. In response, services
run a process to update the relevant attributes for the person in the PER_KEYWORDS
table; therefore, most changes are made in PER_KEYWORDS immediately and
automatically.
When you create a new person record, keyword values for that person are copied
automatically to the PER_KEYWORDS table.
Although most changes to the PER_KEYWORDS table are made automatically, you
need to run the Update Person Search Keywords process regularly because the
automatic process does not apply future-dated changes to the PER_KEYWORDS table.
Running the Update Person Search Keywords process also ensures that all changes
are copied to the PER_KEYWORDS table, despite any temporary failures of the
automatic process.
Scheduling the Update Person Search Keywords Process
You can run the Update Person Search Keywords process manually or schedule it to
run at regular intervals (for example, weekly at a specified time).
The likely volume and frequency of changes to person records in your enterprise will
determine how often you run the Update Person Search Keywords process:
• If the volume and frequency are high, you need to schedule the process to run
frequently.
• If the volume and frequency are low, running the process once a month is
recommended.
When you run the Update Person Search Keywords process, the whole
PER_KEYWORDS table is refreshed; therefore, you are recommended to run the
process at times of low activity to avoid performance problems.

Lesson 1: Appendix
Reference Resources
Related Resources:
• Oracle Fusion Applications Administrator's Guide
• Oracle Fusion Applications Common Implementation Guide

Lesson 1: Appendix
There are no demonstrations or activities for this
lesson

Lesson 1: Appendix
Lesson Highlights
In this lesson, you should have learned to:
• Describe what enterprise scheduler job definitions are.
• Identify the purpose of list of values sources.

Lesson 1: Appendix
Lesson Highlight Details
Enterprise Scheduler Job Definitions
An Oracle Enterprise Scheduler job is an executable that users can run to process
data, for example to validate invoices or create journal entries.
Related concepts include:
• Process or Scheduled Process: A unique submission or run of a job.
• Job Definition: The metadata for the job that allows it to be run.
• Parameters: Filters that users can set when they submit a process.
Predefined jobs are used in various Oracle Fusion applications. Your technical
administrators can create custom jobs and job definitions based on Java, PL/SQL, or
any other supported technology.
List of Values Sources
A list of values source:
• Determines where a list of values comes from and what the specific values are.
• Is used for job parameters so that users can select a value for the parameter.
Your technical administrator can create lists of values sources, for example, one for
country names to be used for a Country parameter in a job definition.

Lesson 1: Appendix
Define Help Configuration
This lesson describes the tasks in the Define Help Configuration task list, which
enable you to set up Oracle Fusion Applications Help:
• Set Help Options
• Assign Help Text Administration Duty
• Manage Help Security Groups

Lesson 1: Appendix
Objectives
After completing this lesson, you should be able to:
• Set options for the features available in the help system.

Lesson 1: Appendix
Set Help Options
Use the Set Help Options task from the Setup and Maintenance work area to control
the behavior of certain features in Oracle Fusion Applications Help. Some of these
options may not be available, depending on what is set for help feature choices on the
Configure Offerings page in the same work area.
• Collaboration Features: Enable or disable discussion forums and
announcements.
• Web Sites Available from Help Site: Enable or disable links in the global area
of Oracle Fusion Applications Help that go to Oracle web sites.
• Custom Help: Define the name and logo used to identify custom help. For
example, the logo would be displayed next to the title of custom help files in
search results. If you are using Oracle User Productivity Kit (UPK) content as
custom help, enter the default location where the UPK player packages reside.
• Oracle User Productivity Kit: If you are using UPK, you can provide a link in
the global area of Oracle Fusion Applications Help that goes to your UPK library.
Note: If you have UPK versions earlier than 3.6.1, then you cannot add UPK
demos as custom help, so the link is the only way for users to access custom
UPK content from the help site.
• Privacy Statement: Optionally replace the predefined privacy statement in the
footer of Oracle Fusion Applications Help with your own statement.

Lesson 1: Appendix
Instructor Note: Set Help Options Demonstration
-_-_-_-_-_- INSTRUCTOR NOTE -_-_-_-_-_-
Before class or before the demonstration, make sure that the two discussions-related
help options are selected, so that you can demonstrate disabling them.

Lesson 1: Appendix
Demonstration: Set Help Options
Background
Your company has a policy against employees participating in discussion
forums. You are setting up Oracle Fusion Applications Help and must disable access to
discussions.
Demonstration Scope
Deselect discussions-related help options and review the impact in Oracle Fusion
Applications Help.
Demonstration Steps
1. In the global area Help menu, select Applications Help.
Location: New browser tab with Oracle Fusion Applications Help showing
Information
The global area of Oracle Fusion Applications Help contains the Oracle Forums
link.
2. Open any help file to see the Discuss link.
3. Close the entire browser window for Oracle Fusion Applications Help.
4. In the Setup and Maintenance work area Tasks pane Name field, enter Set Help
Options.
5. Press Enter.
6. In the All Tasks section Set Help Options row, click Go to Task.
Location: Set Help Options page
7. In the Collaboration Features section, clear the Enable local discussions on
help option.

Lesson 1: Appendix
8. In the Web Sites Available from Help Site section, clear the Discussion
forums on Oracle Technology Network option.
9. Click Save and Close.
10.Repeat steps 1 through 3, this time checking that the discussion-related links are
no longer there.

Lesson 1: Appendix
Reference Resources
Related Resources:
• Oracle Fusion Applications Common Implementation Guide
• Oracle Fusion Applications security reference manuals
• Oracle Fusion Middleware Authorization Policy Manager Administrator's
Guide (Oracle Fusion Applications Edition)
• Oracle Fusion Applications Security Guide

Lesson 1: Appendix
Highlights
In this lesson, you should have learned to:
• Set options for the features available in the help system.

Lesson 1: Appendix
Define Profile Options
In this section, you will learn key concepts about:
• Profile Options
• Profile Option Categories
• Profile Option Levels and Values
• Common Profile Options to Set Up

Lesson 1: Appendix
Profile Options
Profile options are global configuration settings that users can modify to change the way
an application works. For example, settings such as user preferences and application
configuration parameters can be modified as per the user's requirements.
You can use profile options to modify:
• The look and behavior of the application's user interface
• User preferences such as settings used for social networking
• The business logic of the application
• Log settings and processing options that determine how and where information is
stored
A profile option is made up of the following:
• Name
• Application and module
• Values
• Categories
• Hierarchy level
You can modify any of these constituents of the existing profile options, but system
administrators must have enabled the profile option for modification.

Lesson 1: Appendix
Profile Option Categories
Profile options are grouped into categories depending upon the functional area in which
the profile options are used. For example, in Oracle Fusion Receivables, the
Transactions profile option category groups the profile options related to Receivables
transactions processing, such as Require Adjustment Reason, Invoices with
Unconfirmed Receipts, Use Invoice Accounting for Credit Memos, and so on.
Profile option categories facilitate searching and defining data security.
A profile option can be grouped into more than one category.

Lesson 1: Appendix
Profile Option Levels and Values
Profile Option Levels
In an application, the display and availability of profile options depends upon the
hierarchy level at which it is enabled. The different hierarchy levels are:
1. Site level - the lowest level of hierarchy that unless superceded by any other
level provides accessibility to all the users of the application, across the
deployment site. In a multi-tenant environment, Site is scoped per tenant.
2. Product level - the next level in the hierarchy that applies to the selected product
family (product offering within Oracle Fusion, such as Financials) and its specific
users. For the same user, the profile option at this level supercedes any site level
profile option setting.
3. User level - the highest level in the hierarchy that applies to the specific user or
user role and supercedes any product or site level setting that was earlier
associated with the user.
Profile options defined at higher levels override the profile options at the lower level.
Profile Option Values
Profile values determine application behavior that you want at the selected level.
Context such as user session or accessed product determines which profile option
value is associated with the profile option name.
The following example of the profile option FND_LANGUAGE shows how the profile
values determine the default language of the application at various levels.

Lesson 1: Appendix

Lesson 1: Appendix
Define Lookups
In this section, you will learn key concepts about:
• Lookups, their constituents, and their types
• Managing lookups

Lesson 1: Appendix
Key Concepts
Lookups are containers for the list items that appear in an application. Users select one
of the items from such lists to enter a value on the application UI.
Lookups consist of:
• Lookup Type - A lookup type is a static list of values users use to make entries
in the application. This is the name of the field that appears on the setup UI and
not on the application UI where you make the selection.
• Lookup Code - An internal application code for each lookup that is not visible to
users.
• Meaning - The actual UI term associated with the lookup code. It is the item that
appears in the list on the application UI against the specific field name, and can
be selected by the users to indicate their choice.
• Tag - The description or a label associated with that lookup.
• Enabled (status) - Determines the availability of the meaning (the value or the
item) within the selection list for that lookup type. If you do not enable it, the value
does not appear in the selection list at runtime.

Lesson 1: Appendix
As per the settings shown in the table, the users would see the following values in the
list on the application UI to determine the Ticket Class:
• Any
• Business
• Economy
There are three different categories of lookups:
• Standard Lookups - These are the simplest form of lookup types consisting of
lookup codes and their meanings.
• Common Lookups - These are predefined lookups and are available for internal
system administrative use and are used by more than one application.
• Set-enabled Lookups - These lookups contain lookup codes that are part of a
reference data. You can use sets to enable different values in that lookup for
different sets of users. At runtime, a selected attribute determines which set-
enabled lookup will be visible to the users. For example, the attribute east-coast
or west-coast in the determinant 'location' determines whether it is the 'east-
coast' or the 'west-coast' location, depending upon the selected lookup.
Lookup codes and their meanings are valid between a specified date range. If a date
range is not specified, the lookup codes and meanings have indefinite validity from the
time they are created.

Lesson 1: Appendix
Manage Lookups
Standard, common, and set-enabled lookups are defined in the Standard, Common,
and Set-enabled views, respectively. Applications development may define lookups in
an application view to restrict the UI pages where they may appear.
In lookups management tasks, lookups may be associated with a module and striped by
application taxonomy to provide a criterion for narrowing a search or limiting the number
of lookups accessed by a product specific task such as Manage Purchasing Lookups.
Enabling Lookups
You can create new lookup types and also add new lookup codes and meanings to the
existing lookup types, depending upon the access permissions granted to you. But for
the lookups and lookup values to appear as values in the lists, they need to be enabled.
To enable a lookup type, you need to enable at least one of its lookup codes and that
code must be in a valid date range.
You can access this task from the Setup and Maintenance menu.
Customizing Lookups
Oracle applications contain certain predefined system lookups that are locked for
editing. You can only customize the lookups that are left open for extensibility. Even if a
lookup is available for customization, the customization levels may vary depending upon
the access restrictions. For example, you may modify the meanings of certain
predefined lookup codes but may not have the permission to create new lookup codes.

Lesson 1: Appendix
Oracle Fusion Watchlist
The Watchlist is an Oracle Fusion component that is categorized by functional area and:
• Provides a set of shortcuts to work areas based on items that a user wants to
monitor
• Presents a list of pre-queried searches (saved searches or standard queries) of
items that the user needs to track.
Each item is made up of descriptive text followed by a count. Each item is also linked to
a page in a work area where the individual items of interest are listed.
Example of a watchlist

Lesson 1: Appendix
Oracle's Cloud Architecture

Lesson 1: Appendix
Instructor Note: Oracle Cloud Terminology
The following terminology definitions are provided as a courtesy reference for learners
and are not meant to be covered during class.

Lesson 1: Appendix
Oracle Cloud Terminology
The following terminology is used when describing the Oracle Cloud features and
functionality.
Account
A unique account that corresponds to an individual or company that is an Oracle
customer. The account can have many Oracle Cloud services and has one or more
identity domains.
Identity Console
A self-service administration tool of the identity management application that is used in
the provisioning and management of service end users for all Oracle Cloud services.
Identity Domain
A collection of user and password pairs that identify users allowed to use services
associated with the domain. Identity domains control authentication and authorization,
that is, who can sign in and what they can access after they sign in.
• Multiple services can be associated with a single identity domain to share user
definitions and authentication.
• Users in an identity domain are granted different levels of access to different
services associated with the domain.
Service
A type of application or platform service offered by Oracle Cloud.
Service Alerts
Indicators in the first column of the My Services pages that show the status of the
service.
• If the icon is green, the service is up and running.
• Other statuses display as red and yellow, with the meaning shown in the hover
text.
Service Lockout
The process of locking a service to prevent service users from accessing Oracle Cloud
services or any deployed applications.
Note: When a service is locked, administrators can still manage the service and
perform operations through the Identity Console.
Service Metrics

Lesson 1: Appendix
Utilization data that is shown on the My Services Service page and Overview and
Utilization tabs on the service details page.
Service Name
A name that you assign to your service, which must be unique within the identity
domain. You can add a longer description to a service to help you identify it, after it is
activated.
Service Notifications
Events reported on the Notifications page that do not require administrative action. They
provide information about upcoming system-wide and service-specific events, such as
outages and blackouts.
Trial Services
Services that are available for a limited time period, for trial purposes only.
Utilization
Metrics that show on the:
• My Services Service page (two key metrics)
• Service details page Overview tab (last usage for all metrics tracked)
• Utilization tab (history and latest usage)

Lesson 1: Appendix

27 appendix

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (15)

Similaire à 27 appendix

Similaire à 27 appendix (20)

Plus de mohamed refaei

Plus de mohamed refaei (10)

Dernier

Dernier (20)

27 appendix