Search Results g_type_set

Overview

DOM_SECURITY_PVT is a private PL/SQL package in the APPS schema that resolves document security mappings within Oracle E-Business Suite. Its stated purpose, taken from the package header comment, is to "resolve document security mappings based on FND data security." In this context, "DOM" refers to the document management and collaboration layer of EBS, which relies on FND user and responsibility security to determine which users may access specific documents, folders, or repository objects.

The package is classified as PVT (private), meaning it is an internal utility package rather than a public, supported API. Customers and integrators are not expected to call it directly; it supports higher-level document management logic that must translate FND security constructs into document-level authorization decisions. A key part of this translation involves integrating with Oracle Internet Directory (OID), since user identity in the document management subsystem is frequently represented by the OID nickname rather than the native FND user name.

The source carries a version header of 120.5 dated 2006/08/17, indicating the package is long-established and stable across the 12.1.1 and 12.2.2 releases. Because it is private and referenced by zero other documented packages, its footprint in the ETRM metadata is limited, but its role in bridging FND security and document security remains the central business function.

Key Procedures and Functions

Two documented entry points are exposed, both concerned with resolving OID user identities. Neither is described with a published parameter list here, so only their purpose is characterized.

• GET_OID_USER — A function that accepts a user name and returns the corresponding OID nickname. It obtains the FND user record through the FND OID utility layer, extracts the associated user GUID, and resolves that GUID to an OID nickname. When any error occurs, the function suppresses the exception and returns NULL, so callers must treat a NULL result as "identity could not be resolved" rather than as a hard failure.
• GET_OID_USERS — A bulk variant of the preceding function. It accepts a collection of user names and returns a parallel collection of OID nicknames, iterating the input and resolving each name through the same FND OID utility calls. It handles the degenerate case of an empty input collection gracefully.

Both routines depend on FND_OID_UTIL for GUID and nickname lookups. The package also declares the constants G_PKG_NAME, G_LOG_HEAD, G_TYPE_SET, G_TYPE_INSTANCE, and G_TYPE_UNIVERSAL. The presence of G_TYPE_INSTANCE and its siblings in the user's search term "g_type_instance" indicates they are used internally to classify the granularity of a security mapping — set-level, instance-level, or universal — when evaluating document security rules.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

• FND_USER — The core EBS user repository. It supplies the user name and associative identifiers needed to initiate identity resolution.
• PLITBLM — A PL/SQL internal table type utility table, referenced in the package's declaration generated by the EBS PL/SQL table-type mechanism. It supports collection handling used by the bulk routines.

Access is read-only in nature; the package resolves and returns identities and security mappings rather than persisting changes.

Usage Notes

Because DOM_SECURITY_PVT is private, it is invoked by document management forms, concurrent programs, and internal APIs that need to reconcile FND users with their OID counterparts before applying document-level security. Typical call sites are those preparing a list of authorized document viewers or filtering repository content by user identity. Custom code should not call this package directly; integrators should use the supported public document management APIs instead. When debugging document access issues, tracing executions of GET_OID_USER or GET_OID_USERS is useful, but a NULL return should not be interpreted as a definitive authorization denial, since the package deliberately masks all exceptions.