Search Results fnd_object_instance_sets




Overview

The FND_OBJECT_INSTANCE_SETS table is a core repository table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as a master definition table for object instance sets, which are logical groups of object instances. In the initial and primary implementation, these sets define dynamic groups of database rows through a stored SQL predicate (WHERE clause condition). This functionality is foundational for features requiring dynamic, rule-based grouping of data, such as security, data partitioning, and hierarchical relationships, without storing static lists of identifiers. The table is owned by the APPLSYS schema and is integral to the platform's data abstraction and access control layers.

Key Information Stored

The table's primary purpose is to store the unique definition of each instance set. While the provided metadata does not list specific columns, the documented primary key constraint (FND_OBJECT_INSTANCE_SETS_UK1) on the column INSTANCE_SET_NAME is the most critical structural detail. This column stores the unique identifier for the instance set. Based on the table's described function, other columns would typically store the SQL predicate that defines the set's membership, an associated application ID, a user-friendly description, and creation/modification metadata. The foreign key relationships indicate the table also stores object type codes that are referenced by the Trading Community Architecture (TCA) modules to define relationship and hierarchy rules.

Common Use Cases and Queries

A primary use case is the definition of security groups for Oracle EBS' Data Security model (also known as Fine-Grained Access Control), where instance sets dynamically determine which rows a responsibility or user can access within a secured object. Another significant use, evidenced by the foreign keys, is within Oracle TCA to define the subject and object types for party relationships and hierarchy nodes. A common reporting query would involve joining this table to its related TCA entities to audit the definition of relationship rules. For example, to see all instance sets used in defining hierarchy node types, one might use a query pattern such as: SELECT his.NODE_TYPE, os.INSTANCE_SET_NAME FROM HZ_HIERARCHY_NODES his JOIN FND_OBJECT_INSTANCE_SETS os ON os.INSTANCE_SET_NAME = his.PARENT_OBJECT_TYPE; Direct manipulation of this table via DML is strongly discouraged; configuration should be performed through dedicated administrative APIs.

Related Objects

The table has documented foreign key relationships with several key tables in the Trading Community Architecture (HZ) module, highlighting its central role in defining relationship and hierarchy structures. These relationships are:

These relationships confirm that instance sets are used to classify the types of parties (e.g., Organization, Person, Group) that can participate in specific hierarchical or relational roles within the TCA model.