Pipeline Customization Guidelines

This section describes the recommended guidelines for implementing customizations within Data Augmentation Script applications. Adhering to these guidelines helps preserve the integrity of Oracle-delivered content, simplifies future upgrades, and ensures that user-specific extensions are implemented in a consistent and maintainable manner.

General Guidelines

Review these guidelines:
  • Of the ready-to-use Data Augmentation Script applications, only the EBS_CONFIG and EBS_PARAMETERS Data Augmentation Script applications are editable. These applications are intended for user-specific functional configuration and parameter management.
  • All other Oracle-delivered Data Augmentation Script applications are provided with view-only access. You can't modify these but you can copy the hrf code as needed.
  • Oracle recommends implementing all customizations in a custom Data Augmentation Script application. Before making any modifications, copy the required mappings or scripts from the corresponding Oracle-delivered application into the custom application.

Dependent Datasets

  • Define all dependent datasets in the Dependent_Datasets.hrf file.
  • Ensure that each dependent dataset is defined before it is referenced by a mapping.
  • Oracle recommends defining dependent datasets as PRIVATE VERSIONED to ensure that the mapping always processes the latest available version of the dataset.

Module Imports

When a custom mapping references Oracle-delivered data stores, the corresponding application modules must be imported into the custom mapping. For example: Import only the modules required by the custom mapping.
       IMPORT MODULE [EBS_PARAMETERS,EBS_DOMAINS,EBS_CONFIG,EBS_COMMON]

Import Source Statements

Within Oracle-delivered Data Augmentation Script applications, all IMPORT SOURCE statements are maintained in the ImportSource_%.hrf file. When copying an Oracle-delivered mapping into a custom application:
  • Review the source table aliases referenced by the mapping.
  • Locate the corresponding IMPORT SOURCE statements in the ImportSource_%.hrf file of the Oracle-delivered application.
  • Copy the required IMPORT SOURCE statements into the custom mapping and resolve the aliases accordingly.

This ensures that all required source data stores are correctly referenced during execution.

Dataset Visibility

Oracle recommends the following visibility guidelines:
  • Define all intermediate datasets as PRIVATE.
  • Use PUBLIC only for the final output dataset that is consumed by downstream mappings or publishing processes.

This approach minimizes unnecessary exposure of intermediate processing datasets and maintains a clean application structure.

HRF File Maintenance

Some aliases and lookup datasets within the Oracle-delivered .hrf files may be commented because they are referenced by previously included HRF files. When implementing customizations:
  • Review all referenced aliases and lookup datasets.
  • Uncomment only those entries that are required by the custom mapping.

For more information on Data Augmentation Scripts, see Overview of Data Augmentation Scripts.