Important scheduled processes list in fusion hcm

1. Important scheduled processes list in Fusion HCM
In thispostwe will gothroughthe listof scheduledprocesses,how touse,whentouse and whatthey
will do.
Some of the processlistandtheirexplanations:
Post-ConversionProcessing:(1-5)
Afteran initial orincrementalloadof personrecords,youruna setof processestocomplete datasetup
inthe Oracle FusionHCMenvironment.Thisisdone toeithercreate indexesoradditional databasedon
the conversionyoujustdid.Please ensure youare runningthese programsafterconversionandalso
evaluate postgo-liveactivitiestosee if youshouldscheduletheseprogramstorun ona dailybasis.
1. Update Person Search Keywords
Copiesattributesof person,employment,andprofilerecordsthatare usedas searchkeywordstothe
PER_KEYWORDS table,where they're indexedtoimprove searchperformance.The processupdatesthe
entire PER_KEYWORDStable.
2. Synchronize PersonRecords
Communicateschangestopersonandassignmentrecordsthathave occurredsince the lastdata loadto
consumingapplications,suchasOracle FusionTradingCommunityModel andOracle Identity
Management(OIM).
3. Calculate RelationshipStrength
Updatesstoredrelationship-strengthinformation.Inthe PersonGallery,searchresultscanappearin
orderof the strengthof the relationshipbetweenthe personperformingthe searchandeachpersonin
the search results.The strongerthe relationship,the nearertothe topof the resultsa person's
assignmentappears.
4. RefreshManager Hierarchy
Populatesthe denormalizedmanagerhierarchytableswithlatestinformationaftereachdataload.For
performance reasons,the complete managerhierarchyforeachpersonisextractedfromlive data
tablesandstoredina separate manager-hierarchytable,knownasthe denormalizedmanagerhierarchy

2. USER AND ROLE PROVISIONING PROCESSES: (5-8)
SCHEDULING THE PROCESSES
You shouldrun one userand role provisioningprocessat a time. These processesshouldnot overlap.
Please make sure your schedule allowstime for the process to complete before youschedule another
provisioningprocess.
5. SendPendingLDAP Requests(DailyAdHoc):Bulkprocessingof userand role provisioning
requests.
SendsbulkrequeststoOIMimmediatelytocreate (andalsosuspendor re-enable) useraccounts,as
appropriate.Whenyouloadpersonrecords,the applicationautomaticallycreatesuser-account
requestsbydefaultandprovisionsrolestousersinaccordance withrole provisioningrules.
Important
Before yourunthis process, review yourdataconversionfullyandconfirmitsaccuracy.If youneedto
purge your data andrepeatthe conversion,itwill take muchlongerif you've createduseraccountsand
notifiedusersof theirsign-indetails.Youcancontrol aspectsof the
provisioningprocessforthe enterprise bysettingthe UserandRole Provisioningoptionsonthe Manage
Enterprise HCMInformationpage.Forexample,youcansuppressthe automaticcreationof user
accounts.
Thisprocesssendsto the LDAPdirectorythe requestsrelatedtouseraccountprovisioningaswell asthe
requestsforaddingandremovinguserroles.Youtypicallyuse thistoprocessthe provisioningrequests
createdby bulkprocessesaswell astoprocessfuture datedrequests.
Thisjob shouldbe scheduledatleastonce perday to handle anybulkorfuture-dateduserorrole
provisioningrequests.
Thisjob shouldalsobe runafterloadingworkersorusersinbulkusingHCM Data Loader.
6. AutoprovisionRolesfor All Users(AdHoc Rarely):Evaluates rolesmembershipforall users,
includinginactive.
Thisprocessevaluatesall usersinthe systemagainstthe role provisioningrules.Thisprocessmayhave
heavyperformance impactonyourenvironmentif yourunitregularly.Youshouldrunthisprocess
occasionally,onlywhenrole-provisioningrulesare addedorupdated.

