Oracle continues to enhance the user experience by introducing Redwood UX across Oracle Fusion Cloud applications. As part of this ongoing experience enhancement, the View Extract Results page for Oracle HCM Extracts has been redesigned using Visual Builder Studio (VBS). The Redwood-based interface provides a modern, intuitive, and user-friendly experience for administrators who need to monitor and manage HCM Extract executions. It brings key execution information into a more accessible view, making it easier to review extract status, execution details, generated output files, diagnostics, and performance information.

The View Extract Results page serves as a centralized location for monitoring submitted HCM Extract instances, including running, completed, and failed extract instances. Administrators can search for specific extract instances, apply filters, review quick instance details, and open detailed execution information when further analysis is required. The redesigned page also provides access to important tabs such as Criteria, Instance Details, Changes Only Details, Extract Delivery Options, Diagnostics, and Extract Run Analysis, each providing specific information about the extract execution.

These capabilities can be particularly useful when administrators need to troubleshoot failed or long-running extracts, verify the parameters used during submission, review generated output files, analyze processing metrics, or compare the performance of multiple extract executions. The Rollback option also provides a way to remove archived data from successfully completed and archived extract instances when the extract needs to be resubmitted and reprocessed.

In this blog, we’ll explore the key features of the Redwood-based View Extract Results page, understand the information available across each tab, and review the best practices and common mistakes to consider when managing HCM Extract runs.

Key Concept

The View Extract Results page provides a centralized location to monitor all submitted HCM Extract instances, including:

• Running extract instances
• Completed extract instances
• Failed extract instances

The redesigned Redwood page simplifies extract monitoring by providing quick access to extract details, execution status, diagnostics, generated output files, and performance analysis.

Navigation

My Client Groups → Data Exchange → View Extract Results

Features and Functionality

Searching and Filtering Extract Instances

The View Extract Results page allows administrators to quickly locate submitted extract instances.

You can search using the instance name or apply filters based on:

• Extract Name
• Legislative Data Group
• Status
• Submitted By
• Submission Date

These filtering options help administrators quickly identify specific extract executions without browsing through the complete list.

Viewing Quick Instance Details

Select the Chevron (>) icon at the end of an extract instance to view summary information without opening the complete record.

The quick details include:

• Legislative Data Group
• Process Status
• Submitted By
• Submission Date
• Instance Age

This feature enables administrators to review essential information at a glance.

Viewing Detailed Extract Run Information

Click the Extract Instance Name to open the detailed execution page.

The Details page displays:

• Extract Name
• Workflow Process Name
• Submission Date
• Completion Date
• Overall Status
• Process Occurrence State
• Elapsed Time

The page also provides access to several tabs for detailed analysis:

• Criteria
• Instance Details
• Changes Only Details
• Extract Delivery Options
• Diagnostics
• Extract Run Analysis

Rollback Option

For successfully completed and archived extract instances, the Rollback button is available.

Rollback removes the archived data associated with the extract instance, allowing administrators to resubmit and reprocess the extract when required.

Note: The Rollback option isn’t available for:

• Running extract instances
• Failed extract instances

Understanding Each Tab

1. Criteria Tab

The Criteria tab displays all parameters used while submitting the extract.

Examples include:

• Baseline Only
• Changes Only
• Process Start Date
• Process End Date
• Process Configuration Group

This helps administrators verify the exact configuration used during execution.

2. Instance Details Tab

The Instance Details tab displays the complete process hierarchy for the extract execution.

It provides:

• Process Status
• Start Time
• Completion Time
• Downloadable Log Files

The log files are particularly useful when troubleshooting failed processes or investigating long running extract executions.

3. Changes Only Details Tab

The Changes Only Details tab is available only when the extract is executed in Changes Only mode.

This tab allows administrators to:

• Review attribute changes
• Compare values from the previous successful run
• Validate incremental data processing

It also confirms whether the Changes Only parameter was enabled during submission.

4. Extract Delivery Options Tab

The Extract Delivery Options tab displays all output files generated by the extract execution.

Administrators can download the generated files once the extract completes successfully.

This simplifies verification of delivered output files.

5. Diagnostics Tab

The Diagnostics tab provides detailed execution metrics for each processing phase.

The displayed phases include:

• Preprocessing
• Archive Processes
• Root Data Group Extract
• XML Generation
• XML Delivery
• Attachment Delivery

It also includes a Metrics Dashboard displaying:

• Total Processed Objects
• Successful Records
• Failed Records
• Pending Records
• Ignored Records

This information helps identify bottlenecks and monitor extract performance.

6. Extract Run Analysis Tab

The Extract Run Analysis tab enables administrators to compare multiple extract executions.

You can:

• Select previous extract instances
• Compare related ESS jobs
• Generate comparative line graphs
• Analyze execution times for each processing phase

This analysis helps identify performance trends and opportunities for optimization.

Best Practices

