Oracle® Fusion Applications Coexistence for HCM Implementation Guide 11g Release 7 (11.1.7) Part Number E20378-05 |
![]() Home |
![]() Contents |
![]() Book List |
![]() Contact Us |
![]() Previous |
![]() Next |
This chapter contains the following:
Deleting HCM Stage Data and Files for Coexistence: Explained
Data that you upload to Oracle Fusion Human Capital Management (HCM) is imported first to the Load Batch Data stage tables. Following validation against Oracle Fusion business rules, data is loaded from the stage tables to the application tables.
Whenever you upload changed data to Oracle Fusion HCM, you must resend all of the original data for a business object type. For example, if you update one person's home address, then you must upload all person records again. If you regularly upload changes for several types of business objects, then the Load Batch Data stage tables can grow very quickly. This topic explains how to delete data batches from the Load Batch Data stage tables. It also describes the circumstances in which the associated zip files and directory structures are deleted from the Oracle Fusion Application Server.
To identify batches for deletion from the Load Batch Data stage tables, you perform the Delete HCM Stage Data and Files for Coexistence task in the Data Exchange work area.
On the Delete HCM Stage Data and Files for Coexistence page, you search for batches to delete by entering From Date, To Date, and Batch Status values. If you specify no From Date value, then 01/01/0001 is used.
Batches with both the specified status and a processing time stamp that falls in the specified date range appear in the search results. For example, you could search for all Completed batches for the previous week or all Not Processed batches for today.
A batch's processing time stamp is derived as follows:
If an attempt has been made to load a batch to the application tables, then the processing time stamp records when the attempt was made.
If no attempt has been made to load a batch to the application tables, then the processing time stamp records when the batch was generated in the stage tables.
You cannot delete batches that are in progress.
All batches that appear in the Search Results region are deleted when you submit the deletion process. To remove batches from these results, you must adjust the search criteria and search again.
When you are ready to proceed, you schedule the Delete HCM Stage Data and Files for Coexistence process; the search criteria are carried forward automatically to the Schedule Process page.
Use the process ID to monitor the process in the Scheduled Processes work area.
In some circumstances, the Delete HCM Stage Data and Files for Coexistence process also deletes the following items from the Oracle Fusion Application Server:
The original zip file associated with a batch
The decompressed file and its directory structure
Files that were imported to the stage tables within the specified dates and for which no associated batches remain are deleted. However, if any of the associated batches remains and will not be removed by the deletion process, then no file or directory deletion occurs.
To perform the task Delete HCM Stage Data and Files for Coexistence, you must have the HCM Co-Existence Management Duty role. By default, the Application Implementation Consultant and Human Capital Management Application Administrator job roles have this duty role.