Objective:

In the previous article Oracle SOA suite, webcentre Portal,  Webcentre Content, Identity Management schemas and Installation we learned about the schemas in Fusion Middleware. In this article we will learn about the configuration required for the installation of Fusion Middleware.

Fusion Middleware Installation

Supported configuration overview:-

Before we start with Installation we need to check whether the products are certified and supports the operating system where we will install Middleware stack.

• Check and verify system requirements.

• support.oracle.com -->certifications

• Excel sheet with all the certifications.

Obtained certified version of FMW from below website:

http://www.oracle.com/technetwork/middleware/fusion-middleware/downloads/index.html

Memory Requirements of operating system:-

Hardware and System Requirements:

RPMS(Red Hat Process Package Managers)

when we install some softwares on linux, there are some binaries that help the software to get installed on linux machine. Like in Windows we have DLL likewise in linux we have RPMS. we need the RPMS for database also.

Below is the list of RPMS.

Setting Open File Limit:-

• on all the Linux system, the minimum Open FIle limit should be set to 4096. Below are the commands to change open file limits:

1. Log In as Root user

2. Locate and open the following OS configuration file:

/etc/security/limits.conf

3.   Look for and modify below in limits.conf:

*soft nofile 4096

*hard nofile 65536

*soft nproc 2047

*hard nproc 16384

4.   save the changes and close the limit.conf file.

5.   If you are using Linux 6 o0r Red Hat Linux 6, locate the following operating system configuration

           file.

           /etc/secutiy/limits.d/90-nproc.conf

6.   Make sure the same values are added to the 90-nproc.conf.file; otherwise, the values in the

           90-nproc.conf.file can override the values in the limits.conf file.                       

7.   Reboot the Machine.

special startup requirements for linux 32-64 bit operating system for Oracle Universal Intaller.

1. change the value for SHMMAX to 4294967295 by including the following line in/etc/sysctl.conf:

kernel.shmmax=4294967295

2.   Activate the new SHMMAX setting by running the command:

/sbin/sysctl -p

3.   Start the Universal Installer and install the software.

Objective: In this article we are going to learn how to install Oracle Linux 6.5

Oracle Linux 6.5 Installation:

1. Log on to www.oracle.com

2. Now look for Downloads at the top of the Website. Click on Downloads and it will give you some options. Under Server and storage system select the option Linux and Oracle VM.

 But before the downloads gets started, it will ask the user to Sign in.

 4. Now Type Oracle Order Management and select the platform depending on the type of machine. for e.g. We have selected elected Linux x64-86, as shown in the screenshot below.

5 Once the platform is selected, click on continue.

6. Then it will ask you to Accept the agreement. select the checkbox and then click on Continue.              

 7. Now Download all the Files.

 Once all the files are downloaded, run the .exe file and then it will show the below screen:

Press Enter Key

Select Skip

Click Next

Select Language(English)

Click--->Next

Select Basic Storage Option--->Next

Click on yes, discard any data--->Click Next

Give the hostname e.g icm-ind.oracle.com

Click Next---->

Select the country--->Click Next

Select the create custom Layout --->Click Next

 Manual partitions

/bootext48000MB

swap40000MB

/ext4fill to all allowable size

After partitions click--->Next

Click on write changes to disk

Click Next

Select Customize now --->Click Next

Select the Below Packages:

Base system Packages

Base, Hardware monitoring utilities, Large System Performance, Network File system client, Performance tool, Perl support

Server packages

Server platform, System Administration tools.

Desktop packages

Desktop, desktop platform, Fonts, General purpose Desktop, Graphical administration tools, Input methods, X Windows System.

Application Packages

Internet Browser

Development Packages

Additional Development, Development Tools

Click Next

Pre-Request to Install R12.2

Disable firewall

Click Close 

Click on Disabled 

Click on Apply & Close

Disable Selinux

[root@icm Desktop]# vi /etc/selinux/config

Change SELinux=disabled

Apply the following commands

chkconfig iptables off

chkconfig ip6ables off

service iptables stop

service ip6tables stop

Install Linux Packages

install packages with rpm –ivh package_name command

1. binutils-2.20.51.0.2-5.11

2. gcc-4.4.4-13.el16.x86_64

3. gcc-c++-4.4.4-13.el16.x86_64

4. glibc-2.12-1.7.el6.x86_64

5. glibc-common-2.12-1.7.el6.x86_64

6. glibc-devel-2.12-1.7.el6.x86_64

7. libgcc-4.4.4-13.el6.i686

8. libgcc-4.4.4-13.el6.x86_64

9. libstdc++-devel-4.4.4-13.el6.x86_64

10.libstdc++-4.4.4-13.el6.x86_64

11. libaio-0.3.107-10.el6.i686

12. libaio-0.3.107-10.el6.x86_64

13. libgomp-4.4.4-13.el6.x86_64

14. make-3.81-19.el6.x86_64

15. gdbm-1.8.0-36.el6.x86_64

16. sysstat-9.0.4-11.el6.x86_64

17. util-linux-ng-2.17.2-6.el6.x86_64

18. compat-libcap1-1.10-1.x86_64

19. compat-libstdc++-33-3.2.3-69.el6.x86_64

20. elfutils-libelf-devel-0.148.1-el6.x86_64

21. libaio-devel-0.3.107-10.el6.x86_64

22. unixODBC-2.2.14-11.el6.x86_64

23. unixODBC-devel-2.2.14-11.el6.x86_64

24. xorg-x11-utils-7.4-8

install following packages with yum install package_name command

Create User & Groups

groupadd dba

groupadd oinstall

adduser –G dba –g oinstall oracle

asswd oracle

mkdir /u01

Chown –R oracle:oinstall /u01

Host and Settings

vi /etc/hosts

192.168.1.99 icm.oracle.com icm

vi /etc/resolv.config

Options attempts:5

Options timeout:15

# ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

mv /usr/bin/unzip /usr/bin/unzip-ver6

copy unzip from below folder to above folder

Objective:

In previous article Oracle Linux 6.5 Installation we learned how to install linux in a machine. In this article we will learn about the Oracle EBS R12.2 installation.

Oracle EBS R12.2 Installation:

Run the command

Stage122/startCD/Disk1/rapidwiz/rapidwiz

Click Next

Click Next

Click yes

Click Next

Click Next

Set Passwords & Click Next

Click Next

Click next

Click Yes

Introduction

This article is the second part of the series “An Overview of Fusion Absence Management”.

To access the first part, please click on: “An overview of Fusion Absence Management Part 1 Absence Plan Definition and Use”

Before we start to understand How to create an Absence Type first try to understand what a Absence Type is and why is it required.

An absence type as the name suggests refers to different types of absences like Sick Leave, Annual Leave, Vacation Leave, Marriage Leave, Compassionate Leave, Maternity leave, Paternity Leave and you can keep on expanding so on and so forth.

Basically in a nutshell, all the various reasons / events / activities for which a Leave Application may be raised can be treated as Absence Type (context being Fusion Absence Management).

So before we jump into a typical business requirement and dig deep into how to fulfill the same let-us try to familiarize ourselves with some of the most commonly used terms which would be referred in the ongoing article:

Absence Pattern

This could be defined as the broad level categorization of different leave types like General Leave, Illness, Injury … special leave types.

In context of Fusion Absence Management there are 3 different types of Patterns (available as of today) namely :

Legislation

Geography / Country where this Absence Type is Maintained. For Example if we are doing Absence Type setup for India Legislation would be India , if we are doing for USA it would be United States and so on....

Absence Type UOM

Unit of Measure which states in which unit (either of Days / Calendar Days / Hours) will this Absence Type will get measured

Business Requirement

Now since we are aware of some of the most commonly used terms for an absence types we should try to create one absence type .Requirement is to create an Absence Type of Pattern Generic Absence.

Perquisites:

You need to have an already created Absence Plan available to attach to the absence Type (we did same in Absence Article 1 so we are good)  . Also we would assume that we have an absence reason already created in the application to use.

Setup Steps

In this example to keep things simpler we would only discuss about the Mandatory Details required to create an Absence type (fields which are mandatory are generally highlighted with an asterisk mark beside them),  A complete detail of all fields could be covered in next article.

Navigation is as shown below:

Click on Go to Task Button

Click on Create Button and populate the following details:

You may populate the following screen with above details

Each absence plan setup requires four Tabs to be filled namely (screen-shot reference).

1. TYPE ATTRIBUTES

Contains Details about Type Name, Description, UOM, Legislative Data Group, Status, Duration Rules , Absence Record Maintenance, fast formulas Conversion Formula , Validation Formula along with Eligibility Profile associated with a particular absence type

Populate the following values (displayed in tabular format below)

2. PLANS AND REASONS

Contains Details about Effective Start Date, Plan, Status Priority as shown in below screenshot :

Also select an Absence Reason as shown:

The page after filling details should look like:

DISPLAY FEATURES

This page comes with default values populated and for the sake of simplicity let-us keep them as is  the page appears as shown below

ACTION ITEMS

Used to configure any specific actions to be triggered / executed / performed whenever this leave type is applied. Not applicable for current example hence ignored for now. We keep this page as blank as shown below;

Once all the above setup is done Absence Type Creation is complete.

 {jcomments off}

Objective:

In the previous article we seen the Introduction of Middleware and different types of Web services. In this article we will learn about the Oracle Fusion Application architecture.

Oracle FMW Architecture:

It mostly comprises of Fusion Application and Fusion Middleware

Fusion Middleware:

It comprises of oracle application server. Middleware is a family of middleware products covering all the areas such as: BI(Business Inclusion), IDM(Identity Management), Content, SOA, BPEL.

Fusion Application:

Fusion application is build on top of Fusion middleware technology. It uses Fusion architecture as the Blueprint. Modules of Fusion Applications are:

Any of these applications can be installed. If you face any issues in installing any of these applications, then install HCM before installing that application.

Simplified Architecture of Fusion Middleware:

This is a 3-tier architecture:

1. Database tier:

Oracle Internet Directory

Oracle Virtual Directory

Oracle Database

2. Oracle Weblogic Server

Oracle SOA suite

Oracle Webcenter

Oracle Web cache

