Search Results get_url

Overview

HR_AUTH_INT is an integrated authentication and authorization bridge within the Oracle E-Business Suite Human Resources product family. Its principal business function is to construct and resolve the URLs, page references, and credential elements that link Oracle HRMS self-service transactions to the Oracle Authoria benefits decision-support system. Benefits administrators configure mappings between Oracle plans and Authoria content, and the package converts those mappings into runtime navigation targets and authentication tokens that end users can follow directly from the EBS interface.

The package is declared AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking session rather than the APPS schema owner. This design choice permits row-level security policies and HRMS security profiles to filter the underlying person and benefit records according to the responsibility of the caller. It is relevant to both Oracle EBS 12.1.1 and 12.2.2, where the Authoria integration continues to be supported through the same PL/SQL entry points.

Key Procedures and Functions

The package exposes six documented functions, all of which return scalar values to the calling form, JSP, or custom program.

• GET_URL (two overloads) — Returns a fully qualified URL string that directs the user to an Authoria page or plan. One overload accepts the user identifier as a NUMBER, the other as a VARCHAR2, accommodating callers that store the identifier in either datatype. Both accept a provider name, person identifier, a page token, and a primary object reference, which together select the destination content.
• GET_PASSWORD — Derives or retrieves the password value associated with a given person for the external provider handshake. This supports single sign-on style authentication to the Authoria site without requiring the employee to re-enter credentials.
• GET_PAGE — Resolves the target page for a specific learning or benefits assignment context based on the plan-line, plan, and learner-enrollment identifiers supplied by the caller.
• GET_ANCHOR_TAG_SS — Produces a complete HTML anchor tag for the Authoria self-service link, accepting plan, person, plan-name, enrollment, plan-line, plan-URL, and primary-object-context values. Several parameters carry defaults so that callers may omit optional context.
• GET_URL_SS — Returns the raw URL used by the self-service flow, mirroring the parameter set of GET_ANCHOR_TAG_SS but without the surrounding markup. Forms and JSP pages typically use this when they construct their own anchor elements.

Tables Accessed

The package reads from five documented base tables through APPS synonyms:

• HR_AUTHORIA_MAPPINGS — The primary configuration table translating Oracle HRMS plans and programs into Authoria provider identifiers and content keys.
• PER_ALL_PEOPLE_F — Supplies person-level attributes such as employee number and effective-dated assignment information required to authenticate and identify the user.
• BEN_LER_F — Provides learner-enrollment records that determine which benefit plan a person is currently enrolled in, and therefore which Authoria page is appropriate.
• FND_USER — Resolves the EBS application user account associated with the person, linking the FND and HRMS identity models.
• FND_PROFILE_OPTION_VALUES — Supplies site- or responsibility-level profile values such as the Authoria server base URL and integration flags.

Usage Notes

HR_AUTH_INT is typically invoked indirectly rather than directly by end users. Oracle iRecruitment, Advanced Benefits, and self-service Benefits forms call GET_ANCHOR_TAG_SS or GET_URL_SS to render the "Go to Authoria" link on a page, while the target Authoria application calls the URL returned by GET_URL to complete deep links into decision-support content. The package is referenced by at least one other database package, confirming that it functions as a shared integration service rather than a standalone utility.

Because the functions depend on effective-dated person and enrollment data, callers should ensure that the current HRMS security context and effective date are established before invocation. Custom integrations replacing Authoria with another provider can reuse GET_URL as a template but must repoint the mapping and profile lookups accordingly.