Search Results so_objects




Overview
Explore in AI Chat

Overview

The SO_OBJECTS table is a core metadata repository within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master definition table for business objects that are utilized in configuring and enforcing application security and data validation rules. Its primary role is to define the entities—such as orders, lines, or shipments—upon which security rules and standard value rule sets are built. By centralizing object definitions, it provides a consistent framework for the Order Management system to control data access and automate default value assignments based on complex business logic.

Key Information Stored

The table stores essential metadata that uniquely identifies and describes each configurable object. The critical columns, as indicated by the primary and unique keys, include the OBJECT_ID (the surrogate primary key), the OBJECT_CODE (a unique identifier for the object), and the NAME (another unique descriptive name). A significant structural aspect is its foreign key relationship to FND_TABLES via the TABLE_APPLICATION_ID and TABLE_NAME columns. This relationship ties the abstract security or rule object directly to a physical database table in the application, thereby linking the configuration layer with the operational data layer. Other columns typically include descriptive fields and control attributes that define the object's behavior within the rule engines.

Common Use Cases and Queries

The primary use case for SO_OBJECTS is during the analysis and troubleshooting of Order Management security profiles and standard value rule sets. Administrators and developers query this table to understand the available objects for rule configuration or to diagnose issues where rules are not firing as expected. A common pattern is to join SO_OBJECTS with related rule tables to see all defined rules for a specific object. For example, to list all security rules defined for objects related to the 'OE_ORDER_HEADERS' table, one might use a query such as:

  • SELECT obj.OBJECT_CODE, obj.NAME, sec.RULE_ID FROM OE.SO_OBJECTS obj JOIN OE.SO_SECURITY_RULES sec ON obj.OBJECT_ID = sec.OBJECT_ID WHERE obj.TABLE_NAME = 'OE_ORDER_HEADERS';

Another frequent query is to retrieve the full list of configurable objects for reporting or setup purposes: SELECT OBJECT_ID, OBJECT_CODE, NAME, TABLE_NAME FROM OE.SO_OBJECTS ORDER BY OBJECT_CODE.

Related Objects

SO_OBJECTS maintains integral relationships with several other key tables in the OE schema, forming the backbone of the rules configuration framework. As per the provided metadata:

  • Referenced Table: It references FND_TABLES via foreign key columns (TABLE_APPLICATION_ID, TABLE_NAME).
  • Referencing Tables: It is referenced as a parent table by:
    • SO_ATTRIBUTES via OBJECT_ID. This table defines the specific attributes (columns) of an object that can be used in rules.
    • SO_ATTRIBUTES again via REPRESENTED_OBJECT_ID, for more complex attribute relationships.
    • SO_SECURITY_RULES via OBJECT_ID. This is a direct and critical relationship, as every security rule must be associated with a defined object from this table.

Therefore, SO_OBJECTS sits at the top of a hierarchy, with SO_ATTRIBUTES and SO_SECURITY_RULES being its primary dependent entities.