3. Web tier

Oracle Web centre

Web http server

HTTP 80- it is a simple HTTP request

HTTP 443- Secured request.

Objective:In the previous article we learned about the Oracle EBS R12.2 installation. In the article we are going to learn about the E-business Suite Architecture.

Oracle E-Business Suite Architecture

The Oracle E-Business Suite Architecture is consist on three tiers.

1. The Client (Desktop) Tier

2. The Application Tier

3. The Database Tier

Client Tier and Application Tier Components

Client Tier, Application Tier and Database Tier Components

File System Structure

An Oracle E-Business Suite Release 12.2 system utilizes components from many Oracle products. These

product files are stored below a number of key top-level directories on the database and application

server machines.

Oracle E-Business Suite Release 12.2 uses a dual file system, one file system designated “run edition”,

while the other designated “patch edition”. These two file systems are often referred to as fs1 and fs2.

There is also one more file system which is called non-editioned file system (fs_ne). This file system is

used to store files containing data that is needed across all file systems.

File System1 (FS1)

• Stores a complete copy of all applications and Middle Tier code

File System2 (FS2)

• Stores a complete copy of all applications and Middle Tier code

File System NON Editioned (FS_NE)

• Stores data that is written or read from the file system

• Report Outputs

• Log Files etc

Patch_Top

Start & Stop Database & Application Services.

How to Stop & Start Database and Application Services

1. Start database:

[oracle@icm~]$ /u01/oracle/PROD/db/tech_st/11.2.0/appsutil/scripts/PROD_icm/addbctl.sh start

2. Stop database:

[oracle@icm~]$ /u01/oracle/PROD/db/tech_st/11.2.0/appsutil/scripts/PROD_icm/addbctl.sh stop immediate

3. Start & Stop listener:

[oracle@icm~]$ /u01/oracle/PROD/db/tech_st/11.2.0/appsutil/scripts/PROD_icm/addlnctl.sh stop/start PROD

4. Start & Stop application Services:

[oracle@icm~]$ /u01/oracle/PROD/fs1/inst/apps/PROD_dserver/admin/scripts/adstrtal.sh/adstpal.sh

Objective:

In the previous article Oracle E-Business Suite Architecture we learned about the basic architecture of E-Business Suite. In this article we will learn how to upgrade oracle EBS R12.2.0 to R12.2.4

Upgrade Oracle EBS R12.2.0 to R12.2.4:

Install Oracle RDBMS Opatches

Step 1:Install following patches

Shutdown application & database services.

a) 16989137

Go to patch Patch_top

[oracle@icm 16989137]$ /u01/oracle/PROD/11.2.0/OPatch/opatch apply

b) 17875948

c) 17912217

d) 18419770

e) 18614015

f) 18685209

g) 19078951(rool back patch 18259911)

[oracle@icm OPatch]$ opatch lsinventory | grep 18259911

[oracle@icm OPatch]$ opatch rollback -id 18259911

h) 19393542

Now run the following patches sql scripts

a) 16989137

b) 17875948

c) 18614015

i) 17537119 apply this patch for check db

Now Install Oracle Fusion Middleware 11.1.1.6 patches

First set Oracle home for middleware

export ORACLE_HOME=/u01/oracle/PROD/fs1/FMW_Home/webtier

export PATH=/u01/oracle/PROD/fs1/FMW_Home/webtier/OPatch:$PATH

#opatch lsinventory

opatch apply –jre $ORACLE_HOME/jdk/jre

17639414

[oracle@icm ]$ export ORACLE_HOME=/u01/oracle/PROD/fs1/FMW_Home/oracle_common/

export PATH=/u01/oracle/PROD/fs1/FMW_Home/oracle_comn/OPatch:$PATH

[oracle@icm 18989444]$ opatch apply

Also apply patch 19462638 with same way.

Install Oracle 10.1.2.3 Forms & Reports Patches:

Set environmental variable

18186693

opatch apply

Install Oracle Weblogic server (10.3.6) Patches:

And unzip in this directory /u01/oracle/PROD/fs1/FMW_Home/utils/bsu/cache_dir

Cd /u01/oracle/PROD/fs1/FMW_Home/utils/bsu

#./bsu.sh

Installation Of EBS Application patches:

The Online Patching Cycle

The online patching cycle is divided into five phases:

Patching Cycle Overview:

1. Prepare

• Synchronizes patch edition and run edition on the file system.

• Creates a new patch edition in the database.

2 Apply

• Executes patch drivers to update patch edition.

• Patches applied: can be one or many, including customizations.

3. Finalize

• Compiles invalid objects.

• Generates derived objects.

4. Cutover

• Configures patch edition file system to be the new run edition file system.

• Configures patch edition of database to be the new run edition.

• Restarts application tier services.

5. Cleanup

• Delete obsolete code and seed data to recover space.

Oracle Applications DBA (AD) Utility

The Oracle Applications DBA product provides a set of tools for administration of the Oracle E-Business

Suite file system and database. AD tools are used for installing, upgrading, maintaining, and patching the

Oracle E-Business Suite system.

The AD utilities include:

AD Administration - Performs general maintenance tasks for Oracle E-Business Suite.

AD Merge Patch - Merges multiple patches into a single, integrated patch.

AutoConfig - Manages configuration changes to components that are specific to an Oracle

E-Business Suite system. Configuration changes to technology components that are not specific

to Oracle E-Business Suite are managed via the native tools for those components.

AutoPatch - Applies patches and adds new languages and products to an Oracle E-Business

Suite system. In Oracle E-Business Suite Release 12.2, adop (AD online patching) is used, rather

than adpatch which is used in previous releases.

To install Application Patches we need to start all services

Below all patches apply with hot patch option

Copy the patches in following location

/u01/oracle/PROD/fs_ne/EBSapps/patch

17204589

adop phase=apply patches=17204589 hotpatch=yes

18283295 also run adgrants sql script

19581770

18288881

19445058

19259764

Now run bellow command

[oracle@icm]$ cd /u01/oracle/PROD/

[oracle@icm]$ . EBSapps.env

[oracle@icm]$ adop phase=fs_clone

Now Apply update patch with adop command as above.

17919161

[oracle@icm]$ adop phase=apply patches=17919161 hotpatch=yes

17919162 on same way

The upgrade form 12.2.0 to 12.2.4 completed.

Objective:

In the previous article we learned how to upgrade oracle EBS R12.2.0 to R12.2.4. In this article we will learn about the Cloning of R12.2.4 and User creation.

Cloning R12.2.4:

1. Source Application Env on run edition

2. Run fs_clone

3. Run Autoconfig on Appstier

4. Synchronize Appsutil on database node through admkappsutil.pl utility

a. On the application tier:

i. Run EBSapps.env.

EBSapps.env RUN

ii. Create the appsutil.zip file by running the following command:

$ perl <AD_TOP>/bin/admkappsutil.pl

This will create appsutil.zip in <INST_TOP>/admin/out.

b. On the database tie:

i. Copy the appsutil.zip file to the RDBMS ORACLE_HOME, then run the following

commands:

ii. $ cd <RDBMS ORACLE_HOME>

$ unzip -o appsutil.zip

5. Runautoconfig on DBtier

6. Update current view snapshot through adadmin utility

7. Run preclone on appstier

Log on to the primary node of the Source System as the applmgr user.

Source the environment file of the Run Edition File system.

Execute the following commands:

$ cd <INST_TOP>/admin/scripts

$ perl adpreclone.pl appsTier

8. Run preclone on dbtier

Prepare the Source System database tier for cloning

a. Log on to the Source System as the oracle user.

b. Source the Database tier environment file.

c. Execute the following commands:

$cd <RDBMS ORACLE_HOME>/appsutil/script/<CONTEXT_NAME>

$ perl adpreclone.pl dbTier

9. Shutdown Application & Database Services

10. Copy database file from source to target system

11. Copy database file from source to target system

12. Copy Application run-edition file system from source system to target system

Donot copy FMW_Home, inst files

13. Configure the Target System Database Tier

$ cd <RDBMS ORACLE_HOME>/appsutil/clone/bin

$ perl adcfgclone.pl dbTier

14. Configure the Target System Application Tier

$ cd <COMMON_TOP>/clone/bin

$ perl adcfgclone.pl appsTier

15. Run adpreclone on Target Run file system

$cd $ADMIN_SCRIPTS_HOME

$ perl adpreclone.pl appsTier

16. SHUTDOWN THE APPLICATION which is running on RUN FILESYSTEM

17. COPY THE TARGET RUN FILESYSTEM to TARGET PATCH FILESYSTEM

Only EBSapps

18. UNSET the application Enviroment.Previously

19. Before we run adcfgclone.pl dont run any env's, Directly go to

/u02/apps/fs2/EBSapps/comn/clone/bin/ and execute adcfgclone.pl

$ cd /u02/apps/fs2/EBSapps/comn/clone/bin

$ perl adcfgclone.pl appsTier

Target System File Edition type [run] : patch

Once done everything. Start the application Tier using adstral.sh

User Creation

Url : http://icm.oracle.com:8000

Login Page

Responsibility: System Administrator  Security user define

Enter user name & password(Enter password two time).

Add responsibility to user.

Click on save button.

Now login with Noor Hassan User

Click on Login

Enter current & new password

How to Create Menu

Responsibility: System AdministratorApplicationMenu

Enter the following Information

1. Enter Menu Name ICM_TEST_GL_MENU

2. Enter the Submenu Names

3. Save

How to create Request

Write simple select query

Select ledger_id from gl_ledgers;

Save it as ledger_sql.sql

Copy this sql script to location on the server

/u01/oracle/PROD/apps/apps_st/appl/gl/12.0.0/sql

Create executable for this script in Oracle APPS

Responsibility: System AdministratorConcurrentProgramExecutable

Click Executable

Give the above information

Save

Now define concurrent program

Responsibility: System administrator-->Concurrent-->Program-->Define

Give the above information

Save

How To Create Request Group

Responsibility: System Administrator-->Security-->Responsibility-->Request

Click-->Request

Give the Request Group Name

Application Name

Give the Concurrent Group Name( which we defined in previous step)

Save Work

