Important Schedule process List

Some of the important Schedule process List:

Post-Conversion Processing: (1-5)

After an initial or incremental load of person records, you run a set of processes to complete data setup in the Oracle Fusion HCM environment. This is done to either create indexes or additional data based on the conversion you just did. Please ensure you are running these programs after conversion and also evaluate post go-live activities to see if you should schedule these programs to run on a daily basis.

1.      Update Person Search Keywords

 

Copies attributes of person, employment, and profile records that are used as search keywords to the PER_KEYWORDS table, where they're indexed to improve search performance. The process updates the entire PER_KEYWORDS table.

2.      Synchronize Person Records

Communicates changes to person and assignment records that have occurred since the last data load to consuming applications, such as Oracle Fusion Trading Community Model and Oracle Identity Management (OIM).

3.      Calculate Relationship Strength

Updates stored relationship-strength information. In the Person Gallery, search results can appear in order of the strength of the relationship between the person performing the search and each person in the search results. The stronger the relationship, the nearer to the top of the results a person's assignment appears.

4.      Refresh Manager Hierarchy

Populates the denormalized manager hierarchy tables with latest information after each data load. For performance reasons, the complete manager hierarchy for each person is extracted from live data tables and stored in a separate manager-hierarchy table, known as the denormalized manager hierarchy

USER AND ROLE PROVISIONING PROCESSES: (5-8)

SCHEDULING THE PROCESSES

You should run one user and role provisioning process at a time. These processes should not overlap. Please make sure your schedule allows time for the process to complete before you schedule another provisioning process.

5.      Send Pending LDAP Requests (Daily Ad Hoc): Bulk processing of user and role provisioning requests.

Sends bulk requests to OIM immediately to create (and also suspend or re-enable) user accounts, as appropriate. When you load person records, the application automatically creates user-account requests by default and provisions roles to users in accordance with role provisioning rules.

Important

Before you run this process, review your data conversion fully and confirm its accuracy. If you need to purge your data and repeat the conversion, it will take much longer if you've created user accounts and notified users of their sign-in details. You can control aspects of the

provisioning process for the enterprise by setting the User and Role Provisioning options on the Manage Enterprise HCM Information page. For example, you can suppress the automatic creation of user accounts.

This process sends to the LDAP directory the requests related to user account provisioning as well as the requests for adding and removing user roles. You typically use this to process the provisioning requests created by bulk processes as well as to process future dated requests.

This job should be scheduled at least once per day to handle any bulk or future-dated user or role provisioning requests.

This job should also be run after loading workers or users in bulk using HCM Data Loader.

6.      Autoprovision Roles for All Users (Ad Hoc Rarely): Evaluates roles membership for all users, including inactive.

This process evaluates all users in the system against the role provisioning rules. This process may have heavy performance impact on your environment if you run it regularly. You should run this process occasionally, only when role-provisioning rules are added or updated.

Should be run only when role mapping rules have been added or changed, and these rules apply to the entire user population.

This job does not need to be regularly scheduled as automatic role provisioning happens as part of user creation.

Never expected to be used frequently on daily basis.

7.      Send Personal Data for Multiple Users to LDAP(Ad Hoc Rarely): Reconciles personal information changes in Oracle HCM Cloud with LDAP directory

This process synchronizes changes performed in bulk on Oracle HCM Cloud person records with the LDAP directory records. The following fields are synchronized: First Name, Last Name, Email, and Manager. You typically run this process after loading person data in bulk. You can also run this process to update the manager hierarchy in the LDAP directory.

This job is only needed after changing personal data (name, manager, email) via a bulk process such as HCM Data Loader imports.

This job should be scheduled to run once after the bulk load is complete.

8.      Retrieve Latest LDAP Changes (Very rarely): Updates Oracle HCM Cloud person records with data coming from LDAP directory.

This job updates the Oracle Cloud Applications Security tables with data coming from the LDAP directory. You should run this process once after the product update is completed. For example, after you upgrade from 18C to 19A.

Never expected to be used frequently on daily basis.

9.      Synchronize Bell Notifications (Every 2 hours): Bell Notifications to synchronize with the BPM Worklist

