Search Results ies_aux_script_relationship_pk

Overview

The IES.IES_AUX_SCRIPT_RELATIONSHIPS table is an auxiliary data object within the IES Scripting module of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). Its stated purpose is to store relationships between deployed scripts, providing the associative layer that links one script to another within a defined contextual meaning. Where the IES_DEPLOYED_SCRIPTS table functions as the repository of individual script definitions, this table records how those scripts interrelate — for example, calling, chaining, or dependency associations.

From a Data Vault modeling perspective, the FK structure mined from the metadata suggests that this table is best classified as a link table. It resolves a many-to-many relationship between two instances of the IES_DEPLOYED_SCRIPTS entity (represented by SCRIPT_A_ID and SCRIPT_B_ID), with the relationship type captured as descriptive attribute data. This classification is heuristic and offered as a modeling suggestion rather than a prescriptive definition.

Key Information Stored

The table contains 27 documented columns. The most significant are summarized below.

• SCRIPT_RELATIONSHIP_ID — Surrogate primary key, enforced by IES_AUX_SCRIPT_RELATIONSHIP_PK. Uniquely identifies each relationship record.
• SCRIPT_A_ID — Foreign key to IES_DEPLOYED_SCRIPTS; the first (source) script in the relationship pair.
• SCRIPT_B_ID — Foreign key to IES_DEPLOYED_SCRIPTS; the second (target) script in the relationship pair.
• RELATIONSHIP — Describes the semantic nature of the relationship between SCRIPT_A_ID and SCRIPT_B_ID.
• SECURITY_GROUP_ID — Reference to FND_SECURITY_GROUPS, supporting Multi-Org / data-security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) columns for extensibility.

The surrogate primary key (SCRIPT_RELATIONSHIP_ID) is distinct from any business-key candidate. In the absence of a documented unique index other than the PK, the combination of SCRIPT_A_ID, SCRIPT_B_ID, and RELATIONSHIP should be treated as the logical business key when de-duplicating records.

Common Use Cases and Queries

Typical scenarios include tracing script dependency chains, auditing script deployment relationships, and reporting on script interconnections for impact analysis.

• Find all targets related to a given source script:

SELECT r.SCRIPT_RELATIONSHIP_ID, r.SCRIPT_A_ID, r.SCRIPT_B_ID, r.RELATIONSHIP
FROM   IES.IES_AUX_SCRIPT_RELATIONSHIPS r
WHERE  r.SCRIPT_A_ID = :script_id;

• Join both endpoints back to script definitions:

SELECT a.SCRIPT_ID, b.SCRIPT_ID, r.RELATIONSHIP
FROM   IES.IES_AUX_SCRIPT_RELATIONSHIPS r,
       IES.IES_DEPLOYED_SCRIPTS a,
       IES.IES_DEPLOYED_SCRIPTS b
WHERE  r.SCRIPT_A_ID = a.SCRIPT_ID
AND    r.SCRIPT_B_ID = b.SCRIPT_ID;

• Security-filtered reporting: restrict by SECURITY_GROUP_ID, noting that in an R12 Multi-Org context this column frequently has a system-level sentinel value and is not always filtered at query time.
• Concurrency control: use OBJECT_VERSION_NUMBER in update statements to prevent lost updates.

Related Objects

The following objects are most significant in relation to this table and its foreign-key dependencies:

• IES_DEPLOYED_SCRIPTS — Referenced twice, via SCRIPT_A_ID and SCRIPT_B_ID. This is the core parent table for script definitions.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID, supplying the security partition context.
• IES_AUX_SCRIPT_RELATIONSHIP_PK — The primary-key constraint owned directly by this table.
• IES script definition and deployment views/APIs — Downstream consumers that resolve the relationship graph when processing script execution order.
• EBS WHO audit columns — While not separate objects, the FND standard audit columns integrate this table with EBS logging infrastructure.

Because the table is auxiliary, direct application DML is uncommon; most access occurs through the IES Scripting runtime and deployment components, with SQL querying reserved for diagnostics and reporting.