Oracle Fusion HCM Knowledge Hub

Element duration dates control when element entries for an employee start or end. Here are the predefined element duration dates: First standard earnings date Last standard earnings date Last standard process date Final close date Date Values This table provides information about what actions set the date values and which dates they're based on.

When you terminate an employee or end an assignment record, the Payroll Relationship page displays the corresponding dates. These dates control how earnings and deductions are processed for the terminated employment record. For example, Andy resigned from his teaching post at Royal High School, and his line manager enters a termination date of 22-July-2022. The application will process Andy's last payroll payment for 31-July-2022. You can view these termination dates on the payroll relationship page for Andy. These dates show up at all the employment levels of Andy, such as assignment, associated payroll, and payroll relationship.

Oracle HCM Cloud automatically creates a payroll relationship when you hire an employee or create other types of person records, such as candidates and pending workers. A payroll relationship is an association between a person and a payroll statutory unit (PSU). A payroll relationship represents the association between a person and a payroll statutory unit (PSU), which is the legal entity responsible for employee payment. Payroll relationships group a person's employment assignment records based on the payroll statutory calculation and reporting requirements. Payroll relationships facilitate the capture and extraction of HR and payroll-related data sent to a third party, such as a payroll provider for payroll processing. Payroll relationships aggregate balances at the payroll relationship level. Within a payroll relationship, payroll processes can aggregate balances for multiple assignment records. Balances don't span payroll relationships.

METADATA|CalculationValueDefinition|LegislativeDataGroupName|TaxRepUnitName|EffectiveStartDate|ValueDefinitionName|DirCardDefinitionName|DirCardCompDefName|Context1|CardSequence|ComponentSequence MERGE|CalculationValueDefinition|LDG_NAME|TRU_NAME|2022/01/01|SUI Employer Rate|Calculation Rules for Tax Reporting and Payroll Statutory Unit|State Unemployment|6|1|2 METADATA|EnterableCalculationValue|DirCardDefinitionName|LegislativeDataGroupName|TaxRepUnitName|DirCardCompDefName|ValueDefinitionName|EffectiveStartDate|Value1|Context1|CardSequence|ComponentSequence MERGE|EnterableCalculationValue|Calculation Rules for Tax Reporting and Payroll Statutory Unit|LDG_NAME|TRU_NAME|State Unemployment|SUI Employer Rate|2022/01/01|1.5|6|1|2

METADATA|ElementEntry|CreatorType|EffectiveStartDate|EffectiveEndDate|ElementName|LegislativeDataGroupName|EntryType|AssignmentNumber|MultipleEntryCount MERGE|ElementEntry|PAY_CREATOR_TYPE|2023/01/01||TEST_ELE|TEST_LDG|E|E101010|1 METADATA|ElementEntryValue|EffectiveStartDate|EffectiveEndDate|InputValueName|ScreenEntryValue|AssignmentNumber|ElementName|LegislativeDataGroupName|LegislationCode|MultipleEntryCount|EntryType MERGE|ElementEntryValue|2023/01/01||Amount|1234.99|E101010|TEST_ELE|TEST_LDG|US|1|E

select aaa.person_number,aaa.element_name,aaa.creator_type,aaa.created_by,aaa.creation_Date,aaa.entry_range,aaa.multiple_entry_count, (select min(date_from)||'~'||max(date_to) from pay_entry_usages where element_entry_id=aaa.element_entry_id) usage_range, aaa.element_entry_id, (select --LISTAGG(piv.name, '; ') WITHIN GROUP (ORDER BY piv.display_sequence) rtrim(xmlserialize(content extract(xmlagg(xmlelement("e", piv.name||'; ') order by piv.display_sequence), '//text()')), ',' ) from PAY_INPUT_VALUES_VL piv where piv.element_type_id = aaa.element_type_id and aaa.start_Date between piv.effective_start_date and piv.EFFECTIVE_END_DATE) inputs, (select --LISTAGG(piv.name||'='||peev.screen_entry_value, '; ') WITHIN GROUP (ORDER BY piv.display_sequence) rtrim(xmlserialize(content extract(xmlagg(xmlelement("e", piv.name||'='||peev.screen_entry_value||'; ') order by piv.display_sequence), '//text()...

 select petf.element_type_id ,pettl.element_name ,petf.processing_type Recurring_NonRecurring ,petf.effective_start_date ,petf.effective_end_date ,petf.multiple_entries_allowed_flag ,pivf.base_name ,pivf.mandatory_flag from pay_element_types_f petf ,pay_element_types_tl pettl ,pay_input_values_f pivf where petf.element_type_id = pettl.element_type_id and pivf.element_type_id=petf.element_type_id and pettl.element_name = :Element_Name and pettl.language='US' and pivf.user_enterable_flag='Y'

Enable the HCM_RESPONSIVE_PAGES_ENABLED profile option for HCM Redesigned Cloud User Experience. Reference :  HCM Responsive Edit Page Demos (Doc ID 2399671.1)