To move the already approved notifications from bell, there is an ESS job definition which can be scheduled to run periodically. Privilege Needed to Schedule/Execute this Job Definition is : FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV ( This privilege rolls up to all the Family Admin Job Roles).

They will be marked as Read/moved from Pending Notifications to All Notifications immediately once the user reads them as there are no pending actions on them.

The Synchronize Bell Notifications  should be scheduled  for every 2 hrs. and is restricted by Development to update  500 records at a time.

10.  Calculate Seniority Dates(Adhoc): To calculate the seniority dates for workers based on the seniority rules configured in the application

Parameters:

Person Number: Enter person number

Seniority Date Code List: ORA_ESD_P,ORA_LESD_W( This values may be different based on the customer configurations--See the configuration setup data table for this information) (ORA_ESD_P,ORA_LESD_W,ORA_POSITION_SD_A)

Exclude terminated Workers: Yes

Operation: Clean And Repopulate

Setup and Maintenance > Manage Common Lookups using the Lookup

Type ORA_PER_SENIORITY_ITEMS

11.  Synchronize Transaction Workflow Status(Daily once and Adhoc):

This process ensures that the workflow status is updated correctly in SOA and Oracle Fusion Applications

12.   Import User and Role Application Security Data (Daily Once) : To set up and maintain the Security Console

It copies users, roles, privileges, and data security policies from the LDAP directory, policy store, and Applications Core Grants schema to Oracle Fusion Applications Security tables. IT Security Manager : this role must to run this process.

13.  Importing User Login History (Daily Once) :This task runs a process that imports information about user access to Oracle Fusion Applications to the Oracle Fusion Applications Security tables

This information is required by the Inactive Users Report, which reports on users who have been inactive for a specified period.

14.  Optimize Person Search Keywords (Daily at times of low activity):

Optimize Person Search Keywords Index process to identify the fragmented indexes and help improve the overall search performance.

The Update Person Search Keywords process first and then the Optimize Person Search Keywords process. We cannot schedule both processes simultaneously. If you schedule them at the same time, the second process will wait for the first process to complete before it starts.

15.  Process and Reassign Inactive User Accounts(Daily Once):

Process that identifies inactive user accounts and removes them from their teams. It also sends notifications to members reassigned as the new team leads.

16.   To reflect the Flex Fields in OTBI then we need to run the below process in sequence:

A.      Create Rules XML File for BI Extender Automation

B.      Import Oracle Fusion Data Extension For Transactional Business Intelligence

Note: Should check the BI Enabled check box while creating the segments and should deploy the Flex fields.

17.  Generate Flexfield Database Items: (EFF / EIT only):

We should run this process after creating the flex fields and deploy successfully. Then only the Flex Fields DBI's will available in  Fast Formulas and HCM Extracts.

Note: Navigator --> Payroll Checklist --> Tasks --> Submit a process or Report --> search Generate Flexfield Database Items --> run this wi out selecting any LDG.

18.  Run Reassign Pending Approvals for Terminations and Correct Invalid Supervisor Assignments Process (Daily Once):

This process automatically reassigns the direct line reports. All direct reports are reassigned to the transferring manager's manger as of the date following the transfer.

Reassign the line reports manually to the transferring manager's manager during the global transfer transaction or terminated.

It may helpful for you. please visit blog for more information and share your ideas.Thanks,Sainath

HCM EXTRACTS OUTPUT DELIVERY FILE NAME SYSDATE TIME STAMP:

HCM Extract Output Name Date and Time Stamp can be achieve using the following formats:


%y         :Displays the sysdate year in four digits: Example: 2019
%m       :Displays the sysdate month in two digits: 01-12
%d        :Displays the sysdate date in two digits: 01-31
%H       :Displays the sysdate hour in two digits based on 24-hour day: 00-24
%M      :Displays the sysdate minute in two digits: 00 - 59
%S       :Displays the sysdate number of seconds in two digits: 00 - 59
%l         :Displays the sysdate milliseconds in three digits: 000 - 999

