Professional Documents
Culture Documents
About ERPWebTutor
• Launched in 2012 as a video blogging site
• 600+ hours content created
• Trained over 6000 students
• Visitors from 130+ countries
• Helped students change careers and succeed in Oracle ERP areas
Day 1 - Agenda
• Chapter 1: Introduction to Fusion Payroll
• Chapter 2: How Fusion Payroll works – Live demo
• Chapter 3: Functional Setup Manager Overview
• Chapter 4: Getting Started for Payroll Implementation
➢ Implementation Project
➢ Manage features for Payroll
➢ Setting up the Payroll Roles
➢ Creating additional users and assigning roles
➢ Geography Setups
➢ Tax Load
• Chapter 5: Common HCM Configurations
➢ Legislative Data Groups
➢ Cost Allocation Key Flexfield
• Multi-Country support.
• Supports out-of-the-box
payroll interfaces with
major providers like ADP.
• Automatic Retro processing
functionality
• Increased flexibility – ability
to define customer specific
payroll processes
Payroll Dashboard
• Option: Each Oracle Fusion offering, in general, includes a set of core functionality
and a set of optional modules, which are called options. It is a part of an offering but
is not required for an offering to be operational.
Example: As well as core functionality, Compensation Management includes
optional functionality such as:
• Individual Compensation
• Workforce Compensation
• Total Compensation Statements
These optional functionality may not be relevant to all Oracle Fusion Application
implementations. You can selectively choose to implement only those options that
are applicable to your business requirements.
Feature: Unit of functionality that is part of an offering or option and identifies a rule for
a specific business process. You make feature selections according to business
requirements, to get the best fit with the offering.
Example:
Compensation has features such as:
Local Installation of Help
Maintain Common Reference Objects
Implementation Project: An implementation project is the list of setup tasks that are
required for implementations of specific offerings and related options. Implementation
projects are also the foundation for identifying what setup data will be exported and
imported, and in which order.
Task List: List of sequenced setup tasks required to enable business functionality
Scope: Sets the context of the task list and the setup data to export and import.
• Applications
Implementation
Consultant – Use this
for majority of the
configurations
• Payroll Administrator – Use this role for payroll processing and setups
*Payroll Manager role inherits Payroll Specialist role. So just Payroll Manager View All role should suffice in most cases.
• A project can have multiple implementation users. These users must be setup
in the OIM area.
• You can perform the task Run User and Roles Synchronization Process from
an implementation project or the Setup and Maintenance work area.
Points to Remember
The product usage settings control the availability of payroll-related features, such as
element templates, for each country or territory. For example, you may have one country
in your enterprise using Payroll and another using Payroll Interface.
For processing payroll in Fusion MAKE SURE you have the following settings:
The Load Payroll Tax Information for US process is necessary to maintain tax data changes
from Vertex in the Oracle Fusion application. Vertex publishes monthly updates that
contain tax data changes (QFPT.dat file). For SaaS customers, Oracle Product Services
installs the files. The On-Demand team installs the files for the customers when they are
requested to do so by their customers. On-Premise customers install the file themselves.
Once the files are installed, all customers (including SaaS) must run the Load Payroll Tax
Information for US process to update their tax data. You must run this process as part of
the initial setup for the implementation project as well as upon a monthly basis.
• A legislative data group is a boundary that can share the same set up and still comply
with the local laws.
• Used for driving legislative requirements (e.g. when a selecting a legal entity that
belongs to the US legislative data group, SSN is used for storing national identifier.
• Associated with a country, currency and cost allocation key flexfield structure.
The Cost
Allocation KFF
structure can
also be set at the
legal entity level
Thank you
Visit us at www.erpwebtutor.com