Results for “validate_profile_opt_value”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_USER_ACCT_INTERNAL is an internal PL/SQL package owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It provides the low-level implementation layer behind the public HR_USER_ACCT_API package, which is the programmatic interface used to provision and maintain Oracle EBS user accounts and their associated security constructs. Specifically, the package encapsulates the DML and validation logic required to create and update FND_USER records, FND_RESPONSIBILITY definitions, responsibility-to-user assignments, security profile assignments, and profile option values, together with the derived security artifacts such as function security exclusion rules and responsibility-level profile values.

The package name signals its scope: "HR_USER" identifies the user-provisioning domain, while "ACCT" and "INTERNAL" indicate that it is a private, implementation-facing component rather than a supported public API. It is referenced by HR_USER_ACCT_API, confirming the layered design in which the public API performs parameter validation and orchestration while HR_USER_ACCT_INTERNAL performs the table-level work. It also references HR_USER_ACCT_UTILITY and HR_API, indicating reuse of shared helper routines and the Oracle HRMS business-process framework. The object's API classification is OTHER, consistent with an internal-only package.

Key Procedures and Functions

The documented 12.2.2 metadata lists twelve procedures and functions, which fall into three functional groups.

The presence of paired CREATE_/UPDATE_ procedures for users, responsibility assignments, and security profile assignments reflects a full lifecycle model in which provisioning and subsequent modification are handled by distinct entry points.

Tables Accessed

The package operates across two schema domains. Oracle Application Object Library tables supply identity, menu, and responsibility metadata: FND_USER, FND_RESPONSIBILITY and its translation table FND_RESPONSIBILITY_TL, FND_USER_RESP_GROUPS, FND_RESP_FUNCTIONS, FND_MENUS, FND_REQUEST_GROUPS, FND_SECURITY_GROUPS, FND_DATA_GROUPS, FND_DATA_GROUPS_STANDARD_VIEW, FND_APPLICATION, FND_FORM_FUNCTIONS, FND_LANGUAGES, and the profile option tables FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES. These are read to resolve valid applications, menus, request groups, function definitions, and language settings, and written to persist the resulting user, responsibility, and profile records.

Oracle HRMS tables supply the security model: PER_SECURITY_PROFILES holds the security profile definitions, and PER_SEC_PROFILE_ASSIGNMENTS records assignments of those profiles to users and responsibilities. HR_API and STANDARD (HR_USER_ACCT_UTILITY) are referenced for shared HRMS routines and standard utilities. The derived views and utility references confirm that validation logic and profile-value derivation are delegated rather than duplicated inline.

Usage Notes

HR_USER_ACCT_INTERNAL is not intended for direct invocation by customer code. Because it bypasses the public API's parameter validation and audit behavior, direct calls risk inconsistent user or responsibility records and are unsupported. It is most appropriately reached through HR_USER_ACCT_API, which is in turn invoked by administrative forms, user-provisioning concurrent programs, and integration flows that onboard users into Oracle EBS with correctly wired responsibilities, security profiles, and profile option values.

Typical triggers include bulk user provisioning during implementations, creation of responsibilities as part of role definition, and synchronization of security profile assignments when organizational access changes. In Oracle EBS 12.1.1, user and responsibility data reside primarily in the FND tables, which the package addresses directly. In 12.2.2 and later, responsibility definitions are defined in the FND tables and then published to the run-time enterprise repository by the RUN form of the Applications Administration responsibility, and this publication step is a prerequisite before newly created responsibilities become usable for navigation. Both the transaction and the publishing step should be completed before a provisioned user attempts to log in. Because the package references HR_API business-process routines, provisioning operations may be subject to HRMS business-group context and security, and callers should ensure the correct business group is initialized. Custom development should treat the package as read-only reference and invoke the supported HR_USER_ACCT_API surface instead.