Now Add this Request Group to Responsibility

Responsibility: System Administrator-->Security-->Responsibility-->Define

Click on define

How to Create Responsibility

Create Responsibility

Assign the menu which we defined in previous steps(Icm General Ledger Test Menue)

Assign Request Group which we defined in previous step

Save the work

Now assign this responsibility to user(in our case Noor Hassan)

Responsibility: System Administrator-->Security-->User-->Define

Save the work.

Now open the responsibility “TEST ICM” which we assigned to Noor Hassan User

Now we can see two submenu which we assigned during the menu creation.

How to run the Request

Go to View-->Request

Click on requests

Click on Submit a New Request

Click ok

Enter the request name

Click Submit

Click On No

Click on find

Click on View Output

The output of the query showing the ledger ids

Flexfield Creation

Responsibility : System Administrator-->Application-->Flexfield-->Key-->Segment

Give the Flexfield Name

Click on Segment

Enter the information & Save

Now create value set

Create values set for all the segments and assign to the segments

Objective:
In this article we will learn about the Request Response Pattern in SOA.

Request Response Pattern:

The following Request Response Patterns are covered in this appendix:

1. One way message

2. Synchronous Synchronisation

3. Asynchronous Interaction

4. Asynchronous Interaction with Timeout

5. Asynchronous Interaction with Notification Timer

6. One Request, Multiple Responses

7. One Request, One or Two possible Responses

8. One Request, a Mandatory Response, and an Optional Response

Request-response patterns are used to facilitate communication between the components of a Business Process Execution Language (BPEL) process. The request-response operation includes one input element (the request) followed by one output element (the response).

A one-way message interaction pattern is a special type of request-response pattern, where the client sends a message to the service, and the service does not need to reply. This could be used for business updates if the requester trusts the message service and the transaction not to fail.The communication pattern for the one-way message interaction involves:

• A service consumer:The client that invokes the service and supplies the input message

• A service provider:The service that accepts an input message from the service client, and does not provide a response (output message) The diagrams show various implementations of a one-way message interaction pattern, such as:

• A Mediator component with a routing rule to a service

• A BPEL component to a service

In a synchronous interaction, a client sends a request to a service, and receives an immediate reply or fault.The service can be at either end of this interaction, and is implemented based on its role as the client or the service. The image in the slide shows two diagrams of a synchronous interaction between two SOA components.

A BPEL process component client with a BPEL process component service

• The BPEL client contains an Invoke to manage the request-response cycle.

• The BPEL service contains a Receive to obtain the request message, and then after some processing, return a response by using a Reply, or throw a fault condition.

A Mediator component client with a BPEL process service

• The client contains a synchronous route to send the request to a BPEL service, and receive the response or fault.

The BPEL service contains a Receive to obtain the request message, and then after some processing, return a response by using a Reply, or throw a fault condition.

In an asynchronous interaction, a client sends a request to a service and waits until the service replies.The image in the slide shows two diagrams of an asynchronous interaction between two SOA components.

A BPEL process component client with a BPEL process component service

• The BPEL client contains an Invoke to initiate the request and do some processing, and a Receive to obtain the response.

• The BPEL service contains a Receive to obtain the request message, and then after some processing, return a response by using an Invoke to the client callback port.

A Mediator component client with a BPEL process service

• The client contains an asynchronous route to send the request to a BPEL service, and wait for a response.

• The BPEL service contains a Receive to obtain the request message, and then after some processing, return a response by using an Invoke to the client callback port.

In this interaction type, the client sends a single request to a service, and receives multiple responses in return. For example, the request can be to order a product online, and the first response can be the estimated delivery time, the second response can be payment confirmation, and the third response can be a notification that the product has been shipped. In this example, the number and types of responses are expected.

• The BPEL Process client:When the BPEL process is on the client side of this transaction, it needs an Invoke activity to send the request, and a sequence activity with three Receive activities, one for each reply.

• The BPEL Process service:The BPEL service needs a Receive activity to accept the message from the client, and a sequence attribute with three Invoke activities, one for each reply.

In this type of interaction, the client sends a single request to a service, and receives one or two responses. Here, the request is to order a product online. If the product is delayed, the service sends a message to inform the customer. In any case, the service always sends a notification when the item ships.

• The BPEL Process client:When the BPEL process is on the client side of this transaction, it needs a Scope activity containing the Invoke activity to send the request, and a Receive activity to accept the mandatory reply. The onMessage handler of the Scope activity is set to accept the optional message and instructions on what to do if the optional message is received (for example, notify you that the product is delayed). The client BPEL process waits to receive the mandatory reply. If the mandatory reply is received first, the BPEL process continues without waiting for the optional reply. As with all partner activities, the WSDL file defines the interaction.

• The BPEL Process service:The BPEL service needs a Scope activity containing the Receive activity and an Invoke activity to send the mandatory shipping message, and the Scope activity’s onAlarm handler to send the optional delayed message if a timer expires (for example, send the delayed message if the item is not shipped in 24 hours).

In an asynchronous interaction with a timeout, a client sends a request to a service and waits until it receives a reply, or until a certain time limit is reached, whichever comes first.The sample implementation in the slide shows:

•A BPEL process client, which uses an Invoke to send an asynchronous request to the service, and a Pick activity with:

-An onMessagebranch to receive the response (callback)

-An onAlarmbranch to manage the timeout condition if it occurs before the response is receivedNote:If the response comes after the time limit has expired, the message goes to the dead letter queue.

•A BPEL Process servicethat contains a Receive to obtain the request message, and then after some processing, return a response by using an Invoke to the client callback port.

In an asynchronous interaction with a notification timer, a client sends a request to a service and waits for a reply, although a notification is sent after a timer expires. The client continues to wait for a reply from the service even after the timer has expired.

•The BPEL Process client:When the BPEL process is on the client side of this transaction, it needs a Scope activity containing an Invoke activity to send the request, and a Receive activity to accept the reply. The onAlarm handler of the Scope activity has a time limit and instructions on what to do when the timer expires. For example, wait 30 minutes, and then send a warning indicating that the process is taking longer than expected. As with all partner activities, the WSDL file defines the interaction.

•The BPEL Process service:As with a synchronous transaction, when the BPEL process is on the service side of an asynchronous transaction, it needs a Receive activity to accept the incoming request, and an Invoke activity to return either the requested information or a fault.

In an interaction using one request and one of two possible responses, the client sends a single request to a service and receives one of two possible responses. For example, the request can be to order a product online, and the first response can be either an in-stock message or an out-of-stock message. The diagram in the slide provides an overview.

•The BPEL Process client:When the BPEL process is on the client side of this transaction, it needs the following:

-An Invoke activity to send the request

-A Pick activity with two branches: one onMessage for the in-stock response and instructions on what to do if an in-stock message is received, and a second onMessage for the out-of-stock response and instructions on what to do if an out-of-stock message is received

•The BPEL Process service:The BPEL service needs a Receive activity to accept the message from the client. It also needs a Switch activity with two branches: one with an Invoke activity that sends the in-stock message if the item is available, and a second branch with an Invoke activity that sends the out-of-stock message if the item is not available.

In this interaction type, the client sends multiple requests to multiple services and receives multiple responses in return. As shown in the slide, the service client (which is a BPEL process) uses a parallel flow to coordinate the request and response interactions from two different services. In this case, two asynchronous callbacks execute in parallel context, so that each callback does not have to wait for the other to complete. However, the flow does not complete until all responses are received.An example of such request-response pattern is implemented in the purchase order course application where the fulfillment process sends a request to determine stock availability in two different stores, an internal and an online store. The process waits for both responses before it chooses the store that is used to acquire the stock to fulfill the order for shipment purposes. Another example is a loan broker process that requests and retrieves loan offers from multiple loan service providers.

In this interaction type, the client sends multiple requests to different services and expects to receive multiple responses. However, to implement the first message response pattern, a Pick activity is used to receive the first of many possible responses, because a Pick processes only the first message to be received for any of its onMessage branches.

As shown in the slide, the service client (which is a BPEL process) uses a parallel flow to initiate asynchronous requests for two different services. Instead of using two asynchronous callbacks in parallel flow, when the flow is completed, a Pick activity is used to wait for all possible responses, in this case, one of two responses. The first response to arrive is processed, from service 1 (as shown in the diagram), and the other response message is not processed because Pick has completed and the service client process continues without waiting for additional responses.

Objective:

In the previous article Request Response Patterns in SOA we have learned about the different types of Request Response Patterns in SOA. In this article we will learn about the Introduction to Service Oriented Architecture.

Introduction to Service Oriented Architecture(SOA):

SOA is is an IT strategy that organizes the discrete functions, contained in enterprise applications into interoperable, standards-based services to be combined and reused quickly to meet business requirements.

Service-oriented architecture attempts to overcome many of the shortcomings of earlier integration technologies by embracing the concept of a service. A service is a discrete, decoupled unit of business functionality that is exposed and available to (ideally) all applications in the enterprise.

Services are the building blocks for a SOA-enabled application. They have functionality-described standard interface and message structure definitions. Multiple services are assembled and reused to more quickly create applications that can better support changing business processes.

The SOA approach to software systems enables a consumer of a service to be decoupled from the service provider. With SOA, services are accessed by using standard protocols (the glue), which enable interoperability from decoupled functions.

When embarking on a SOA approach to systems integration, integrators begin by examining business process requirements to identify functionality to be used as a ―service‖ unit to help complete a business process. A service portfoliois identified from a set of services that are required for implementing one or more business processes within a business domain. A service portfolio can be realized by a combination of new and reused functionality. Existing functionality can be wrapped as services by using the adapter technology. New services can be created with SOA-enabled technologies, including web services, SCA composite applications, BPEL, and a service bus. When a collection of services has been identified to serve a business process, it is recommended to store information about these services, their interfaces, and their message structures in a common location such as an enterprise repository. This facilitates sharing and reusability from design through production. Coupled with a service registry, an enterprise repository can migrate runtime service information into the development, test, and production operational environments. Coupling an enterprise repository and a service registry enables an organization to implement strong SOA governance strategies for services throughout a service’s life cycle, from the design-time environment to the runtime environment.

