1. HCM Extracts
  2. Enhanced Extract Processing and Performance Features

Enhanced Extract Processing and Performance Features

Enhanced extracts provide several runtime and output-processing features that improve extract execution, scalability, and validation.

These features help optimize preprocessing performance, support large extract outputs, and simplify report validation before delivery.

The enhanced extracts engine supports preprocessing multithreading, output file chunking, and previewing extract output using a sample BI Publisher run.

Seeded Extract Configuration Groups

Enhanced extracts provide the following seeded extract configuration groups that can be copied and customized to support performance tuning and runtime feature configuration:

  • Extract Default V2
  • High Performance V2
  • Extreme Performance V2

Use these configuration groups as the base configuration when enabling enhanced extract runtime features such as preprocessing multithreading and output file chunking

Preprocessing Multithreading

Purpose:

During preprocessing, the enhanced extracts engine identifies the business objects that must be included in the extract and stores them for downstream processing. For extracts that process large volumes of data or use complex selection criteria, preprocessing can become a performance bottleneck if the operation runs in a single thread.

Preprocessing multithreading improves performance by distributing preprocessing operations across multiple threads. This reduces overall execution time and improves scalability for large extract runs.

Feature Processing:

When multithreading is disabled, preprocessing runs sequentially in a single thread. In extracts that contain complex criteria or large object sets, this can significantly increase processing time.

When multithreading is enabled, preprocessing tasks are distributed across multiple threads so that multiple object sets can be processed concurrently. This improves throughput and reduces delays during extract initialization.

Preprocessing multithreading supports only the following object types:

  • Person ID
  • Assignment ID
  • Payroll Relationship ID
  • Period of Service ID
  • Payroll Assignment ID
Note:

Extract definitions that don’t support multithreaded processing must be updated before this feature can be used.

Parameters:
Use the following parameters to configure preprocessing multithreading:
  • ORA_HEX_MULT_THRD_PRE_PROC - Enables or disables preprocessing multithreading. Valid values are Enabled and Disabled. Default value is Disabled.
  • ORA_HEX_PRE_PROC_THREAD_COUNT - Specifies the number of preprocessing threads to use when multithreading is enabled. Valid range is 2 to 32. Default value is 8.

Adding Parameters to New Extract Configuration Group to include Multithreading:

  1. Navigate to My Client Groups > Data Exchange > Extract Configuration Groups
  2. Create a copy of Extreme Performance V2 configuration group
  3. On the new configuration group page,
    1. Set the Preprocess Multithreading parameter as Enabled
    2. Set the Preprocess Multithread Count parameter to an appropriate value with the range
    3. Click Save

Chunking of Output Files

Purpose:

Large extract output files can create delivery and processing issues, particularly when files exceed downstream system limitations or transfer thresholds.

Output file chunking improves scalability by splitting a large extract output into multiple smaller files. This simplifies delivery and improves reliability for large extract runs.

Feature Processing:

When chunking is enabled, the enhanced extracts engine divides the extract output into multiple files based on a configured chunk size.

The engine automatically creates sequential output chunks during extract generation, which can then be delivered independently to downstream systems.

Output file chunking isn’t supported for the following scenarios:

  • Documents of Record (DOR)
  • Bursting operations
Parameters:
Use the following parameters to configure preprocessing multithreading:
  • ORA_HEX_OUTPUT_CHUNKING - Specifies whether output file chunking is enabled. Valid values are Y and N. Default value is Y.
  • ORA_HEX_OUTPUT_CHUNK_SIZE - Specifies the number of records included in each output chunk. Default value is 50000.

Adding Parameters to New Extract Configuration Group to include Auto-chunking:

  1. Navigate to My Client Groups > Data Exchange > Extract Configuration Groups
  2. Create a copy of Extreme Performance V2 configuration group
  3. On the new configuration group page,
    1. Set the Chunk Output parameter as Yes
    2. Set the Output Chunk Size parameter tas 5000
    3. Click Save

Previewing Extract Output Using Sample BI Publisher Run

Purpose:

The sample BI Publisher run feature allows you to preview extract output before submitting the extract for delivery. This feature helps validate report templates, delivery options, and output formatting during extract development and testing. The preview capability is available for custom extracts.

Generating Preview Output:
  1. In the Extract Definitions page, select the extract and click Preview on the left pane
  2. Enter an effective date for the preview run and click Preview to generate a preview version of the extract output using the selected extract definition and report configuration
Select Delivery Options: After generating preview data, select the delivery option to preview.

The preview run supports the same BI Publisher delivery configurations used during extract processing. This allows you to validate the

  • Report templates
  • Output formatting
  • Delivery-specific rendering

    before running the extract in production.

View the Report Output:
  1. Click Show Report
  2. The system displays a preview of the final BI Publisher output generated from the extract data and associated report template.

  3. Use the preview output to validate the following aspects before submitting the extract for production processing:

    • Data formatting
    • Report layout
    • Template configuration
    • Delivery behavior