Search Results ies_jarfiles_pk

Overview

IES_JARFILES is a table in the IES (Scripting) product schema of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. The table is described in the ETRM documentation as holding "all the jar files that are used by different scripts." In practice it acts as a central repository of Java archive (JAR) binaries that the IES scripting framework makes available to scripts at runtime, allowing a script to invoke packaged Java classes without each script carrying its own copy of the library.

The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. Modelled formally, IES_JARFILES is best treated as a hub: its primary key, JARFILE_ID, is a surrogate identifier that is referenced from the associative table IES_SCRIPT_JARFILES, which in turn links JAR files to scripts. Descriptive attributes such as the file name and the binary payload would normally be split into a satellite in a strict Data Vault implementation; here they reside in the same physical table.

Key Information Stored

The physical table in the IES schema carries 27 documented columns. The most significant are:

• JARFILE_ID — surrogate primary key, enforced by the IES_JARFILES_PK constraint. This is the value users search for as "jarfile_id" and the column referenced by the dependent table.
• JARFILE — the stored JAR content itself, typically a BLOB, forming the actual binary artifact.
• JARFILE_NAME — the business name of the archive, the natural identifier used to identify a library within the repository.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used to partition records by security group in a multi-organization or multi-tenant deployment.
• OBJECT_VERSION_NUMBER — optimistic concurrency control column used by the OAF/BC4J framework.
• GLOBAL_FLAG — indicates whether the JAR file is shared across security groups.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) extension columns.

Only one unique index is documented, the LOB-related SYS_IL0000083925C00008$$ on the JARFILE column; there is no separate unique business key beyond the primary key, so JARFILE_NAME should be treated as an application-level natural identifier rather than a database-enforced one.

Common Use Cases and Queries

Typical usage centers on identifying which archives exist, which scripts consume them, and how they are secured.

• Look up a JAR by identifier: SELECT jarfile_id, jarfile_name, global_flag FROM ies.ies_jarfiles WHERE jarfile_id = :p_id;
• Find the scripts attached to a JAR by joining through the association table: SELECT s.script_name FROM ies.ies_script_jarfiles sj, ies.ies_jarfiles j WHERE sj.jarfile_id = j.jarfile_id AND j.jarfile_name = :p_name;
• List JAR files restricted to a security group or flagged global: SELECT jarfile_name FROM ies.ies_jarfiles WHERE global_flag = 'Y' OR security_group_id = :p_group;
• Audit recently added or changed archives using the WHO columns.
• Detect orphan JAR records that no script references, using an outer join from IES_JARFILES to IES_SCRIPT_JARFILES.

Reporting queries should generally avoid selecting the JARFILE BLOB column to prevent unnecessary LOB reads.

Related Objects

• IES_SCRIPT_JARFILES — associative table referencing IES_JARFILES.JARFILE_ID; resolves the many-to-many relationship between scripts and JAR files.
• IES_SCRIPTS — the parent script definition table reached through IES_SCRIPT_JARFILES.
• FND_SECURITY_GROUPS — referenced by IES_JARFILES.SECURITY_GROUP_ID.
• IES_JARFILES_PK — the primary key constraint on JARFILE_ID.
• IES_JARFILES table API / IES scripting runtime — the framework components that load and instantiate JAR contents during script execution.