When a satisfactory service portfolio is created, the necessary services are assembled to form a composite application to address a specific business requirement. Services are reused as appropriate in multiple composite applications. As a result, development time and redundant functionality are dramatically reduced.

Service Component Architecture:

Service component Architecture(SCA) is a set of specifications that describe a model for building applications by using a service oriented Architecture.

• Services are assembled to form a composite application that creates a solution that addresses a specific business requirements.

• Composite applications may contain new services and business functions from existing systems and applications.

• SCA provides a model for both the composition of services and the creation of service components, including reuse of existing application functions.

The Service Component Architecture (SCA) specification provides a programming model for building applications and systems based on a SOA approach. SCA is based on the concept that a business function is provided as a series of services. These composite applications may contain new services (specifically for the application) and business functions from existing systems and applications (reused in the composite application). SCA provides a model for both the composition of services and the creation of service components, including reuse of existing application functions.

When assembled together into a composite application, they are managed, maintained, and deployed together. This streamlines and simplifies management of cooperating service components compared to earlier technologies that managed SOA applications as a set of individual services. Because its functionality can be exposed as a service through service entry points, the SOA composite application is itself a coarse-grained service.

SCA is a collection of specifications.

Assembly model specifications define a standard set of XML elements that are used to define the structure and configuration of an SCA compositeapplication.

Client & implementation (C&I) specifications define an implementation language, such as:

• BPEL:The WS-BPEL Client and Implementation (BPEL C&I) model specifies how WS-BPEL processes can be used as SCA components.

• Java, C++, PHP:This specifies language-specific APIs and annotations, which enable the creation of service components and service clients that are built in these languages.

Services are business functions that form the foundation for using a SOA approach to building applications. SOA applications aggregate functionality of related services to automate a business process. In order to reuse services (a fundamental goal of SOA), service functionality must be described by using standard interface and message structures.

SOA-based approaches have, naturally, embraced many of the message standards illustrated in the graphic in the slide, including XML, XSD, and SOAP. These document structures are easily exchanged by using standard Internet protocols such as HTTP. This results in easier interoperability across intranet and Internet networks. Discovery and description standards such as WSDL and UDDI contribute to the reusability of services and help achieve independence of hardware, operating systems, and implementation languages.

As their names suggest, the WS-Security and WS-Reliable Messaging standards describe standards for secure and reliable message delivery among service-based applications.

BPEL provides XML grammar for describing a business process as a series of activities.

The Service Component Architecture (SCA) and Service Data Objects (SDO) specifications are works in progress, guided by the OASIS organization. This work may lead to a new collection of standards with a SOA-enabled approach in mind.

Benefits of SOA:

1. Reusability: Existing functionality within an application is reused across business organization and processes.

2. Interoperability: communication between services is not dependent on platform. Services are loosely coupled to application.

3. Scalability: Applications are flexible to changing business requirements.

4. Cost efficiency: cost are reduced and delivery of new functionality is accelerated because existing resources are reused and integration of business resources is standards based.

This tutorial deals with Fusion Payroll, and how it functions.

The topics covered in this tutorial are Accounts and Bank Setup, under which the following items are discussed:

• Accounting Calendars and Primary Ledger

• Banks and Bank Accounts

• Creating an Accounting Calendar

• Creating a Primary Ledger

• Creating a Bank

• Creating a Bank Account

Accounts and Bank Setup

Accounting Calendars and Primary Ledger

These are financial concepts. Fusion utilises a central module for this, which contains the details of the bank (branches, accounts, etc.). To create any bank account, this information is required.

First, an Accounting Calendar is created. These are not related to Payroll Periods. The task for creating an accounting calendar is Manage Accounting Calendars. Then, you have to specify the total number, frequency, and duration of the account periods to create the accounting calendar. If Oracle Financials are not used, any option on the calendar can be selected. There will be no impact on the other areas of the application.

Then, a Primary Ledger is created. The task to create one is Create Primary Ledger. Once a primary ledger is created, the Primary Ledger Scope has to be provided by the user. After this, a legal entity has to be assigned. This is where you can have a link between the ledger and a legal entity.

Banks and Bank Accounts

Once the accounting calendar and primary ledger are generated, the banks and accounts can be created. This can be done by using the task Manage Banks and Branch Details. To create bank accounts, the Create Bank Accounts task is used.

Here, the internal bank account details for your company can be defined. These are bank accounts that are debited when payments are made to the workers or third parties on behalf of your company. When creating a bank account, ensure that you select the Payroll checkbox. This will make sure that that particular bank account is associated with the payroll process in your company.

While creating an organisation payment method for electronic payments, such as NACHA and BACS, you can attach one or more of your company’s bank account(s).

Creating an Accounting Calendar

The following steps are to be followed to create your accounting calendar:

1. Go to the Manage Accounting Calendars task under Define Chart of Accounts for Enterprise Structures.

2. Click on the Create New Accounting Calendars icon (circled in the screenshot below) in the following screen.

3. Enter the details of the Accounting Calendar (Name, Description, Start Date, Period Frequency, etc) and click on the Next button.

4. The Period Details of the Accounting Calendar will be shown. Click on the Save and Close button.

Fig. 1 - Choosing the Manage Accounting Calendars task

Fig. 2 - The Create New Accounting Calendar icon is circled

Fig. 3 - Entering details for the Accounting Calendar

Fig. 4 - Period Details of the calendar

Creating a Primary Ledger

The next step is to create a Primary Ledger. Follow the steps below to do so:

Go to the Manage Primary Ledgers task under Define Accounting Configurations for Human Capital Management.

1. Click on the Create New Primary Ledger icon (pictured in the screenshot below).

2. Enter the details of the ledger in the screen that follows (Name, Description, Chart of Accounts, Accounting Calendars, etc.). Choose the Accounting Calendar that you created in the previous step and click on the Save and Edit Task List button.

To add a scope to the Primary Ledger, perform the following steps:

Click on the Select… link next to the Assign Legal Entities task.

1. Choose the Select and Add option.

2. Search for your Primary Ledger and select the relevant ledger. Click on the Save and Close button.

3. In the screen that follows, click on the Add Legal Entity icon (pictured in the screenshot below).

4. Search for the legal entity and select the required Legal Entity. Click on the Apply button first, and then the Done button.

5. The Legal Entity will be assigned and will be shown in the screen that follows. Click on the Save and Close button.

6. You will now be able to see the legal entity that you selected under the Selected Scope column of the tasks.

Fig. 5 - Creating a Primary Ledger

Fig. 6 - Create New Primary Ledger icon

Fig. 7 - Entering details of the Ledger

Fig. 8 - Selecting the scope of Legal Entities

Fig. 9 - Selecting and adding the Primary Ledger

Fig. 10 - Add Legal Entity icon

Fig. 11 - Selecting and adding the Legal Entity

Fig. 12 - The selected Legal Entity is shown

Fig. 13 - The assigned Legal Entity is shown under Selected Scope

Creating a Bank

To add a bank and its branch(es), you will first have to add the task associated with it, using the following steps:

1. Click on the Add Task icon above the list of tasks (pictured in the screenshot below).

2. Search for “Manage Bank” and select the Manage Bank Accounts and Manage Bank Branches tasks under the results. Click on the Done button.

3. Go to the Manage Banks task, then click on the Create Bank icon (highlighted in the screenshot below).

4. Enter the bank details and click on the Save and Close button.

5. Then, click on the Create Branch button under the Manage Banks task.

6. Enter the details of the branch and click on the Save and Close button.

7. Click on the Done button. Your bank and its branch have now been created.

Fig. 14 - Adding a task

Fig. 15 - Adding the Manage Bank Accounts and Manage Bank Branches tasks

Fig. 16 - Creating a new bank

Fig. 17 - Entering bank details

Fig. 18 - Entering branch details

Creating a Bank Account

To add a bank account, use the following steps:

Go to the Manage Bank Accounts task and click on the Create Bank Account icon (circled in the screenshot below).

1. Enter the details of the bank account. To add the legal entity, click on Search… to search and add an entity.

2. After entering the details, click on the Save and Close button.

3. The bank account will be created. Click on the Done button.

Fig. 19 - Manage Bank Accounts screen. The Create Bank Account icon is circled

Fig. 20 - Entering the bank account details. Use the “Search..” link to search and add the legal entity

This tutorial deals with Fusion Payroll, and how it functions. This first part deals with the theory aspects of the following topics.

 The topics covered in this tutorial are

• Payroll Product Usage

• Payroll Legislations

• Payroll Lookups and Value Sets

• Payroll Flexfields

• Payroll Profile Options

Payroll Product Usage

The Payroll Product Usage ensures that certain payroll-related features, such as element templates, work correctly in your implementation. It specifies how a certain payroll task or data is to be used for a particular legislation.

The task associated with this is Manage Payroll Product Usage. By default, it is blank or has no value. Other values of Payroll Product Usage are Payroll Interface and Payroll.

For the value Payroll, the following points are concerned:

• During Element Creation, element templates generate formulae and other associated items that are required for costing or payment processing in Global Payroll.

• New-Hire process includes country-specific features, such as automatic generation of calculation cards for statutory deductions and validation of address formats.

• Payroll definitions require associated organisation payment methods. You must select payment methods that include a payment source.

• Defining payment sources requires source banks in Oracle Fusion Financials.

For Payroll Interface, the following are in effect:

• Element Creation - Element templates for Regular and Supplemental Earnings generate formulae, input values, and balances.

• New-Hire process - includes country-specific features, such as validations.

• Validation on Payroll Objects are less restrictive.

In case of no value (other HCM products), Payroll Product Usage has the following in effect:

• Element Creation - Element templates create only Elements. No formulae or input values are generated.

• New-Hire process - includes country-specific features, such as validations.

• Validation on Payroll Objects are less restrictive.

Payroll Legislations

Payroll Legislations configure legislations for Global Payroll which are not preinstalled. It chooses critical definitions for Element Classifications, Payment Types, Dimensions, etc. In other words, it defines the components that need to be enabled for the particular legislation and country.

This is specifically used for International Payroll, where definitions are not supported, and you want to utilise the product. This will help you specify the required information to proceed with the creation of elements. To do this, a classification for the particular country is required.

