Search Results secure_object




Overview
Explore in AI Chat

Overview

GL_DEFAS_ACCESS_DETAILS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Definition Access Set feature set in Oracle General Ledger. A Definition Access Set (DEFAS) is the mechanism by which an administrator grants or restricts user access to specific General Ledger definitions, such as account structures, budgets, recurring journals, and other setup objects. This package provides the server-side routines that populate and maintain the GL_DEFAS_ACCESS_DETAILS records, which represent the individual object-level access controls attached to a Definition Access Set.

The package is declared with AUTHID CURRENT_USER, meaning that its unqualified database references resolve against the privileges of the invoking user rather than those of the APPS owner. The package is classified as an OTHER API in ETRM, and it is referenced by three other packages, indicating that it is a supporting utility layer rather than an end-user facing interface. Its primary internal consumer is the normalization view GL_DEFAS_NORM_ASSIGN_V, for which it supplies record-group query components and the routines needed to resolve object type, name, and key values. In Oracle EBS 12.1.1 and 12.2.2 the package ships in the standard APPS installation and is used mainly by the iSetup migration framework and by the Definition Access Set administration forms.

Key Procedures and Functions

  • GET_QUERY_COMPONENT — Returns the parameters required to construct the record group query against the normalization view, including the id, name, and description columns, the WHERE clause, and the table name.
  • GET_OBJECT_NAME — Resolves an object name from a supplied object type and object key.
  • GET_OBJECT_KEY — Resolves an object key from an object type and object name; documented as being called by the iSetup API.
  • SECURE_OBJECT — Applies security to an object, given its type and key. This is the routine that the user search term "secure_object" refers to. It is documented as being invoked from the API layer to enforce the access set definition against a specific GL object.
  • INSERT_ROW — Inserts a definition access detail record, capturing the definition access set id, object type, object key, the view, use, and modify access flags, and the user and login identifiers.
  • UPDATE_ROW — Modifies an existing definition access detail record.
  • LOCK_ROW — Acquires a row-level lock prior to an update or delete, supporting the standard EBS optimistic locking convention.
  • DELETE_ROW — Removes a definition access detail record.
  • CHECK_UNIQUE_NAME — Validates uniqueness constraints, typically before an insert or rename, to prevent duplicate access detail entries.
  • SUBMIT_CONC_REQUEST — Submits a concurrent request, allowing access detail processing to be executed through the standard concurrent manager framework rather than interactively.

Tables Accessed

The package operates against two documented tables through APPS synonyms. GL_DEFAS_ACCESS_SETS is the header table holding Definition Access Set definitions and is used for validation of the owning set during insert, update, and security operations. GL_DEFAS_ACCESS_DETAILS, referenced through GL_DEFAS_ASSIGNMENTS, stores the individual object-level access rows that the INSERT_ROW, UPDATE_ROW, DELETE_ROW, and SECURE_OBJECT routines create and maintain. The package also references DBMS_SQL, indicating that GET_QUERY_COMPONENT or related logic builds dynamic SQL statements, most likely to assemble the record-group query used by the Definition Access Set form.

Usage Notes

GL_DEFAS_ACCESS_DETAILS_PKG is not intended for direct invocation by end users. It is called by the Definition Access Set administration form at runtime, where GET_QUERY_COMPONENT drives the object selection list and INSERT_ROW, UPDATE_ROW, and DELETE_ROW persist user changes. The SECURE_OBJECT routine is invoked from the API layer when access must be programmatically enforced against a definition. GET_OBJECT_KEY and GET_OBJECT_NAME are consumed by the iSetup migration API to translate between the human-readable object identifiers used in setup data extracts and the internal keys stored in the details table. Because the package is referenced by three other packages, changes to its signature should be assessed against those dependents before patching. In 12.2.2 the package remains consistent with its 12.1.1 form, with the header comment indicating a shipped version chain managed under standard Oracle source control.