Search Results ies_script_jarfiles




Overview
Explore in AI Chat

Overview

The IES_SCRIPT_JARFILES table is a core metadata object within the Oracle E-Business Suite Scripting (IES) module. It stores the associations between Java archive (JAR) files and deployed scripts, enabling the scripting framework to resolve and load the required libraries when a script executes. In EBS 12.1.1 and 12.2.2, the IES schema supports the JTT (Java-based) scripting infrastructure, and this table acts as the bridge that records which JAR files each deployed script depends on. Without these associations, the scripting runtime would be unable to determine classpath requirements and could not reliably instantiate script classes at runtime.

Based on the foreign key topology mined from the ETRM metadata and its heuristic Data Vault classification, this object is best modeled as a link. It resolves a many-to-many relationship between deployed scripts (IES_DEPLOYED_SCRIPTS) and JAR files (IES_JARFILES), carrying descriptive attributes such as LOAD_ORDER that qualify the relationship. It is not a pure hub, since its primary key is a surrogate identifier rather than a business key derived from either parent.

Key Information Stored

The table contains 27 documented columns. The most operationally significant are:

  • SCRIPT_JARFILE_ID — Surrogate primary key defined by IES_SCRIPT_JARFILES_PK; uniquely identifies each script-to-JAR association row.
  • DSCRIPT_ID — Foreign key to IES_DEPLOYED_SCRIPTS, identifying the deployed script that depends on the JAR.
  • JARFILE_ID — Foreign key to IES_JARFILES, identifying the specific JAR file linked to the script.
  • LOAD_ORDER — Sequence value controlling the order in which associated JAR files are loaded at runtime; critical when class resolution depends on precedence.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant or data-group security partitioning across the EBS instance.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF-based IES UI to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns providing audit lineage for each association row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) storage for extensible, customer-defined metadata.

The composite of DSCRIPT_ID and JARFILE_ID functions as the practical business key, although the documented primary key remains SCRIPT_JARFILE_ID. Administrators configuring dependencies should treat the DSCRIPT_ID/JARFILE_ID pair as the logical uniqueness constraint.

Common Use Cases and Queries

Typical scenarios include auditing which JARs a given script requires, diagnosing class-loading failures, and validating dependency integrity after deployments. A representative query lists all JAR dependencies for a named deployed script:

  • SELECT sj.script_jarfile_id, sj.dscript_id, sj.jarfile_id, sj.load_order FROM ies.ies_script_jarfiles sj WHERE sj.dscript_id = :p_dscript_id ORDER BY sj.load_order;
  • Join to IES_JARFILES to obtain JAR names and versions for deployment documentation.
  • Join to IES_DEPLOYED_SCRIPTS to report which scripts would be affected by retiring a specific JAR file — an impact analysis query commonly run before patch application.
  • Filter by SECURITY_GROUP_ID in multi-org or data-group-enabled environments to scope results appropriately.
  • Detect orphaned associations by left-joining to both parent tables and filtering on null keys, a data-integrity check useful after incomplete deployments.

Related Objects

  • IES_DEPLOYED_SCRIPTS — Parent table joined on IES_SCRIPT_JARFILES.DSCRIPT_ID = IES_DEPLOYED_SCRIPTS.DSCRIPT_ID; holds the deployed script definitions.
  • IES_JARFILES — Parent table joined on IES_SCRIPT_JARFILES.JARFILE_ID = IES_JARFILES.JARFILE_ID; holds the registered JAR file metadata.
  • FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID, governing row-level security visibility.
  • IES_SCRIPT_JARFILES_PK — The defining primary key constraint over SCRIPT_JARFILE_ID.
  • IES Dependencies / Deployment APIs — The IES deployment utilities that populate this table when scripts are deployed with associated libraries.

Collectively, these objects form a dependency-resolution graph that the IES scripting runtime traverses to construct classpaths for deployed Java scripts.