Results for “ego_fnd_objects_v”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
EGO_FND_OBJECTS_V is a view owned by the APPS schema in Oracle E-Business Suite, defined under the EGO (Advanced Product Catalog) product family. It is documented as VALID in ETRM for both 12.1.1 and 12.2.2. The view consolidates metadata about registered Oracle Forms and database objects into a single denormalized result set, joining the generic object registry in FND_OBJECTS with the EGO-specific extension data in EGO_FND_OBJECTS_EXT. Its purpose is to expose the descriptive attributes (display names, descriptions) of registered application objects together with the EGO-specific attributes (view privilege, name/description lookup SQL, and parent object hierarchy) needed by the Advanced Product Catalog to render object references in the user interface and to resolve which objects may be maintained or selected by users. Because it is a view rather than a table, it carries no storage of its own and reflects the state of its base objects at query time. Developers commonly reach it when tracing how EGO surfaces FND_OBJECTS entries, and the search term "fnd_objects" frequently leads to this view because it is the EGO-facing projection of the FND object dictionary.
Underlying Base Objects
Per the documented view text, EGO_FND_OBJECTS_V is defined over three referenced base objects, all consumed through synonyms in the APPS schema:
- FND_OBJECTS (SYNONYM) — aliased OBJ. Supplies the core object identity and key structure: OBJECT_ID, OBJ_NAME, APPLICATION_ID, DATABASE_OBJECT_NAME, and the PK1–PK5 column names used to build a unique key for the object.
- FND_OBJECTS_TL (SYNONYM) — aliased OBJ_TL. Supplies the translated DISPLAY_NAME and DESCRIPTION. The join restricts rows to the session language via
OBJ_TL.LANGUAGE = USERENV('LANG'). - EGO_FND_OBJECTS_EXT (SYNONYM) — aliased EXT. Supplies EGO-specific attributes: VIEW_PRIVILEGE, NAME_DESC_SELECT_SQL, and PARENT_OBJECT_ID.
The joins are: OBJ.OBJECT_ID = OBJ_TL.OBJECT_ID and OBJ.OBJ_NAME = EXT.OBJECT_NAME. The second join is name-based rather than ID-based, so any registered object lacking a matching EXT row will be filtered out; the view therefore exposes only FND objects that have been registered in the EGO extension table.
Key Columns
- OBJECT_ID — Primary key of the underlying FND_OBJECTS row; uniquely identifies the registered object.
- OBJECT_NAME — The object name from FND_OBJECTS.OBJ_NAME (also the join key to EGO_FND_OBJECTS_EXT).
- APPLICATION_ID — The application owning the object; joins to FND_APPLICATION.
- DATABASE_OBJECT_NAME — The physical database object (table/view) the FND object maps to.
- PK1_COLUMN_NAME … PK5_COLUMN_NAME — Up to five key columns that define the object's unique identifier, used for generic object references.
- DISPLAY_NAME, DESCRIPTION — Language-specific labels sourced from FND_OBJECTS_TL.
- VIEW_PRIVILEGE — EGO-specific privilege controlling visibility/access to the object within Advanced Product Catalog.
- NAME_DESC_SELECT_SQL — A SQL fragment used to resolve a name and description for an object instance at runtime.
- PARENT_OBJECT_ID — Self-referencing EGO attribute establishing object hierarchy.
Common Use Cases and Queries
Typical uses include listing objects available to EGO, identifying the key columns of an object, and tracing parent/child relationships among registered objects.
List all EGO-visible objects for a given application:
SELECT object_name, display_name, database_object_name, view_privilege FROM apps.ego_fnd_objects_v WHERE application_id = :app_id ORDER BY object_name;
Find the key structure and lookup SQL for a specific object:
SELECT object_name, pk1_column_name, pk2_column_name,
name_desc_select_sql, parent_object_id
FROM apps.ego_fnd_objects_v
WHERE object_name = 'EGO_ITEM';
Traverse the hierarchy to find children of a parent object:
SELECT object_name, display_name FROM apps.ego_fnd_objects_v WHERE parent_object_id = :parent_id;
Because the view enforces session-language translation and filters on matching EXT rows, queries should specify the language environment consistently and expect results only for objects registered in the EGO extension table.
-
View: EGO_FND_OBJECTS_V 12.1.1
View contains data from FND_OBJECTS and EGO_FND_OBJECTS_EXT.
APPS.EGO_FND_OBJECTS_V·↳ EGO_FND_OBJECTS_EXT·↳ FND_OBJECTS·↳ FND_OBJECTS_TL·Explore EGO module →
-
View: EGO_FND_OBJECTS_V 12.2.2
View contains data from FND_OBJECTS and EGO_FND_OBJECTS_EXT.
APPS.EGO_FND_OBJECTS_V·↳ EGO_FND_OBJECTS_EXT·↳ FND_OBJECTS·↳ FND_OBJECTS_TL·Explore EGO module →
-
VIEW: APPS.EGO_FND_OBJECTS_V 12.1.1
-
VIEW: APPS.EGO_FND_OBJECTS_V 12.2.2
-
SYNONYM: APPS.FND_OBJECTS_TL 12.1.1
-
SYNONYM: APPS.FND_OBJECTS_TL 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.FND_OBJECTS 12.1.1
-
SYNONYM: APPS.FND_OBJECTS 12.2.2
-
eTRM - EGO Tables and Views 12.1.1
This table is used to store XML Schema Definitions.
-
eTRM - EGO Tables and Views 12.2.2
Interface table for Item Catalog Category header information
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - EGO Tables and Views 12.1.1
This table is used to store XML Schema Definitions.
-
eTRM - EGO Tables and Views 12.2.2
Interface table for Item Catalog Category header information