How do you Delete Loaded Assigned Payroll Data ?

 SELECT 'METADATA|AssignedPayroll|AssignedPayrollId|EffectiveStartDate|AssignmentId|LegislativeDataGroupId|PayrollId|PayrollTermId|SourceSystemId|SourceSystemOwner' HEADER, 1 DELETE_ASGPAYROLL
  FROM DUAL
UNION ALL
SELECT 'DELETE|AssignedPayroll'
   ||'|'||
       papd.ASSIGNED_PAYROLL_ID
   ||'|'||
       to_char(papd.start_date,'RRRR/MM/DD')
   ||'|'||    
   paam.assignment_id
   ||'|'||    
   papd.LEGISLATIVE_DATA_GROUP_ID
   ||'|'||    
   papd.Payroll_Id
   ||'|'||    
   papd.Payroll_Term_Id
   ||'|'||    
       hikm.source_system_id
   ||'|'||    
       hikm.source_system_owner HEADER, 2 DELETE_ASGPAYROLL
  FROM pay_assigned_payrolls_dn papd
  ,pay_payroll_terms ppt
  ,pay_pay_relationships_dn prrd
  ,pay_all_payrolls_f papf_pay
  ,pay_rel_groups_dn prgd
  ,pay_rel_groups_f prgf
  ,per_all_people_f papf
  ,per_person_names_f ppnf
  ,per_all_assignments_m paam 
  ,hrc_integration_key_map hikm
 WHERE papd.payroll_term_id = ppt.payroll_term_id
   AND ppt.payroll_relationship_id = prrd.payroll_relationship_id
   AND papd.payroll_id = papf_pay.payroll_id
   AND prrd.person_id = papf.person_id
   AND prrd.payroll_relationship_id = prgd.payroll_relationship_id
   AND prgd.relationship_group_id = prgf.relationship_group_id
   AND prgd.assignment_id = paam.assignment_id
   AND paam.effective_latest_change = 'Y'
   AND prgd.group_type = 'A'
   AND ppnf.person_id = papf.person_id
   AND ppnf.name_type = 'GLOBAL'
   AND TRUNC(SYSDATE) BETWEEN papf.effective_start_date AND papf.effective_end_date
   AND TRUNC(SYSDATE) BETWEEN ppnf.effective_start_date AND ppnf.effective_end_date
   AND TRUNC(SYSDATE) BETWEEN prgf.effective_start_date AND prgf.effective_end_date
   AND TRUNC(SYSDATE) BETWEEN paam.effective_start_date AND paam.effective_end_date
   AND hikm.surrogate_id = papd.ASSIGNED_PAYROLL_ID   
   AND papf.person_number = NVL(:P_PERSON_NUMBER,papf.person_number)
 ORDER BY 2

HCM Data Loader

 HDL is a robust and powerful tool to load data in Fusion. It is flexible file format .dat with pipe-delimited to structure the data to import. It handles complex data structures, such as parent child relationships.

It allows complete data load and incremental data load. It provides detailed error log for each object if we have any failures at Import stage or during Load stage.

HDL supports different keys User Keys, Source Keys and GUID. 

User Keys are preferred for manual HDL or updates with known values. 

Source Keys are preferred for initial data loads, automated integration and to update existing information people will use these keys.

GUID - Globally Unique Identifier, this is system generated and rarely used in Data Migration activities.

User Keys: 

• These are business-meaningful keys used by users.

• Typically, these are combinations of fields that uniquely identify a record.

• Example (for Worker.dat), PersonNumber, EffectiveStartDate

Source Keys:

• These are used to support data loads from external systems.

• Comprise SourceSystemOwner and SourceSystemId

• You must set them when you're maintaining integration from an external system.

Use case: Best when loading data from an external source system that has its own identifiers (e.g., from SAP, Workday, or legacy HRMS).

SourceSystemOwner value can be configured in HRC_SOURCE_SYSTEM_OWNER lookup to identify what is the actual source of data.

Navigation: 

Login and navigate to Setup and Maintenance area and search for the task Manage Common Lookups and search for HRC_SOURCE_SYSTEM_OWNER in lookup type field.