Results for “so_objects_pk”

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

Overview

SO_OBJECTS is an Order Entry (OE) reference table in the Oracle E-Business Suite, owned by the OE schema. Its documented purpose is to store the objects that are used in security rules and standard value rule sets. In practical terms, the table acts as a registry of the business entities — such as orders, order lines, and related Order Management constructs — that Oracle's rules engine can constrain or populate. Security rules in Order Management determine which records a given user or responsibility may view or transact against, and standard value rule sets drive defaulting and validation logic. SO_OBJECTS supplies the master list of those governed entities.

From a modeling perspective, the heuristic Data Vault classification supplied with this object is hub-leaning. SO_OBJECTS therefore behaves primarily as a hub: it holds a stable, uniquely identifiable set of object definitions, with descriptive attributes attached and no inherent transaction grain of its own. This classification is a suggestion for downstream modeling rather than a structural property of the EBS table itself.

Key Information Stored

The table is documented with 29 columns, a subset of which carries nearly all functional meaning:

• OBJECT_ID — the surrogate primary key, enforced by SO_OBJECTS_PK and uniquely indexed by SO_OBJECTS_U1. It is the column referenced by all dependent child tables.
• OBJECT_CODE — the developer-facing business key, uniquely indexed by SO_OBJECTS_U2. This is the value external code and rule definitions typically key on.
• NAME — the user-facing label for the object, uniquely indexed by SO_OBJECTS_U3 (SO_OBJECTS_UK2 in the ETRM listing).
• BASE_OBJECT_ID — a self-referencing discriminator that distinguishes a base object from objects derived or extended from it.
• TABLE_APPLICATION_ID and TABLE_NAME — the composite foreign key into FND_TABLES, identifying the underlying database table (and its owning application) that materializes the object.
• DESCRIPTION — free-text explanation of the object's role.
• CONTEXT — the descriptive flexfield context code used to segment the DFF columns.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield segments, available for customer-specific extensions.
• COMPILED_INFORMATION — the compiled or cached representation of the object's rule metadata, used by the rules engine at runtime.

The remaining columns are the standard WHO audit set: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most frequent requirement is resolving an OBJECT_ID to its human-readable name while simultaneously locating the physical table that backs it. This joins SO_OBJECTS to FND_TABLES:

• SELECT o.OBJECT_ID, o.OBJECT_CODE, o.NAME, o.TABLE_NAME, o.DESCRIPTION FROM OE.SO_OBJECTS o ORDER BY o.OBJECT_CODE;

To identify which attributes belong to a specific governed object, join to SO_ATTRIBUTES on OBJECT_ID. To determine which security rules constrain an object, join to SO_SECURITY_RULES on OBJECT_ID. A common diagnostic query lists each object alongside the number of security rules that reference it, which is useful when troubleshooting why a user can or cannot see particular order records.

Reporting use cases include: auditing the complete registry of secured objects during an upgrade or patch assessment; validating that every object points to a valid FND_TABLES row; and extracting OBJECT_CODE and NAME to document rule set coverage. Because OBJECT_CODE is the stable business key, integration scripts and rule exports should reference it rather than the surrogate OBJECT_ID.

Related Objects

The FK metadata identifies the following significant dependencies:

• FND_TABLES — referenced by SO_OBJECTS.TABLE_APPLICATION_ID and SO_OBJECTS.TABLE_NAME; identifies the underlying application table for each object.
• SO_ATTRIBUTES — joins on SO_ATTRIBUTES.OBJECT_ID to OE.SO_OBJECTS.OBJECT_ID, listing the attributes available for each object.
• SO_ATTRIBUTES (REPRESENTED_OBJECT_ID) — a second relationship from SO_ATTRIBUTES back to SO_OBJECTS, supporting attributes that represent another object.
• SO_SECURITY_RULES — joins on SO_SECURITY_RULES.OBJECT_ID to OE.SO_OBJECTS.OBJECT_ID, defining the security rules applied to each object.

Together, SO_OBJECTS, SO_ATTRIBUTES, and SO_SECURITY_RULES form the core metadata triad underpinning Order Management security and standard value rule sets.