%edy     :Displays the effective date year in four digits: Example: 2019
%edm    :Displays the effective date month in two digits: 01-12
%edd     :Displays the effective date date in two digits: 01-31
%edH    :Displays the effective date hour in two digits based on 24-hour day: 00-24
%edM   :Displays the effective date minute in two digits: 00 - 59
%edS    :Displays the effective date number of seconds in two digits: 00 - 59

It may helpful for you. please visit blog for more information and share your ideas.Thanks,Sainath

How to get a employee images using BI report

To get a employee images using BI report:

create data model:
Using the below query:

SELECT A.PERSON_NUMBER,
B.DISPLAY_NAME,
C.IMAGE
FROM PER_ALL_PEOPLE_F A,
PER_PERSON_NAMES_F B,
PER_IMAGES C
WHERE A.PERSON_ID = B.PERSON_ID
AND B.NAME_TYPE='GLOBAL'
AND A.PERSON_ID = C.PERSON_ID
AND TRUNC(SYSDATE) BETWEEN A.EFFECTIVE_START_DATE AND A.EFFECTIVE_END_DATE
AND TRUNC(SYSDATE) BETWEEN B.EFFECTIVE_START_DATE AND B.EFFECTIVE_END_DATE
AND C.PRIMARY_FLAG='Y'
AND A.PERSON_NUMBER IN (DECODE(:pn,'',A.PERSON_NUMBER,:pn))

For parameter use list of values:

SELECT DISTINCT A.PERSON_NUMBER FROM PER_ALL_PEOPLE_F A,PER_IMAGES C where A.PERSON_ID = C.PERSON_ID AND C.IMAGE IS NOT NULL ORDER BY PERSON_NUMBER

Create rtf template:

For image filed use the below tag:
<fo:instream-foreign-object content-type="image/jpg" height="3 in" width="4 in">
<xsl:value-of select="IMAGE"/>
</fo:instream-foreign-object>

Note:Above the IMAGE in red color is the filed name.

The output looks like below:

It may helpful for you. please visit blog for more information and share your ideas.Thanks,Sainath

Calculate Accruals and Balances process batch parameters: change the max errors default value 3

How to change max errors and threads for Absence Process :

My clients --> Absences

Click Tasks

Click Configure Absence Batch Parameters

Here change the Max Error number , Total Threads number 

It may helpful for you. please visit blog for more information and share your ideas.Thanks,Sainath

Change the start date / hire date / effective start date of Worker with HDL

Change hire date of Worker using HDL :

The start date of a work relationship means the Hire Date. To change the Hire Date we need to use the NewStartDate in work relationship Metadata.

only work relationship is sufficient to change the hire date of an employee.

Worker.dat:

SET PURGE_FUTURE_CHANGES N
METADATA|WorkRelationship|SourceSystemOwner|SourceSystemId|PersonNumber|LegalEmployerName|NewStartDate
MERGE|WorkRelationship|FUSION|100000895467|1234|TEST_LE|2017/07/24


To get source system Id:


SELECT PERSON_ID FROM fusion.PER_ALL_PEOPLE_F WHERE PERSON_NUMBER ='1234'

SELECT PERIOD_OF_SERVICE_ID FROM fusion.PER_PERIODS_OF_SERVICE WHERE PERSON_ID =123456788964

SELECT SURROGATE_ID FROM fusion.HRC_INTEGRATION_KEY_MAP

WHERE SURROGATE_ID = 100000895467
  --(SURROGATE_ID =PERIOD_OF_SERVICE_ID )

Note:
Currently Oracle's Fusion Application doesn't support "changing Start Date of Work Relationship created because of global transfer". This is neither supported from HDL(HCM Data Loader) nor from Fusion User Interface.
When a Fusion user perform the global transfer, it will terminate old WorkRelationship(WR)  and create new one. NewStartDate in HDL is to change the hire date of first work relationship of a person and can not be used to change Global transfer new WR start date.

For changing the start date of the Work Relationship created because of global transfer, you have to cancel that Work Relationship and you have to perform global transfer again with correct date.

It may helpful for you. please visit blog for more information and share your ideas.

Thanks,
Sainath

SYSDATE as header in E-TEXT template

We can get the dynamic header in e-text:

Example:

If we need a SYSDATE as header and the person numbers are values for that header.

create a data model with two data sets :