The task associated with this is Configure Payroll Legislations. It can be configured through a wizard.

Payroll Lookups and Value Sets

Lookups

They are static lists used for business logic. They can be created by the system (seeded), the user, or can also be extensible. There are legislation-specific lookups. To specify a reason for the entry of a particular element, in Global Payroll, the lookup is PAY_ELE_ENTRY_REASON.

In Fusion Applications, you can define lookups using the task associated with it, Manage Payroll Lookups.

Value Sets

They are dynamic lists that contain data retrieved through a query. They can either be seeded or created by the user.

In Fusion Applications, you can manage value sets using the task associated with it, Manage Payroll Value Sets.

Flexfields

In Fusion Payroll, as of now, the amount of flexfields are limited. The following list encompasses the flexfields included in Payroll:

• Balances

• Elements

• Element Links

• Element Entries

• Organisation Payment Methods

• Personal Payment Methods

• Report Records

• Time Periods

Profiles

Profiles

Profiles are permanent user preferences and system configuration options with a centralised management. Profiles are provided by a product to specify the values depending upon which the behaviour of the product’s functionalities can be changed.

The levels of profiles are: Site, Product, and User.

The task associated with it is Manage Profiles.

Payroll Profiles

They specify the values that you want to display for each level of the payroll employment hierarchy.

The three values at each level help to identify the record.

The task associated with it is Manage Payroll Profiles.

Depending on the employment model used in your enterprise, you can use the following levels to set up your payroll employment hierarchy:

• Payroll Relationship

• Employment Terms

• Assignments

To define profile option settings and values, select the Manage Payroll Employment Hierarchy Profile Option Values task in the Setup and Maintenance work area.

Payroll Relationship Level

(PAY_EMP_HIERARCHY_REL_DESC_1, PAY_EMP_HIERARCHY_REL_DESC_2, PAY_EMP_HIERARCHY_REL_DESC_3)

It identifies the Payroll, Relationship, Number, Payroll Statutory Unit Name, and the Payroll Relationship Type.

Payroll Term Level

(PAY_EMP_HIERARCHY_TERM_DESC_1, PAY_EMP_HIERARCHY_TERM_DESC_2, PAY_EMP_HIERARCHY_TERM_DESC_3)

It identifies the Legal Employer Name, Grade Name, Job Name, Position Name, Payroll Name, and Location Name.

Payroll Assignment Level

(PAY_EMP_HIERARCHY_ASG_DESC_1, PAY_EMP_HIERARCHY_ASG_DESC_2, PAY_EMP_HIERARCHY_ASG_DESC_3)

It identifies the Assignment Name, Assignment Number, Employment Category, Grade Name, Job Name, Legal Employer Name, Location Name, and Position Name.

-----The second part shall deal with the UIs associated with the above topics, along with walkthroughs and screenshots.-----

This tutorial deals with Fusion Payroll, and how it functions.

Having dealt with First part, this second part deals with the UIs and walkthroughs of the following topics.

The topics covered in this tutorial are

• Payroll Product Usage

• Payroll Legislations

• Payroll Lookups and Value Sets

• Payroll Flexfields

• Payroll Profile Options

Payroll Product Usage

To configure Payroll Product Usage, follow the below steps:

1. Go to the Manage Payroll Product Usage task.

2. The screen will show a list of countries with their legislation codes, along with the Payroll Products available for each. Use the dropdown menu to the right to select Payroll Products for that particular country. Click on the Save button. Note that only available products can be selected.

3. An error message will pop up if the selected product is not available for that particular country.

4. Click on the Done button after selecting the required (valid) Payroll Products.

Fig. 1 - The Manage Payroll Product Usage task

Fig. 2 - Selecting a Payroll Product

Fig. 3 - Error message for an unavailable product selected

Payroll Legislations

To configure Payroll Legislations, follow the below steps:

1. Go to the Configure Payroll Legislations task.

2. A list of legislations is shown on the Configure Payroll Legislations screen. Seeded legislations cannot be edited, and are denoted by lock symbols.

3. Click on the Create Legislation icon (circled in the screenshot below).

4. Select a country from the dropdown list that follows. Click on the Continue button.

5. Specify the details of the legislative rules and click on the Next button.

6. Select the required Element Classifications and click on the Next button.

7. Select the Payment Types and click on the Next button.

8. Select the Component Groups, which are mainly used for deduction when there aren’t any complex calculations involved. Click on the Next button.

9. Choose the required Balance Dimensions and click on the Next button.

10. After reviewing the details, click on the Submit button.

Fig. 4 - The Configure Payroll Legislations task

Fig. 5 - The Configure Payroll Legislations screen. Seeded legislations are denoted by the lock icon

Fig. 6 - Select Legislation dropdown list

Fig. 7 - Selecting Legislative Rules

Fig. 8 - Selecting Element Classifications

Fig. 9 - Selecting Payment Types

Fig. 10 - Selecting Component Groups

Fig. 11 - Selecting Balance Dimensions

Fig. 12 - Reviewing and Submitting the legislation details

Fig. 13 - Confirmation message. Note that the legislation has to be set in the Manage Payroll Product Usage task

Payroll Lookups

To configure Payroll Lookups, follow the below steps:

1. Go to the Manage Payroll Lookups task under Define Payroll..

2. The screen that follows will display all the payroll lookups associated currently.

3. For each lookup, the following fields are present: Lookup Type, Meaning, Description, Module, and User. You can edit the meaning and description fields for adding any explanation to the lookups.

4. Click on the Save and Close button.

Fig. 14 - The Manage Payroll Lookups task

Fig. 15 - Payroll Lookups

Payroll Value Sets

To configure Payroll Value Sets, the following steps are to be followed:

1. Go to the Manage Payroll Value Sets task under Define Payroll.

2. The screen that follows will display all of the value sets that are currently in place.

3. After adding any particular value sets (if required), click on the Save and Close button.

Fig. 16 - The Manage Payroll Value Sets task

Fig. 17 - Managing value sets

Payroll Flexfields

To configure Descriptive Flexfields in Payroll, follow the below steps:

1. Go to the Manage Descriptive Flexfields for Payroll task under Define Payroll.

2. The screen that follows will display a list of the descriptive flexfields that are available for Payroll. Click on a particular flexfield’s name to modify it.

3. On the flexfield’s screen, click on the Edit icon (circled in the screenshot below) to edit the flexfield details.

4. Aftering editing the details, click on the Save and Close button.

Fig. 18 - The Manage Descriptive Flexfields for Payroll task

Fig. 19 - A list of the flexfields available for Payroll

Fig. 20 - Managing a particular flexfield (Edit icon is circled)

Fig. 21 - Editing a flexfield

Payroll Profile Options

To configure Profile Options in Payroll, follow the below steps:

1. Go to the Manage Payroll Employment Hierarchy Profile Option Values under Define Payroll.

2. From the list of profile options displayed on the next screen, click on the profile option that has to be managed.

3. To add a new profile value, click on the Add icon (circled in the screenshot below).

4. Choose the desired options from the dropdown boxes available for the Profile Level and Profile Value fields. Select the User Name field by searching and selecting the relevant user. After selecting the options, click on the Save and Close button.

Fig. 22 - The task for managing profile options

Fig. 23 - Payroll Employment Hierarchy Profile Options

Fig. 24 - Adding a new profile value (Add icon is circled)

Fig. 25 - Searching and adding a user to the profile value

This tutorial deals with Fusion Payroll, and how it functions. In this part, we will discuss about payroll frequencies and the components associated with it.

Payroll Frequencies

Consolidation Groups

Groups can be created for different payroll processes. For example, if two separate payroll processes exist, consolidation groups are created to bring them under one group, to consolidate their results for the payroll payment process.

They can process the results from more than one payroll run in a single action, or process the results for one payroll in separate actions.

They produce one set of results per payment method for several payrolls, one set of reports, and one set of costing results. They are made during Post-Run Processing, Separate Costing, and Payment.

The task associated with it is Manage Consolidation Groups.

Go to the Manage Consolidation Groups task under Define Pay Frequency.

1. Click on the Add icon in the screen that follows (circled in the screenshot below).

2. Choose the relevant options from the dropdowns that appear. Then click on the Save button, followed by the Done button.

Fig. 1 - The Manage Consolidation Groups task

Fig. 2 - Adding a new consolidation group. The Add icon is circled.

Payroll Definitions

Here, the payroll’s details are defined. It is essential for your payroll’s implementation. Aspects like the payroll cycle (whether weekly, bi-weekly, monthly, etc.) and schedule are defined. It indicates the payment frequency and processing schedule.

It contains the following definitions:

• Frequency - monthly, weekly, bi-weekly, etc.

• Calendar - payroll schedule.

• Offsets and Dates - when to calculate and cost payments.

Upon creation of the payroll definition, the application generates the complete payroll schedule based on the payroll period type, any offsets or calendar adjustments, and the number of years that are specified in the definition.

The following attributes of payroll frequencies are included in the payroll definition:

• Effective Start Date

• First Period End Date

• Number of Years

• Offsets

  • Cutoff Date

  • Payslip Availability Date

  • Payroll Run Date

  • Date Earned

  • Date Paid

• Changes to specific dates

The task associated with it is Manage Payroll Definitions.

Go to the Manage Payroll Definitions task under Define Pay Frequency.

1. Click on the New icon (circled in the screenshot below).

2. Select the Effective As-of Date by using the Calendar icon (circled in the screenshot below) and click on the Continue button.

3. Enter the Basic Details and click on the Next button.

4. Select the number of years and choose the required option for the Payroll Offsets Fixed Dates (Yes/No). Click on the Next button.

5. The next screen will display the Time Periods for your Payroll Calendar. Click on the Next button.

6. Select the suspense and default accounts and click on the Next button.

7. Review the details of the Payroll and click on the Submit button.

8. Your Payroll Definition will show up on the task page. Click on the Update icon to update details, else click on the Done button.

Fig. 3 - The Manage Payroll Definitions task

Fig. 4 - Creating a new definition. The New icon is circled

Fig. 5 - Creating a payroll. Calendar icon is circled

Fig. 6 - Entering basic details

