Search Results g_invalid_setup_exp




Overview
Explore in AI Chat

Overview

FND_SSO_REGISTRATION is an Oracle E-Business Suite internal PL/SQL package owned by the APPS schema and declared with AUTHID CURRENT_USER. Its principal business function is to govern and validate the registration and provisioning relationship between EBS application users and an Oracle Internet Directory (OID) or LDAP-based directory service. In EBS 12.1.1 and 12.2.2, single sign-on and centralized identity management depend on the ability of the EBS middle tier to authenticate against, and optionally write identities into, an external directory. This package encapsulates the logic that determines whether such operations are permitted under the configured provisioning profile (AppsToOID), and it supplies the realm resolution utilities required to translate a user name, GUID, or default configuration into the correct distinguished name (DN) within a custom or default Directory Information Tree (DIT).

The package is classified as OTHER within the ETRM metadata, reflecting that it is an internal framework utility rather than a public application programming interface. It exposes thirteen documented procedures and functions, all oriented toward permission checks and realm resolution, and it raises a dedicated exception, G_INVALID_SETUP_EXP, when an invalid registration configuration is detected.

Key Procedures and Functions

The package provides the following documented routines:

  • IS_OPERATION_ALLOWED — Determines whether the provisioning profile permits a requested directory operation, such as identity add, modify, or delete. FND-side operations are always reported as permitted, while the OID-side result depends on profile configuration. A user name or realm DN may be supplied to target a specific realm.
  • GET_USER_OR_SITE_PROFILE — Retrieves the effective profile value applicable to a given user, falling back to the site-level setting where no user-level value exists.
  • FIND_REALM_INDEX — Locates the index of a realm within the directory search configuration.
  • FIND_REALM — Resolves a realm by name or identifier, returning the corresponding realm entry.
  • GET_REALM_DATA — Returns the full set of data associated with a resolved realm.
  • GET_REALM_ATTRIBUTE — Extracts a single named attribute from a realm definition.
  • GETREALMSEARCHBASELIST — Produces the list of search base distinguished names used when querying realms in the directory.
  • GETUSERREALMINDEX — Returns the realm index associated with a specific user.
  • GETGUIDREALM — Resolves the realm that corresponds to a supplied GUID, supporting global-unique identifier lookups.
  • GETDEFAULTREALM — Returns the default realm when no user name or realm DN is specified.

Tables Accessed

The package references FND_USER via APPS synonyms, consistent with its need to associate EBS application users with directory identities and realm assignments. Directory interaction is performed through DBMS_LDAP, the supplied PL/SQL LDAP interface, and PLITBLM, the PL/SQL table and bulk-processing helper package used for collections. The metadata identifies these three dependencies; the package does not appear to maintain its own dedicated registration table, relying instead on profile options and directory-side configuration.

Usage Notes

FND_SSO_REGISTRATION is invoked by the EBS identity-management framework rather than by end users directly. It is called during user registration and provisioning flows, when EBS synchronizes or validates identities against OID, and when determining whether the AppsToOID provisioning profile authorizes a given directory write. Because two other packages reference it, it functions as a shared dependency within the SSO/identity stack. Custom code should treat these routines as internal, version-sensitive interfaces: they are subject to change between 12.1.1 and 12.2.2, and callers should not assume stable signatures. Sites implementing alumni association registration or similar external forms should not call this package directly; such integrations typically target supported public APIs or interface tables, leaving FND_SSO_REGISTRATION to the internal authentication and directory-provisioning layer.