Results for “create_user_acct”

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

Overview

The APPS.HR_USER_ACCT_API package body is a PL/SQL application programming interface within Oracle E-Business Suite (12.1.1 and 12.2.2) that manages the creation and maintenance of Oracle Applications user accounts from within the Oracle Human Resources (HR) module. Its principal business function is to bridge the HR person record and the Oracle Applications security framework by provisioning a corresponding row in the FND_USER table and associating the appropriate responsibilities, security groups, and profile option values. This enables HR-driven onboarding and account provisioning workflows, ensuring that a newly hired or newly defined employee receives a usable application login without requiring an administrator to manually create the account through the Users form.

The package is classified as an API within the ETRM repository and is owned by the APPS schema. It is documented as a valid object that other packages reference, and it is not itself referenced by any database object, which is consistent with it being an entry-point interface rather than a shared utility.

Key Procedures and Functions

The documented metadata identifies two procedures in this package body:

• CREATE_USER_ACCT — Provisions a new Oracle Applications user account. It populates FND_USER and establishes the associated responsibility assignments, security group membership, and profile option values required for the account to function. This is the primary entry point for converting an HR person into an application user.
• UPDATE_USER_ACCT — Modifies an existing application user account. It updates account attributes, adjusts responsibility and security group assignments, and synchronizes profile option values in response to changes originating in the HR record.

Both procedures delegate shared processing logic to helper packages, notably HR_USER_ACCT_UTILITY, HR_USER_ACCT_INTERNAL, and the concurrent request boundary packages HR_USER_ACCT_BK1 and HR_USER_ACCT_BK2. The internal and utility packages isolate common validation and population logic, while the BK1/BK2 packages support buffered or concurrent invocation of the interface.

Tables Accessed

The package operates against the following documented tables, accessed through APPS synonyms:

• FND_USER — the central Applications user account record created or updated by the API.
• FND_RESPONSIBILITY, FND_RESPONSIBILITY_TL, FND_USER_RESP_GROUPS, and FND_USER_RESP_GROUPS_DIRECT — define and store the responsibility assignments granted to the account.
• FND_SECURITY_GROUPS — determines the security group context under which responsibilities are assigned.
• FND_DATA_GROUPS, FND_MENUS, and FND_REQUEST_GROUPS — supply the menus, data groups, and request group definitions attached to assigned responsibilities.
• FND_PROFILE_OPTION_VALUES — stores profile option settings applied to the user or responsibility combination.
• PER_SEC_PROFILE_ASSIGNMENTS — links the HR security profile to the user account, integrating HR security with Applications security.
• FND_MESSAGE — returns user-facing error and informational messages raised during validation.
• PLITBLM — a standard PL/SQL table type used for internal collections and array processing.

Usage Notes

HR_USER_ACCT_API is typically invoked from HR forms, from concurrent programs that process account provisioning in batch, or from custom PL/SQL code that automates user creation as part of an onboarding or data-conversion process. Because it is a C-callable API rather than a seeded concurrent program itself, it is normally wrapped by customer or Oracle-delivered batch logic. Callers should invoke it within a defined transaction boundary and handle the messages returned through FND_MESSAGE, since account provisioning touches the Applications security model and requires valid responsibility, security group, and profile option configuration to succeed. In 12.1.1 and 12.2.2 the package remains valid and dependent on the FND security tables, so it should be exercised in conjunction with standard HR and System Administrator responsibilities.