Search Results run_prms_id

Overview

The IGS_HE_EXT_RUN_PRMS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically under the IGS (iGrads) product family. Its primary function is to store the detailed runtime filtering parameters for individual data extraction jobs. When an external data extract is initiated, this table holds the specific criteria that define the scope of the data to be pulled from the database, enabling precise control over the extraction process. It acts as a child table, storing the configuration details for a parent extract run defined elsewhere.

Key Information Stored

The table's columns are designed to capture the unique identifier, the parent run, the filtering logic, and standard audit information. The RUN_PRMS_ID column is the primary key, a system-generated sequence that uniquely identifies each parameter record. The EXTRACT_RUN_ID is a foreign key that links the parameters to a specific execution instance in a related run details table. The PARAM_TYPE column defines the category of data being filtered (e.g., a specific entity or attribute). The EXCLUDE and ONLY columns provide the actual filtering values; EXCLUDE holds values to be omitted from the extract, while ONLY restricts the output to a specified set of values, based on the defined PARAM_TYPE.

• RUN_PRMS_ID: Primary key. Unique identifier for the parameter set.
• EXTRACT_RUN_ID: Foreign key. Links to the master extract run record.
• PARAM_TYPE: Defines the category of the filtering parameter.
• EXCLUDE/ONLY: Complementary fields containing the specific values used to filter the data extract.
• Standard WHO Columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for audit trails.

Common Use Cases and Queries

This table is central to generating customized data extracts for external reporting or system interfaces. A common use case is configuring a HESA (Higher Education Statistics Agency) or similar regulatory return, where data for specific academic programs, locations, or student cohorts must be isolated. Administrators would configure a run with parameters stored in this table to include ONLY students from a particular campus or EXCLUDE records from a specific academic year. For troubleshooting or auditing, one might query all parameters for a specific extract run to verify its configuration.

Sample Query to Retrieve Parameters for a Specific Run:
SELECT param_type, exclude, only
FROM igs.igs_he_ext_run_prms
WHERE extract_run_id = :run_id
ORDER BY run_prms_id;

Sample Query to Find All Runs Using a Specific Parameter Value:
SELECT prms.extract_run_id, prms.param_type
FROM igs.igs_he_ext_run_prms prms
WHERE prms.only LIKE '%<VALUE>%' OR prms.exclude LIKE '%<VALUE>%';

Related Objects

The IGS_HE_EXT_RUN_PRMS table has a defined dependency relationship within the IGS schema. Its primary key, RUN_PRMS_ID, is enforced by the unique index IGS_HE_EXT_RUN_PRMS_U1. Crucially, it maintains a foreign key relationship where its EXTRACT_RUN_ID column references a parent table, IGS_HE_EXT_RUN_DTLS. This establishes that every set of run parameters must belong to a valid, pre-defined extract run master record. The table is also referenced by an object in the APPS schema, indicating it is accessed via public synonyms or views for application logic and reporting within the EBS framework.

• Primary Key Constraint: IGS_HE_EXT_RUN_PRMS_PK on column RUN_PRMS_ID.
• Foreign Key Relationship: Column EXTRACT_RUN_ID references TABLE: IGS.IGS_HE_EXT_RUN_DTLS.
• Referenced By: An object in the APPS schema (likely a public synonym or view).