Sometimes accessing an HCM environment causes in “Max HTTP Headers, Blocked by WAF” error as shown below:
Resolution:
This issue occurs due to browser cache issue. Clearing the cache or trying to access the environment in incognito mode or another browser should resolve the issue.
Once Jobs data is loaded/created, you can use below SQL to extract the setup data for Jobs:
Select pjft.name
,pjf.job_code
,TO_CHAR(pjf.effective_start_date,'YYYY/MM/DD') start_date
,TO_CHAR(pjf.effective_end_date,'YYYY/MM/DD') end_Date
,(select add_set.set_code
from fnd_setid_sets add_set
where add_set.set_id = pjf.set_id
and add_set.language = USERENV('LANG')) set_code
,pjf.active_status
from per_jobs_f pjf,
per_jobs_f_tl pjft
where 1=1
and pjf.job_id = pjft.job_id
and pjft.language = USERENV('LANG')
and trunc(SYSDATE) between pjft.effective_start_date and pjft.effective_end_date
and trunc(sysdate) between pjf.effective_start_date and pjf.effective_end_date
ORDER BY 2,4There are requirements when the existing legal entity name should be updated to a new name. One should note that the LE name in UI is displayed for a view – HR_ALL_ORGANIZATION_UNITS_F_VL.
Sometimes, even after updating the name in UI, correct name is not reflected on some pages like Manage Employment or Manage Legal Entity Information for HCM.
In such cases, one should verify the value in HR_ALL_ORGANIZATION_UNITS_F_VL view to make sure the updated value is showing here.
If updated value is not available in this view, please follow below steps:
This should force the name update to happen in HR_ALL_ORGANIZATION_UNITS_F_VL view.
Below query can be used to extract checklist configuration details:
select PER_CHECKLISTS_TL.NAME
,PER_CHECKLISTS_TL.DESCRIPTION checklist_desc
,PER_TASKS_IN_CHECKLIST_B.CHECKLIST_TASK_NAME tin_ctn
,PER_TASKS_IN_CHECKLIST_B.DESCRIPTION task_desc
,PER_TASKS_IN_CHECKLIST_B.TASK_ACTION_ID
,PER_TASKS_IN_CHECKLIST_B.TASK_CONFIGURATION
,PER_CHECKLIST_TASKS_B.CHECKLIST_TASK_ID
,PER_CHECKLIST_TASKS_B.TASK_LEVEL_CODE
,PER_CHECKLIST_TASKS_B.TASK_LEVEL_VALUE
,PER_CHECKLIST_TASKS_B.CHECKLIST_TASK_CODE
,PER_CHECKLIST_TASKS_B.TASK_CATEGORY
,PER_CHECKLIST_TASKS_B.ACTION_TYPE
,PER_CHECKLIST_TASKS_B.TASK_ACTION_ID ctb_action_id
,PER_CHECKLIST_TASKS_B.TASK_ACTION_CODE
,PER_CHECKLIST_TASKS_TL.CHECKLIST_TASK_NAME ctc_ctn
,PER_CHECKLIST_TASKS_TL.DESCRIPTION
,PER_CHECKLIST_TASKS_TL.ACTION_URL
,PER_CHECKLIST_TASKS_TL.USER_DISPLAY_NAME
FROM PER_CHECKLISTS_TL PER_CHECKLISTS_TL
,PER_TASKS_IN_CHECKLIST_VL PER_TASKS_IN_CHECKLIST_B
,PER_CHECKLIST_TASKS_B PER_CHECKLIST_TASKS_B
,PER_CHECKLIST_TASKS_TL PER_CHECKLIST_TASKS_TL
WHERE PER_CHECKLIST_TASKS_B.ACTION_TYPE = 'ORA_CHK_APP_TASK'
AND PER_CHECKLIST_TASKS_B.CHECKLIST_TASK_ID = PER_CHECKLIST_TASKS_TL.CHECKLIST_TASK_ID
AND PER_CHECKLIST_TASKS_TL.LANGUAGE = 'US'
AND PER_CHECKLISTS_TL.LANGUAGE = 'US'
AND PER_TASKS_IN_CHECKLIST_B.CHECKLIST_ID = PER_CHECKLISTS_TL.CHECKLIST_ID
AND PER_TASKS_IN_CHECKLIST_B.TASK_ACTION_CODE = PER_CHECKLIST_TASKS_B.TASK_ACTION_CODE
AND PER_TASKS_IN_CHECKLIST_B.ACTION_TYPE = 'ORA_CHK_APP_TASK'HDL provides an option to upload Potential life events for a person in benefits. Please note that ‘Open Enrolment’ life event can’t be loaded using the potential life events file.
Provide the data in below format and save it as PotentialLifeEvents.dat
METADATA|PotentialLifeEvents|PersonNumber|LegalEmployer|BenefitRelationName|LifeEventName|LifeEventStatusCode|LifeEventOccuredDate|UnprocessedDate|NotificationDate|DetectedStatusDate|ManualStatusDate|ManualOverrideStatusDate|ProcessedDate|VoidedStatusDate|PtnlLerForPerSrcCd|SourceSystemId|SourceSystemOwner|LerId|PtnlLerForPerId|PersonId|LegalEntityId|BenefitRelationId|LifeEventTypeCode|ProdCd
MERGE|PotentialLifeEvents|123718|XX Test|DFLT|New Hire|UNPROCD|2023/02/01|2023/02/01||||||||123718_2023/02/01|HRC_SQLLOADER|||||||