Search Results fnd_objects_pkg




Overview
Explore in AI Chat

Overview

FND_OBJECTS_PKG is a low-level Oracle Application Object Library (FND) maintenance package that owns the DML and translation logic for the FND_OBJECTS entity — the registry of application objects (forms, reports, functions, menus, and other registered components) that Oracle E-Business Suite uses for security, menu construction, and object registration. The package is classified as OTHER in the ETRM metadata, indicating that it is not published as a supported public API but serves an internal, framework-level role.

In both 12.1.1 and 12.2.2 the object resides in the APPS schema and reports a VALID status. Its documented dependency footprint is deliberately narrow: it references only SYS.STANDARD and is referenced by no other packages, confirming that it is a leaf utility invoked directly by the Oracle Forms-based maintenance screens rather than a building block consumed elsewhere. Business users encounter its effects indirectly whenever object definitions are created, changed, or translated through the standard application setup windows; functional consultants rarely call it by name.

Key Procedures and Functions

ETRM documents nine procedures and functions. They fall into four functional groups:

  • INSERT_ROW — Creates a new object definition in the base table, including its base-language translation row.
  • UPDATE_ROW — Applies changes to an existing object definition record.
  • DELETE_ROW — Removes an object definition and its dependent translation rows.
  • LOCK_ROW — Acquires a row-level lock so that concurrent maintenance sessions cannot overwrite each other, supporting the Forms "select for update" pattern.
  • LOAD_ROW — Loads a complete object definition, typically used by seed data and upgrade scripts that must materialize a row in a defined state.
  • TRANSLATE_ROW — Writes translated user-facing attributes (object name and description) into the translation table for a given language.
  • ADD_LANGUAGE — Creates missing translation rows for a newly installed or activated language so that every object has a row in FND_OBJECTS_TL.

The remaining documented entry points follow the same naming and purpose conventions of the FND table-handler family. No parameter lists are published in the ETRM extract; callers should inspect the package specification in the target instance before invoking any procedure directly.

Tables Accessed

The package operates against the standard FND_OBJECTS entity group through APPS synonyms:

  • FND_OBJECTS — the base table holding non-translatable object attributes.
  • FND_OBJECTS_TL — the translation table holding language-specific object name and description; maintained by TRANSLATE_ROW and ADD_LANGUAGE.
  • FND_OBJECTS_S — the sequence used to generate primary keys during INSERT_ROW and LOAD_ROW.
  • FND_APPLICATION — confirms the owning application of the object, validating the product short name supplied by the caller.
  • FND_LANGUAGES — determines installed and active languages, driving ADD_LANGUAGE and default translation behavior.
  • DUAL — used for simple SELECT ... FROM DUAL expressions.

Usage Notes

FND_OBJECTS_PKG is invoked primarily by the Oracle Forms-based object registration and maintenance windows shipped with Application Object Library. It is also exercised by seed data loaders and patching routines that register new objects during installation or upgrade, and by language installation scripts that populate translations for newly activated languages.

Because the package is classified OTHER rather than PUBLIC, it is not a supported integration point. Custom code should prefer querying FND_OBJECTS and FND_OBJECTS_TL directly for read access and should avoid direct DML through this package in production, since inserts bypass the layer of validation applied by the Forms UI. Any direct invocation should be limited to controlled environments and preceded by review of the current package specification, as internal behavior is not guaranteed across point releases.