Fig. 7 - Payroll Offsets with the Fixed Dates option set as ‘Yes’

Fig. 8 - Payroll Offsets with the Fixed Dates option set as ‘No’

Fig. 9 - The Payroll Calendar screen

Fig. 10 - Costing of Payroll

Fig. 11 - The Payroll Review screen

Fig. 12 - The created Payroll Definition gets displayed

Roles in Payroll Definitions

This deals with the security aspect of Payroll. It assigns roles to users for payroll definitions. It involves the following two tasks:

Go to the Verify Data Role Generation for Payroll Definitions task. The Authorisation Policy Manager will open up.

1. Go to the Provision Roles to Implementation Users for Payroll Definitions task. The Oracle Identity Manager will open up.

Fig. 13 - The Verify Data Role Generation task

Fig. 14 - Home screen for the Authorisation Policy Manager

Fig. 15 - Home screen of the Oracle Identity Manager

Time Definitions

Time Definitions are static periods of unusual length based on a given static date. They can also create dates based on dynamic variables. Time definitions are used when a date or period has to be specified to be used for various modules within the payroll. (e.g., how a date is to be derived, specifying a particular date for a payroll process, etc.).

Time definitions are mainly used for payroll periods, element start and end dates, and balance dimensions.

The task associated with it is Manage Time Definitions.

Go to the Manage Time Definitions task under Define Pay Frequency.

1. Click on the New icon (circled in the screenshot below) to create a new time definition.

2. Select the definition type from the dropdown and click on the Continue button.

3. Enter the details of the time definition and click on the Submit button.

4. Click on the Done button.

Fig. 16 - The Manage Time Definitions task

Fig. 17 - Creating a new definition. The New icon is circled

Fig. 18 - Static time definition type. Choose the Retrieval Date from the dropdown

Fig. 19 - Time span definition type. Use the arrows circled to add and remove time span usages

Run Types

Run Types control the elements and payment types to process in a payroll run. What data is to be picked during payroll processing is specified under the run type.

This is done during payroll processing. If certain payment methods, elements, and element classifications are attached with a run type, the payroll processing will pick only those elements. There are two predefined run types: Regular and Supplemental.

The task associated with it is Manage Run Types.

Go to the Manage Run Types task under Define Pay Frequency.

1. After selecting the Effective As-of Date and Legislative Data Group, click on the Search button. A list of run types available will appear below. Click on the name of the relevant run type.

2. For the Regular Normal run type, click on the Add icon (circled in the screenshot below) to add a new payment method or element classification. Then click on the Done button.

Fig. 20 - The Manage Run Types task

Fig. 21 - The Manage Run Types task screen

Fig. 22 - The screen of the Regular Normal run type

Fig. 23 - Adding an element classification to the Regular Normal run type

Introduction

Logical Table source (LTS) is one of the important and new feature introduced in OBIEE 11g which provides the way to dynamically select the LTS for a particular dimension or fact based on the user.

This chapter comprises following topics:

1. Managing LTS

2. Import Additional Tables

3. Identify Extra Columns

4. Add Column and Bridge LTS

5. Map Column

6. Define Keys and Joins

7. Rename Columns and add to Presentation Layer

8. Add a new LTS

9. Add Calculations to fact

Managing Logical Table Source (LTS)

The LTS is nothing but reference to the physical table.  In the BMM layer, you will have logical table and logical fact table. A logical table have multiple LTS and each logical table have one or many physical tables.

• Describe normalized and de-normalized table structures in database designs

• Add multiple sources to a LTS for a dimension in the business model

• Add a second LTS to a dimension in the business model

Business Challenge

Data may spread across several physical tables and needs to be mapped to a single logical table.

Fig 1

Solution

1. Add multiple sources to LTS if the data in not duplicated across tables

2. Add new LTS if data is not duplicated and snowflake schema is used

Fig 2:

1.1. Import Additional tables

Import Additional product tables that store product code, product type, pricing, and supplier information.

Writers such as Ralph Kimball sometimes call this structure “snowflaking a dimension”.

Fig 3:

The physical diagram after snowflaking is shown below:

Fig 4:

1.2. Identify extra columns

The extra columns are identified and brought into the BMM layer.

Fig 4:

1.3. Add column and bridge LTS

Fig 5:

1.4. Map Column

The logical column can be mapped to two tables as described below:

Fig 6:

Drag and Drop Method

Sometimes the columns cannot be mapped automatically and so drag and drop method is used.

Fig 7:

After mapping the columns manually by drag and drop method, the results are shown below

Fig 8:

1.5. Define keys and joins

Fig 9:

1.6. Rename Logical Columns and add to Presentation Layer

You have to rename the columns in BMM layer since renaming columns in presentation layer will result in error. OBIEE do not create aliases automatically for presentation columns. We need to create aliases manually.

After renaming the Logical Columns, aliases will be created which are references to old names. You can check the aliases in Column Name->alias in presentation layer.

Fig 10:

1.7. Add a new LTS

• In the BMM layer, expand SupplierSales -> Dim-Product -> Sources. Note that the Dim-Product has LTS named Dim D1_PRODUCTS.

• Double-Click Dim D1_PRODUCTS to open the Logical Table Source dialog box

• Click the Column Mapping tab and note that all logical columns map to the physical columns in the same physical table.

• Click ok to close the Logical Table Source dialog box.

• Drag Dim_D1_Product_Type to the Dim-Product logical table in the BMM layer. Note that this creates a LTS named Type for the Dim-Product logical table.

Fig 11:

Define content of LTS

There are new two Logical table sources for the Dim-Product logical table:Dim_D1_Products and Type. The Type Code logical column is mapped in both logical table sources and therefore maps to both Dim_D1_PRODUCT_TYPE and the Dim_D1_PRODUCTS tables

Now you need to specify the aggregation content for the logical table sources. To use source correctly, Oracle BI Server has to know what each source contains in terms of the business model.

Fig 12:

8. Adding Calculations to Fact

• Calculation measures can be created based on logical columns and physical columns.

• Calculation measures can also be created by using the Calculation Wizard.

• Create Calculations using existing Logical columns

• Right-click the fact table and select new Object->Logical Column

Fig 13:

Create Calculations using Existing physical columns

Use the Column Mapping tab of the Logical Table Source dialog box to open the Expression builder for the new column.

Fig 14:

Build the calculation formula by using physical columns.

Using Calculation Wizard

1. Open the calculation wizard

2. Choose the columns for comparison and select the calculations.

3. Confirm the calculation measures and new calculation measures are automatically added.

4. Right click the logical column to be included in the calculation and then select calculation wizard.

Fig 15:

Fig 16:

New calculation measures are automatically added to the business model.

Fig 17:

Examining a query using physical columns

Use physical columns for calculations that require an aggregation rule to be applied after the calculation.

Fig 18:

The differentiation of when a physical column or logical column used in the calculation is shown below:

Table 1

Fig 19:

Examining a query using physical columns

Use physical columns for calculations that require an aggregation rule to be applied after the calculation

Fig 20:

Examining a query using logical columns

Use logical columns for calculation formulas that require an aggregation rule that is applied before the calculation.

A Query uses the Dollars per Units Measured calculation measure, was built using existing logical columns in the formula.

In this example, the SQL applies the SUM aggregation rule to Units Ordered (UNITORDD) and Dollars (DOLLARS) first and then calculates the division.

Fig 21:

Examining a query using calculation wizard

When you use the calculation wizard to model the calculation measures, it is important to note that the wizard uses logical columns as objects in the calculation formulation. Therefore, an aggregation rule is applied before the calculation.

Fig 22:

Create Rank Measure

Use the Provided functions to build expressions in the expression builder.

Fig 23:

Introduction

This chapter illustrates how to use the Oracle BI Administration tool to nest the folders in the presentation layer of the Oracle BI Repository. After finishing the building of an initial business model, the repository is tested and validated by running Oracle BI analysis and verifying the results generated by Oracle BI Server.

This chapter covers the following topics:

1. Nesting Presentation Tables

2. Testing and Validating RPD

3. Publishing the Repository

4. Validating UI with RPD

Nesting Presentation Tables

The Presentation Tables can be nested by following the steps below:

1. Use the Administrator Tool to update Presentation layer metadata to give the appearance of nested folders in UI.

2. Select a presentation table which is to be set as parent folder.

3. Open the Properties dialog box for the presentation table that corresponds to the folder that you want to nest.

4. Use Child Presentation Tables tab to define child presentation tables.

5. Add → to the beginning of the Description field and then place the table after the presentation table in which it nests.

6. Alternatively, you can prefix the name of the presentation table to be nested with a hypen and a space and then place the table after the presentation table in which it nests.

7. The Upgrade Presentation Foldering utility to convert your metadata to the new structure.

Testing and Validating RPD

It involves several steps that check whether a repository is constructed correctly and whether it yields the expected results when queries are executed in Oracle Business Intelligence (BI) end-user applications.

At a high-level, the steps include:

1. Checking the repository for consistency

2. Enabling logging

3. Loading a Repository

4. Checking analysis results

5. Checking query results by inspecting the query log

1. Consistency Check

When you create RPD, the OBIEE server does not accept the rpd until it is error free. It is very important to perform consistency check on the rpd. You can do consistency check on various bases at an individual object or the entire rpd.

Checking a repository for consistency at high-level

Navigate to File->Global Consistency Check or use ctrl+k shortcut. This will open the Consistency Check Manager that checks for entire RPD.

Fig 1

When you do the consistency check,

The following points are checked during the consistency check:

• All logical columns are mapped directly or indirectly to one or more physical columns.

• All logical dimension tables have a logical key.

• All logical tables have a logical join relationship to another logical table.

• There are at least two logical tables in the business model: a logical fact table and a logical dimension table.

• Both can map to the same physical table.

• There are no circular logical join relationships.

• A subject area exists for the business model.

Note:

Errors: Must be fixed to make the repository consistent

Warnings: Indicate conditions that may or may not be the error

BestPractices: Are conditions that do not indicate in consistencies

