Results for “instance_set_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_OBJECT_INSTANCE_SETS is a reference table in the APPLSYS schema of Oracle E-Business Suite, owned by the FND – Application Object Library product. It stores metadata describing object instance sets, which are named groupings of object instances. According to the documented description, instance sets initially define groups of database rows via a SQL predicate, allowing the application to treat a dynamically computed collection of records as a single logical unit. Instance sets therefore act as reusable segmentation definitions consumed by various EBS subsystems, including the Oracle Trading Community Architecture (TCA) and its hierarchy and relationship facilities.

The table carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Within the documented 12.2.2 physical schema, the table is composed of 10 columns. Based on the foreign key topology — where multiple TCA tables reference INSTANCE_SET_NAME as a lookup — the object behaves as a reference or hub-style entity in a Data Vault sense: a stable, uniquely identified business concept that other tables link to. This classification is a modeling heuristic derived from the FK structure rather than a formal Oracle designation.

Key Information Stored

The table centers on a small set of identifying and descriptive attributes:

• INSTANCE_SET_ID — the surrogate primary key column for the instance set; also part of the composite unique index FND_OBJECT_INSTANCE_SETS_U1 (INSTANCE_SET_ID, ZD_EDITION_NAME).
• INSTANCE_SET_NAME — the user-facing business key. In the documented 12.2.2 schema it participates in FND_OBJECT_INSTANCE_SETS_U2 (INSTANCE_SET_NAME, ZD_EDITION_NAME), and in the 12.1.1 documentation it was the sole column of primary key FND_OBJECT_INSTANCE_SETS_UK1.
• OBJECT_ID — identifies the object type or entity to which the instance set applies, binding the set to a specific business object definition.
• PREDICATE — the SQL predicate fragment that dynamically defines which database rows belong to the set.
• ZD_EDITION_NAME — the editioning column supporting Oracle EBS 12.2 online patching and edition-based redefinition, which is why the unique keys in 12.2.2 are composites.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-did-what auditing.

The distinction between the surrogate ID and the name-based unique index is important: integrations frequently resolve an instance set by INSTANCE_SET_NAME, while internal joins use INSTANCE_SET_ID.

Common Use Cases and Queries

Typical scenarios include resolving a named instance set to its predicate, auditing which sets reference a given object, and joining instance sets to TCA relationship and hierarchy tables. A representative lookup query is:

SELECT instance_set_id, instance_set_name, object_id, predicate
FROM   applsys.fnd_object_instance_sets
WHERE  instance_set_name = :set_name;

Analysts often scan PREDICATE values to understand the row-level filter applied to a grouping, and report on creation and last-update metadata for governance. Because the same INSTANCE_SET_NAME is referenced by several TCA relationship tables, join queries such as the following are common:

SELECT r.subject_type, r.object_type, s.instance_set_name
FROM   hz_relationships r
JOIN   fnd_object_instance_sets s
       ON s.instance_set_name = r.subject_type;

Related Objects

The documented FK relationships show that FND_OBJECT_INSTANCE_SETS is referenced by multiple Oracle Trading Community Architecture tables, confirming its role as a shared reference source:

• HZ_HIERARCHY_NODES — references the instance set through PARENT_OBJECT_TYPE and CHILD_OBJECT_TYPE.
• HZ_RELATIONSHIPS — references it via SUBJECT_TYPE and OBJECT_TYPE.
• HZ_RELATIONSHIP_TYPES — references it via SUBJECT_TYPE and OBJECT_TYPE.

These relationships indicate that instance sets supply the permissible object type values used when defining TCA hierarchies, relationships, and relationship types. Administrators should therefore treat deletions or renames of instance set names with caution, since dependent TCA configuration may reference them.