To get the most value from the Redwood View Extract Results page:

Use filters to quickly locate extract instances.

Applying filters such as Extract Name, Legislative Data Group, Status, Submitted By, and Submission Date helps administrators find specific extract instances without manually reviewing the complete list. This can reduce the time required to identify and review relevant executions.

Review Quick Details before opening the complete extract.

The Quick Details option provides essential information such as Legislative Data Group, Process Status, Submitted By, Submission Date, and Instance Age. Reviewing this information first allows administrators to quickly understand the status of an extract instance and open the complete record only when further investigation is required.

Download log files whenever an extract fails.

Log files provide useful information about the extract execution and can help administrators identify the cause of failed processes. Reviewing these logs supports faster troubleshooting and helps administrators understand where an execution encountered an issue.

Use the Diagnostics tab to monitor processing performance.

The Diagnostics tab provides execution metrics across different processing phases, along with the Metrics Dashboard. Reviewing these metrics helps administrators identify failed records, pending records, ignored records, and potential processing bottlenecks, providing better visibility into extract performance.

Review Changes Only Details when running incremental extracts.

The Changes Only Details tab helps administrators review attribute changes and compare values with the previous successful run. This provides better visibility into incremental data processing and helps verify that the Changes Only parameter was enabled during submission.

Compare extract executions using Extract Run Analysis to identify performance improvements.

Extract Run Analysis allows administrators to compare previous extract instances, related ESS jobs, and execution times across processing phases. Reviewing these comparisons can help identify performance trends and areas where extract execution can be optimized.

Use Rollback only when archived data must be removed before rerunning an extract.

The Rollback option can remove archived data associated with successfully completed and archived extract instances. Using this option when required allows administrators to prepare the extract for resubmission and reprocessing while maintaining better control over archived extract data.

Common Mistakes

Avoid these common mistakes while working with HCM Extract Results. Being aware of these issues can help administrators monitor extract executions more effectively and troubleshoot problems without overlooking important execution details.

Not using filters makes it difficult to locate extract instances.

When a large number of extract instances are available, manually browsing through the complete list can make it difficult to identify a specific execution. Not using filters such as Extract Name, Legislative Data Group, Status, Submitted By, and Submission Date can increase the time required to locate and review the required extract instance.

Ignoring log files when troubleshooting failed extracts.

Log files contain important information about the extract execution and can help identify errors or issues encountered during processing. Ignoring these logs can make troubleshooting more difficult because administrators may not have sufficient execution details to determine where the process failed.

Attempting Rollback on running or failed extract instances.

The Rollback option is available for successfully completed and archived extract instances. Attempting to use Rollback for running or failed extract instances can lead to confusion when managing extract executions. Administrators should first verify the extract status and confirm that the instance is eligible for Rollback before using the option.

Forgetting to verify the Criteria tab before analyzing extract results.

The Criteria tab displays the parameters used while submitting the extract, including Baseline Only, Changes Only, Process Start Date, Process End Date, and Process Configuration Group. Not reviewing these parameters can make it difficult to understand the configuration under which the extract was executed and can affect the analysis of the results.

Ignoring Diagnostics metrics that could indicate performance issues.

The Diagnostics tab provides detailed execution metrics across different processing phases and includes information such as Total Processed Objects, Successful Records, Failed Records, Pending Records, and Ignored Records. Ignoring these metrics can cause administrators to overlook processing bottlenecks or other performance-related issues that may require further investigation.

Not reviewing Extract Run Analysis to identify execution trends.

Extract Run Analysis provides the ability to compare multiple extract executions, related ESS jobs, and execution times across processing phases. Not reviewing this information can make it difficult to identify changes in execution performance or recurring trends that could help administrators optimize extract processing.

Conclusion

The Redwood Experience for HCM Extracts: View Extract Results provides a modern, efficient, and user-friendly interface for managing HCM Extract executions. With enhanced search capabilities, detailed execution information, diagnostics, downloadable logs, delivery options, and comparative performance analysis, administrators can monitor extract processing more effectively and troubleshoot issues with greater confidence.

By leveraging these Redwood features, organizations can improve extract monitoring, optimize execution performance, and simplify HCM Extract administration.

Optimize HCM Extract Management with Oracle HCM Cloud Services

Managing HCM Extracts effectively requires clear visibility into extract executions, output files, diagnostics, processing performance, and execution history. Proper configuration and monitoring can help administrators troubleshoot issues, manage extract runs efficiently, and improve overall extract processing.

Kovaion’s Oracle HCM Cloud Services help organizations configure, implement, integrate, and optimize Oracle Cloud HCM solutions based on their business and workforce requirements. Our expertise includes HCM Extracts, integrations, data migration, configuration, testing, enhancements, upgrades, and ongoing support.

Looking to improve your Oracle HCM Extract management and monitoring? Connect with Kovaion to explore how our Oracle HCM Cloud Services can support your HCM requirements.