3. Shouldbe runonlywhenrole mappingruleshave beenaddedorchanged,andthese rulesapplytothe
entire userpopulation.
Thisjob doesnotneedtobe regularlyscheduledasautomatic role provisioninghappensaspartof user
creation.
Neverexpectedtobe usedfrequentlyondailybasis.
7. SendPersonal Data for Multiple UserstoLDAP(Ad Hoc Rarely):Reconcilespersonal information
changesinOracle HCM CloudwithLDAPdirectory
ThisprocesssynchronizeschangesperformedinbulkonOracle HCMCloudpersonrecordswiththe
LDAP directoryrecords.The followingfieldsare synchronized:FirstName,LastName,Email,and
Manager. You typicallyrunthisprocessafterloadingpersondatainbulk.Youcan alsorun thisprocess
to update the managerhierarchyinthe LDAP directory.
Thisjob isonlyneededafterchangingpersonal data(name,manager,email) viaabulkprocesssuchas
HCM Data Loader imports.
Thisjob shouldbe scheduledtorunonce afterthe bulkloadiscomplete.
8. Retrieve Latest LDAP Changes (Veryrarely):UpdatesOracle HCMCloudpersonrecordswith
data comingfromLDAP directory.
Thisjob updatesthe Oracle CloudApplicationsSecuritytableswithdatacomingfromthe LDAP
directory.Youshouldrunthisprocessonce after the productupdate iscompleted.Forexample,after
youupgrade from 18C to 19A.
Neverexpectedtobe usedfrequentlyondailybasis.
9. Synchronize Bell Notifications(Every2 hours):Bell Notificationstosynchronize withthe BPM
Worklist
To move the alreadyapprovednotificationsfrombell,thereisanESS jobdefinitionwhichcanbe
scheduledtorunperiodically.Privilege NeededtoSchedule/ExecutethisJobDefinitionis:
FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV ( Thisprivilegerollsuptoall the FamilyAdminJob
Roles).
Theywill be markedasRead/movedfromPendingNotificationstoAll Notificationsimmediatelyonce
the userreads themas there are no pendingactionsonthem.

4. The Synchronize Bell Notifications shouldbe scheduled forevery2hrs. and isrestrictedby
Developmenttoupdate 500 recordsat a time.
10. Calculate SeniorityDates(Adhoc):To calculate the senioritydatesforworkersbasedonthe
seniorityrulesconfiguredinthe application
Parameters:
PersonNumber:Enterpersonnumber
SeniorityDate Code List:ORA_ESD_P,ORA_LESD_W( Thisvaluesmaybe differentbasedonthe customer
configurations--Seethe configurationsetupdatatable forthisinformation)
(ORA_ESD_P,ORA_LESD_W,ORA_POSITION_SD_A)
Exclude terminatedWorkers:Yes
Operation:CleanAndRepopulate
SetupandMaintenance > Manage CommonLookupsusingthe Lookup
Type ORA_PER_SENIORITY_ITEMS
11. Synchronize Transaction WorkflowStatus(Dailyonce andAdhoc):
Thisprocessensuresthat the workflowstatusisupdatedcorrectlyinSOA andOracle FusionApplications
12. Import User and Role ApplicationSecurity Data (DailyOnce) : To setup andmaintainthe
SecurityConsole
It copiesusers,roles,privileges,anddatasecuritypoliciesfromthe LDAPdirectory,policystore,and
ApplicationsCore GrantsschematoOracle FusionApplicationsSecuritytables.ITSecurityManager: this
role mustto run thisprocess.
13. Importing UserLogin History (DailyOnce) :Thistaskruns a processthat imports information
aboutuser accessto Oracle FusionApplicationstothe Oracle FusionApplicationsSecuritytables
Thisinformationisrequiredbythe Inactive UsersReport,whichreportsonuserswhohave been
inactive fora specifiedperiod.
14. Optimize PersonSearch Keywords(Dailyat timesof low activity):

5. Optimize PersonSearchKeywordsIndex processtoidentifythe fragmentedindexesandhelpimprove
the overall searchperformance.
The Update PersonSearchKeywordsprocessfirstandthenthe Optimize PersonSearchKeywords
process.We cannot schedule bothprocessessimultaneously.If youschedule thematthe same time,the
secondprocesswill waitforthe firstprocesstocomplete before itstarts.
15. Processand ReassignInactive UserAccounts(DailyOnce):
Processthat identifiesinactive useraccountsandremovesthemfromtheirteams.Italsosends
notificationstomembersreassignedasthe new teamleads.
16. To reflectthe Flex FieldsinOTBIthenwe needtorun the below processinsequence:
1. Create Rules XML File for BI ExtenderAutomation
2. Import Oracle FusionData ExtensionFor Transactional BusinessIntelligence
Note:Should check the BI Enabledcheck box while creatingthe segmentsand shoulddeploythe Flex
fields.
17. Generate Flexfield Database Items:(EFF / EIT only):
We shouldrunthisprocessaftercreatingthe flex fieldsanddeploysuccessfully.Thenonlythe Flex
FieldsDBI'swill available in FastFormulasandHCMExtracts.
Note:Navigator -->Payroll Checklist-->Tasks --> Submita processor Report -->search Generate
FlexfieldDatabase Items --> run this withoutselectingany LDG.
18. Run Reassign PendingApprovalsfor Terminationsand Correct InvalidSupervisorAssignments
Process(DailyOnce):
Thisprocessautomaticallyreassignsthe directline reports.All directreportsare reassignedtothe
transferringmanager'smangerasof the date followingthe transfer.
Reassignthe line reportsmanuallytothe transferringmanager'smanagerduringthe global transfer
transactionor terminated.
Hope thishelps.Staytunedformore updates.