2. Enabling logging

     Logging is intended for quality assurance testing and debugging. We can enable logging      for individual users, system user, and individual request.

   Logging can be set if we are performing ad-hoc reporting which is doing reporting for a   particular time and want to see that query. Basically this is definitely not for the business users. It is really important if your query result is something unexpected and checks for the appropriate query in the query log.

   Query logging is normally disabled in production mode. If it is required, the logging can be enabled for the certain set of users, and can be controlled for each user.

How at a user level we can control logging in two ways as follows:

Initializing Log-Level Session Variable:

1. Open the online RPD. In Admin tool, select Manage->Identity. The security manager dialog appears.

2. Double-Click the user’s user ID. The user dialog box appears.

3. Set the logging level by clicking up or down arrows next to the logging level field or by manually entering the number between 0-7 in the field.

4. Any changes made in the rpd can be saved by check-in.

Fig 2

System Log Level:

We can find a default logging level in the Options->Repository tab of the repository.

This will set a default system log level which will fetch logs for all users as well as analysis.

Fig 3

3. Publishing a Repository

    Once we do the consistency check, then the repository is published as described below

• Go to the Enterprise Manager URL.

• Go to Business Intelligence, the RPD can be located in any drive.

• The BI Server can access multiple repositories.

They are located:

On 10g: BI_ORACLE_HOME/server/Repository

On 11g:  ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis\repository

You can publish the repository in two modes:

• Distributed Mode: In distributed mode, each Oracle BI Server instance loads the repository from its default local directory. Repositories uploaded through Fusion MiddleWare Control are uploaded to each default local directory.

• Shared Mode: In shared mode, each Oracle BI Server instance loads the repository from the shared network location designated as the repository publishing directory.

Repositories can be edited in either online mode or offline mode.

From the Admin Tool,

You develop repository in offline mode indicated by

You use online mode for minor updates and changes.

Online Mode:

If the server is in the same network online editing can be done. In Online mode, the administrator can edit a live repository that the server has in memory. The users can access the repository while changes are being made. Changes to the RPD are immediately made when they are checked in.

Warning: In Multi-user environment (MUD) online editing can result in conflicts, because developers potentially overwrite each other’s work.

Offline Mode:

In offline mode, the Admin can edit any repository and save the changes. The changes are applied when the BI server next starts and loads the repository into memory.

4. Validate UI with RPD

      For the first time you make the rpd online, change all the users in the system, and you      save that rpd, we can see the query log as shown below.

Fig 4

Viewing log files in Fusion MiddleWare Screen (FMW)

Enter http://localhost:7001/em in a browser to open FMW screen and sign in as your administrative user.

Click the Log Messages sub tab. The query log will be opened as shown below:

Fig 5

Oracle BI Logical SQL

The example for a simple SQL Query is shown below

Fig 6

There are types of SQL: physical SQL and logical SQL. The logical SQL is the SQL that understand BI Server. The physical SQL is the SQL that send the BI Server request to the data sources to retrieve the data.

Queries specific to OBIEE

Can we connect directly to the database without any of the three layers?

The Direct Database Request (DDR) allows you to perform SQL statement directly on database. However the rpd cannot be skipped even though the request does not go to subject area and the BMM layer. This can be achieved by creating connection pool using EDS. Users with permissions can create and issue DDR directly to physical end database.

Can we create Analysis from two subject areas?

We can create query from multiple subject areas within the same repository by using the option “Add/Remove Subject Areas”.

Can we include Fusion DFFs into RPD?

Yes we can include Fusion DFF and KFF into the rpd. If you are directly importing the OLTP table into the rpd then it is just like adding a new physical column. Once you add the column, the BMM object to which you want to add particular DFF is included.

This tutorial deals with Fusion Payroll, and how it functions. In this part, we will discuss about Earnings and Deductions.

Earnings and Deductions

The following tasks are associated with Earnings and Deductions in Payroll: Manage Element Classifications, Manage Elements, Manage Calculation Value Definitions, Manage Payroll Calculation Information, Manage Component Group Rules, Add Eligibility Rules for Predefined Elements, Manage Rate Definitions.

First, we shall look into the basic terms and components that comprise the Earnings and Deductions.

Elements

Elements are building blocks of Payroll that help determine the payment of base pay, benefits, absences, and other earnings and deductions. Apart from within Payroll (for bonuses, overtime earnings, etc.), this is also used in Compensation Benefits (on the basis of the base pay) and Absence Management (for absence payments like in the case of maternity leaves and other long leaves).

Fig. 1 - Elements for different types of earnings and deductions

Element Classifications

They are a mechanism by which you classify the Element as Earnings or Deductions and defines a default processing priority for the element in payroll runs.

There are three types of element classifications:

• Primary Classifications - They are given by the payroll and enabled at the country-specific module. They meet the legislative requirements of your country or territory, so you cannot change them.

• Secondary Classifications - They are subsets of the primary classifications. They are used to manage wage basis rules for deductions and taxes.

• Subclassifications - they are a way to feed balances depending upon some criteria.

The Costing information and Frequency Rules are the components that can be modified.

Element Creation

In Fusion Payroll, the organisation or legislation provides a set of predefined elements either for regulatory purposes or deductions. The first thing to be done is to identify these predefined elements and make them eligible to all employees.

For the creation of elements, templates are used. Primary Classification, Payroll Product Usage, and Category determine the templates that are used. Any number of elements can be created depending on your requirement.

For elements, there are certain Critical Child Entities: Input Values, Element Eligibility Records, Status Processing Rules, and Formula Result Rules. These need to be active for the earnings.

Upon element creation, Related Formulas, Related Elements, and related Balances are created based on the template used in the creation wizard.

Input Values

An element’s input values define the entry values available on each entry of that particular element. In Fusion, any number of input values can be created depending upon your requirement. In most cases, the template will create the input values for you.

The critical attributes for input values are:

• Special Purpose - the purpose of the value

• Unit of Measure - can be currency, hours, weeks, etc.

• Display Sequence - the level in which the value needs to come up

• Create a Database Item - to create a separate item for the value

• Required - whether yes/no during element entry

• Validation Formula - validation criteria

• Validation Source - the source of the validation

• Lookup Type - for the appropriate lookup to be displayed

Element Eligibility

Element eligibility determines which people are eligible for an element. To determine eligibility, you have to select a specific criteria that people must have to receive entries of that particular element.

The eligibility criteria can be selected from the following:

• All payrolls or for specific payrolls

• Payroll Statutory Unit

• Legal Employer

• Payroll relationship type

• Department in which the person works

• Location of person’s office

• Job (e.g. associate professor or secretary)

• Position

• Grade

• People group

Status Processing Rules and Formula Result Rules

These identify the formula that the payroll run uses to process the element for workers with a specified assignment status. The formulas return formula results such as the amount to be paid or a message.

These results can update the current element entry or another target element entry with a lower processing priority, which means that it is processed later in the payroll run.

There are different types of formula results:

• Direct Result - updates the entry after calculation

• Indirect Result - updates the entry of a non-recurring element

• Message - gives a message to the entry value

• Order Indirect - lowers priority within the element based on the calculation

• Stop - omits an entry from further calculation

Payroll Calculation Information

The following flowchart explains how the payroll earnings and deductions are calculated:

Fig. 2 - Payroll Calculation Information

The Payroll Component is enabled and has rules and rates defined for a particular classification. Depending upon the primary and secondary classifications, the Wage Basis Rules are seeded at the legislative level.

At the calculation level, the calculation value definitions are derived from the calculation factors, telling which values are to be utilised for the calculation.

This tutorial deals with Fusion Payroll, and how it functions. In this part, we will discuss about the following components of Organisation Structure:

Enterprise HCM Information

• Actions and Action Reasons

• Locations and Location Lookups

• Organisation Lookups

• Divisions

• Departments

Organisation Structure

Any changes to be made to the organisation structure can be done by using the tasks under Define Organisation Structures.

Enterprise HCM Information

To modify the Enterprise HCM (Human Capital Management) Information, follow the below steps:

1. Go to the Manage Enterprise HCM Information task under Define Organisation Structures.

2. In the screen that follows, the Enterprise HCM Information will be displayed, including the Enterprise Description, Organisation Information EFF : Enterprise Details, etc.

3. To edit any of the HCM information, click on the Edit button.

4. After editing is complete, click on the Done button.

Fig. 1 - The Manage Enterprise HCM Information task

Fig. 2 - The Enterprise HCM Information

Actions and Action Reasons

This deals with the workforce structure, a mechanism by which you can control what is to be done while creating a new business entity, performing a data operation, etc. To manage actions related to the organisation structure, follow the below steps:

1. Go to the Manage Actions task under Define Organisation Structures.

2. There are certain predefined action types of which you can create new actions. In the screen that follows, click on the New icon (circled in the screenshot below) to add a new action. Be sure to specify the Action Type, along with the Action Code, Action Name, and Start Date. The End Date is optional.

3. After adding or editing action(s), click on the Save button, followed by the Done button.

Action Reasons are the reasons for which the defined actions take place. This can be managed by using the Manage Action Reasons task under Define Organisation Structures.

Fig. 3 - The Manage Actions task

Fig. 4 - The Manage Actions screen. The New icon is circled

 Locations and Location Lookups

 To add a location to your organisation’s structure, the below steps are to be followed:

1. Go to the Manage Locations task under Define Organisation Structure.

2. In the screen that follows, click on the Create icon (circled in the screenshot below).

3. Fill in the details of the location. Make sure to fill the mandatory details marked with a “*”. For the Country field, use the Search… option in the dropdown to search and select the required country for your organisation.

4. After the details are filled in, click on the Save button, followed by the Submit button.

5. On the Manage Locations page, click on the Done button.

Once your required location is created, you can manage that location’s lookup by using the Manage Location Lookups task under Define Organisation Structures.

Fig. 5 - The Manage Locations task

Fig. 6 - The Manage Locations page. The Create icon is circled

Fig. 7 - Creating a new location

Fig. 8 - The Country field’s dropdown list. Use the Search option to easily find your country

Fig. 9 - Searching and selecting the required country of the organisation

Organisation Lookups

There are three types of lookups available: system-seeded, extensible, and user. The system lookups are provided by Oracle, and their codes cannot be changed. Extensible lookups are provided by Oracle, and they can be modified by the user. User lookups are created by the user.