1. Sysdate  : SELECT SYSDATE FROM DUAL
2. PersonNumbers : select person_number from per_all_people_f

The XML file for the above data sets will generate like below:

<?xml version = '1.0' encoding = 'utf-8'?>
<DATA_DS>
<G_1>
<SYSDATE>2019-03-04T06:20:02.000+00:00</SYSDATE>
</G_1>
<G_2>
<PERSON_NUMBER>5678</PERSON_NUMBER>
</G_2>
<G_2>
<PERSON_NUMBER>7799</PERSON_NUMBER>
</G_2>
<G_2>
<PERSON_NUMBER>7769</PERSON_NUMBER>
</G_2>
<G_2>
<PERSON_NUMBER>3557</PERSON_NUMBER>
</G_2>
<G_2>
<PERSON_NUMBER>6436</PERSON_NUMBER>
</G_2>
</DATA_DS>

create a e-text like below:

Format Setup:

<TEMPLATE TYPE>	DELIMITER_BASED
<OUTPUT CHARACTER SET>	UTF-8
<NEW RECORD CHARACTER>	Carriage Return

Format Data Records:

<LEVEL>

DATA_DS

<LEVEL>

G_1

<MAXIMUM LENGTH>	<FORMAT>	<PAD>	<DATA>	<COMMENTS>
<NEW RECORD>		Line
1000000	ALPHA		TO_CHAR(SYSDATE,’YYMMDD’)	SYSDATE

<END LEVEL>

G_1

<LEVEL>

G_2

<MAXIMUM LENGTH>	<FORMAT>	<PAD>	<DATA>	<COMMENTS>
<NEW RECORD>		Line
1000000	ALPHA		PERSON_NUMBER	PERSON_NUMBER

<END LEVEL>

G_2

<END LEVEL>

DATA_DS

 The output will come like below:

190304

5678

7799

7769

3557

6436

In the above output the header is SYSDATE and the remaining values are Person Numbers.

It may helpful for you. please visit blog for more information and share your ideas.

Thanks,
Sainath

Correct Legal Employer Name for Employees

Correct Legal Employer For Employee:

HR Administrator selects an Incorrect Legal Employer while hiring. We can correct this legal Employer:

Legal Employer can be changed by cancelling the current work relationship hiring the employee again in the correct legal employer. The existing record will be found when attempting to create a New Person with the correct Legal Employer.

Steps:

1. Hired worker in wrong LE

2. Steps to Cancel Work Relationship

      Navigator > Person Management > Search for Person

3. Select person

    Manage Work Relationship

    Actions > Cancel Work Relationship

    Navigator > New Person > Hire an Employee

4. Enter person details to include correct LE

    Select Person > Continue

    Navigator > Person Management  > Search for Person By including Termination check box >Only One record found.

It may helpful for you. please visit blog for more information and share your ideas.

Thanks,
Sainath

How to make a user Read only in Oracle cloud HCM

How to make a user Read only in Oracle cloud HCM:

We can make a user to read only in oracle cloud HCM. If that user tries to update any thing then that user gets error.

Error: You have only read-only access to all applications. You cannot perform updates. (FND-3319)

1.  Setup and Maintenance à Manage administrator profile Values
2.  Search profile Option Code: FND_READ_ONLY_MODE
3. Click add (+) and set :

             Profile level: User

             User Name: HCM_Read_Only

             Profile Value: ENABLED

To rollback this read only option set the Profile Value: Enabled

It may helpful for you. please visit blog for more information and share your ideas.

Thanks,
Sainath

Introduction to SandBox:

Sandbox:

1. Sandbox is the tool used to manage customization or edit pages. 

2. Sandbox provides an independent development environment so that we can fully test our changes before merging them with the main application and making them available to end users. 

3. Anyone who makes sandbox active can see the changes that are made in that sandbox. When a sandbox is published the changes that are made in that sandbox are visible to all users who have the permissions to view the affected pages and fields.

4. We cannot delete the active sandbox. The good thing to do is delete the sandboxes that are not required. We can create any number of sandboxes, there is no limit.

5. Role required to create sandbox: Application Implementation Admin 

It may helpful for you. please visit blog for more information and share your ideas.

Thanks,
Sainath