Search Results create_user

Overview

IBE_USER_PVT is a private (PVT-classified) PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It functions as the iStore (IBE) user provisioning layer, providing the procedures that create, maintain, and revoke Oracle E-Business Suite application user accounts on behalf of the iStore self-service storefront and related customer-facing flows. Rather than calling the underlying Oracle Application Object Library user maintenance APIs directly, iStore components invoke IBE_USER_PVT, which encapsulates the orchestration logic required to keep FND_USER records synchronized with iStore person, organization, and contact data.

The package is declared AUTHID CURRENT_USER, meaning its unqualified references resolve in the schema of the calling session and its execution privileges are those of the invoker. The header ships with the version identifier $Header: IBEVUSRS.pls 120.3 2005/08/29 09:26:24 appldev ship $, and the package body defines package-level constants and sentinel values (G_PKG_NAME, null_char, null_date, null_number) used to represent missing or unspecified values in API calls.

The metadata records that IBE_USER_PVT is referenced by one other package, confirming its role as an internal building block within the iStore code stack rather than a standalone public interface.

Key Procedures and Functions

The documented interface exposes four procedures: CREATE_USER, UPDATE_USER, UPDATE_ASSIGNMENT, and TESTUSERNAME.

• Create_User — Creates an FND application user. It is described as being called by Create_Person and Create_Organization within iStore, and it delegates the actual user creation to FND_USER_PKG.Create_User. It accepts the user name, password, start and end dates, password date, e-mail address, and customer identifier as inputs, and returns the newly generated user identifier through an OUT parameter.
• Update_User — Updates the FND user and its contact mapping. It is invoked from User Management when a new contact must be mapped to an existing user name, and calls FND_USER_PKG.UpdateUser. Its inputs include user name, password, start and end dates, the old password, and a party identifier.
• Update_Assignment — Used when sites are revoked from a user through User Management. It calls FND_USER_RESP_GROUPS_API and end-dates the affected responsibility assignment, thereby removing the user's access to the revoked site.
• TESTUSERNAME — A validation routine used within the iStore registration flow to test whether a proposed user name is acceptable or already in use before a user record is created.

Tables Accessed

The documented table reference for this package is FND_USER, accessed through APPS synonyms. FND_USER is the Oracle Applications core user repository, holding user names, encrypted passwords, password dates, effective start and end dates, e-mail addresses, and the customer and party linkage columns that associate an application user with a trading community entity. CREATE_USER and UPDATE_USER write to this table indirectly through FND_USER_PKG, while UPDATE_ASSIGNMENT affects responsibility assignments held in the FND user responsibility tables via FND_USER_RESP_GROUPS_API. TESTUSERNAME relies on the same user repository to detect duplicate or invalid user names.

Usage Notes

IBE_USER_PVT is an internal iStore API and is not intended as a general-purpose integration point. It is invoked primarily by iStore person and organization creation logic and by the iStore User Management screens, and it is referenced programmatically by one other iStore package. Because it is classified PVT and is not registered as a public API, customizations and extensions should call it only when replicating native iStore behavior; for general purpose user provisioning in EBS 12.1.1 and 12.2.2, FND_USER_PKG remains the supported public interface. Callers should note the invoker's-rights semantics and the requirement that the invoking schema be able to resolve the APPS synonyms for FND_USER.