To manage organisation lookups, the following steps are to be taken:

1. Go to the Manage Organisation Lookups task under Define Organisation Structures.

2. The different organisation lookups that are present for the organisation are displayed on the screen. You can add or remove lookup codes by using the icons provided.

3. Click on the Save and Close button.

Fig. 10 - The Manage Organisation Lookups task

Fig. 11 - The Organisation Lookups page

Divisions

To manage the divisions of your organisation, follow the below steps:

1. Go to the Manage Divisions task under Define Organisation Structures.

2. Click on the Create icon to create a new division.

3. Enter the division description details and click on the Next button.

4. After reviewing the division details, click on the Submit button.

Fig. 12 - The Manage Divisions task

Fig. 13 - The Manage Divisions page

Fig. 14 - Entering the division’s description

Fig. 15 - Reviewing the division details

Departments

To manage your organisation’s departments, follow the below steps:

1. Go to the Manage Departments task under Define Organisation Structures.

2. Click on the Create icon.

3. Enter the details of the department and click on the Next button.

4. Use the Add and Remove icons (circled in the screenshot below) to add/remove GL Cost Centre information. Click on the Next button.

5. After reviewing the department details, click on the Submit button.

Fig. 16 - The Manage Departments task

Fig. 17 - The Manage Departments page

Fig. 18 - Entering department details

Fig. 19 - Adding/Removing GL Cost Centre Information

This tutorial deals with Fusion Payroll, and how it functions. In this part, we will discuss about the following components of Organisation Structure:

• Organisation Trees

• Grades

• Jobs and Positions

• Security for Human Capital Management

• Data Security for Human Capital Management

• Users for Human Capital Management

Organisation Structure (contd.)

Any changes to be made to the organisation structure can be done by using the tasks under Define Organisation Structures.

Organisation Trees

To manage organisation trees, follow the below steps:

1. Go to the Manage Organisation Trees task under Define Organisation Structures.

2. Click on Actions->Create Tree to create a new organisation tree.

3. Specify the definition details of the tree and click on the Next button.

4. Specify the Label details and click on the Next button.

5. Specify the Access Rule details and click on the Submit button.

Fig. 1 - The Manage Organisation Trees task

Fig. 2 - The Create Tree option

Fig. 3 - Entering definition details

To create a tree version, follow the below steps:

1. On the Manage Organisation Trees page, click on Actions->Create Tree Version.

2. Enter the name of the organisation and the Effective Start Date and click on the Next button.

3. Click on the Add icon (circled in the screenshot below) to add a node. Click on Search to search for a node. After selecting the required node, click on the small double-arrow (circled in the screenshot), then click on the Add Tree Node button.

4. After adding the node(s), click on the Submit button.

Upon creation of the tree and tree version, you can click on that tree on the Manage Organisation Trees page. When you click the Next button, you can view the nodes attached to the tree by clicking on the arrows on the left to expand the nodes.

Fig. 4 - Specifying labels. Since this is seeded, it is not editable

Fig. 5 - Creating a tree version

Fig. 6 - Entering definition of tree version

Fig. 7 - Adding a node

Fig. 8 - The nodes after creation of the tree

After the tree is created, its status needs to be set to Active. To do this, click on Actions->Set Status->Active. A set of validations will take place to validate the tree, after which you can click on the Done button.

Fig. 9 - Setting the tree as active

Fig. 10 - Validation of tree before being set to active

Grades

To manage the grades, follow the below steps:

1. Go to the Manage Grades task under DefineGrades.

2. On the screen that follows, click on the Create icon (circled in the screenshot below).

3. Enter the grade details and click on the Next button.

4. Use the Add Row button to add Grade Steps and click on the Next button.

5. In the next step, Grade Rates are to be added. To add an existing rate, click on the Add Existing Rate button. To create a new rate, click on the Create New Rate button. After entering the details of the rate, click on the OK button.

6. Enter the Minimum, Maximum, and Midpoint values and click on the Next button.

7. Review the details of the grade and click on the Submit button.

8. On the Manage Grades page, click on the Done button.

Fig. 11 - The Manage Grades task

Fig. 12 - The Manage Grades page. The Create icon is circled

Fig. 13 - Entering the grade details

Fig. 14 - Adding Grade Steps

Fig, 15 - Creating a new grade rate

Fig. 16 - After adding a grade rate

Fig. 17 - Reviewing grade details

Jobs and Positions

To manage jobs and positions, go to the Manage Job and Manage Positions tasks under Define Jobs and Positions. This deals with the employees’ jobs and their positions within the organisation.

Fig. 18 - The Manage Job and Manage Positions tasks

Security for Human Capital Management

To define the security for Human Capital Management, go to Define Security for Human Capital Management. There are three tasks associated with it: Revoke Data Role from Implementation Users, Manage Job Roles, and Manage Duties.

1. Go to the Manage Job Roles task under Define Security for Human Capital Management.

2. The Identity Manager Self Service window will open. Here, you can define the job roles for Human Capital Management.

Fig. 19 - The Manage Job Roles task

Fig. 20 - The Identity Manager Self Service window

Data Roles can be revoked from implementation users by using the Revoke Data Role from Implementation Users task, while the duties can be defined by using the Manage Duties task.

Data Security for Human Capital Management

There are different security profiles for different data roles. One of these profiles is discussed below:

1. Go to the Manage Legislative Data Group Security Profile task under Define Data Security for Human Capital Management.

2. Search for a Legislative Data Group Security Profile and click on the Search button. From the search results, click on the name of the required profile. Click on the Edit button to edit the security profile.

3. To create a new security profile, click on the New icon (circled in the screenshot below) on the Manage Legislative Data Group Security Profile page.

Fig. 21 - The Manage Legislative Data Group Security Profile task

Fig. 22 - Searching for profiles. New icon is circled

Fig. 23 - Viewing a security profile

Users for Human Capital Management

To manage users, follow the below steps:

1. Go to the Manage Users task under Define Users for Human Capital Management.

2. Use the search bar to search for users.

3. Note that an access privilege has to be granted to your user to be able to search all users.

Fig. 24 - The Manage Users task

Fig. 25 - Searching for users

Fig. 26 - No results due to access privilege not being present

This tutorial deals with Fusion Payroll, and how it functions. In this part, we will discuss about Balances, Balance Exceptions, and Balance Exception Reports.

Balances

A balance is a value that is accumulated over a period of time. The end result of a balance would be a value - be it money, hours, or any other numerical value. There are two main aspects to a balance: the period of time over which it is to be accumulated or calculated; and the input (feed) for the calculation of the balance.

The task associated with it is Manage Balance Definitions.

A balance can be predefined, created by Element Templates, or can be user-created:

• Predefined: There are some predefined balances provided by Oracle in Payroll, like the Net Pay. It would give the net amount of pay that the employee would get at the end of the month.

• Other: Other balances are mostly created by the Element Templates during element creation. These are generated along with formulas when elements are created.

• User-created: In case any more balances (other than those described above) are required, the user can create their own balances separately. But this is rarely done, as the above two types of balances are usually enough to perform the Payroll functions.

 The critical aspects of a balance are:

• Balance Categories - how the balance is categorised and utilised for calculation, e.g., earnings, deductions, etc.

• Unit of Measure - how the value of balance is measured, e.g., money (currency), time (hours, days, weeks, etc.), or any other numerical unit.

• Generated Balances - those balances that are generated by element templates

• Database Items - a code by which you can access a value from the database

• Remuneration - the value of the balance

 There are two components for a balance: Dimensions and Defined Balances (the time period of calculation or accumulation of the balance), and Feeds (the inputs required for the calculation of the balance).

Predefined Balances

Each legislation comes with predefined balances provided by the Global Payroll. Predefined balances mostly contain information about the earnings and deductions.

The Dimensions, Defined Balances, and Feeds would already be seeded for these balances. As they are system-defined, they cannot be edited. However, they can be removed from a Balance if required.

 The following are the predefined balances provided, classified based on their category:

 Earnings

• • Standard Earnings

  • Supplemental Earnings

• Deductions

  • Pre-Statutory Deductions

  • Social Insurance Deductions

  • Tax Deductions

  • Involuntary Deductions

  • Voluntary Deductions

  • Total Deductions

• Gross and Net

  • Gross Earning

  • Gross Pay

  • Net

  • Net Pay

Dimensions and Defined Balances

They are the definition of how to retrieve specific values for the accumulation of the balance. Dimensions are predefined by Global Payroll. They can be utilised by the legislations to create Defined Balances for specific balances.

A balance’s Dimensions and Defined Balances contain the following components:

• Time: e.g., Period to date, Fiscal Year to date, Core Assignment Tax Unit Year to date, Term to date, etc.

• Employment Level: e.g., Relationship, Term, Assignment

• Context: (for few) e.g., TRU, Element, Payroll

Feeds

Feeds are the definition of what data values are to be used for the accumulation of the balance. Feeds can be defined by Element Input Values (as definition) and by Run Result Values (during the Payroll run). The unit of measure of the Input Value and the Balance should be the same.

There are two types of Balance Feeds:

• Balance Feeds by Element: It indicates one or more Element Input Value(s) to add or subtract from a balance.

• Balance Feeds by Classification: It attaches a Primary or Secondary Element Classification or Subclassification and uses the input value that has the special purpose of a primary output value.

Balance Exceptions and Reports

Balance Exceptions are a mechanism to find deviations in calculations through Dimensions. You can define the criteria to be used in Balance Exception Reports to identify overpayments, underpayments, and trends.

Any dimension can be selected, based on which the deviations in the balance will be returned in the Balance Exception. For example, the deviations in the balance of Net Pay of the employees for the past three months can be found using Balance Exceptions. The task associated with it is Manage Balance Exceptions.

You can create an Exception Report Definition by using the created Balance Exception. After you have created the required Balance Exception, you can add it to a new Balance Exception Report. The task associated with it is Manage Balance Exceptions and Reports.

Once the Balance Exception Report is created, the report has to be run to get the results of the Balance Exception. To run the Balance Exception process and view the Balance Exception Report, the report associated with it is Run Balance Exception Report.