Results for “update_user_acct_a”

14 results




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

Overview

APPS.HR_USER_ACCT_BK2 is a private API package within the Oracle E-Business Suite Human Resources (HR) module, delivered as part of the application's seeded database objects. The package encapsulates the server-side logic that supports the deactivation of Oracle Applications user accounts belonging to terminated employees. Its header declaration carries the AUTHID CURRENT_USER clause, meaning that the package executes with the privileges of the invoking schema rather than the definer, which is the standard convention for Oracle EBS API packages that are called from within a session context carrying the appropriate HR security profile.

The package is designated in the ETRM metadata with an API classification of Other, reflecting that it is an internal business-layer implementation rather than a formally published, externally callable API. The _BK2 suffix follows the EBS naming convention for a "backup" or secondary generation of a package body, typically created when a public synonym or wrapper package (such as HR_USER_ACCT_API) delegates the real work to the _BK2 implementation. The documented purpose is narrow and specific: the update API is strictly used for inactivating the user account of a terminated person. The calling API does not gather any information from the user hook program, meaning the termination logic is self-contained and deterministic.

Key Procedures and Functions

The ETRM metadata documents two procedures in this package:

  • UPDATE_USER_ACCT_B — the "before" or business-logic stub. In Oracle EBS API design, the _B suffix denotes the procedure that performs the core validation and business rules. Here it carries the detailed comments in the package header explaining exactly how the caller must pass person and assignment context.
  • UPDATE_USER_ACCT_A — the "after" or wrapper procedure. The _A convention denotes a procedure that wraps the _B logic with audit initialization and row-level locking, typically through HR_API utility calls. It is the entry point most commonly invoked by the calling API layer.

No parameter lists are documented in the metadata excerpt, and none should be inferred. The header notes describe the semantic contract of three parameter families, however. The first is p_person_id, p_per_effective_start_date, and p_per_effective_end_date, which together uniquely retrieve a person record from PER_ALL_PEOPLE_F at the moment the person type becomes EX_EMP. The second family is p_assignment_id, p_asg_effective_start_date, and p_asg_effective_end_date, used to retrieve the assignment record from PER_ALL_ASSIGNMENTS_F when the assignment status type becomes TERM_ASSIGN. The documentation explicitly instructs that date comparisons use the "=" operator, and provides a worked example: for a termination dated 31-Jan-2000, the effective start date parameter carries 01-Feb-2000, the date the person becomes an ex-employee.

Tables Accessed

The package works against the core HR date-tracked tables through APPS synonyms:

  • PER_ALL_PEOPLE_F — read to resolve the person record at the effective date interval where the person type transitions to EX_EMP. This determines whether a user account should be inactivated.
  • PER_ALL_ASSIGNMENTS_F — read to resolve the assignment at the interval where the assignment status becomes TERM_ASSIGN, providing the assignment-level termination context.

Although the excerpt does not enumerate write targets, the business purpose of inactivating a user account implies that the procedure ultimately writes to the FND_USER table (or invokes the corresponding FND user-account API) to set the account to inactive for the person's associated user name. Consumers of this package should validate this against their specific 12.1.1 or 12.2.2 installation, as the ETRM table list for this object is truncated.

Usage Notes

HR_USER_ACCT_BK2 is not intended for direct invocation by end users or by arbitrary custom code. It is invoked from within the HR termination processing flow, most commonly from the calling public API package when an employee's termination is processed through the Person/Assignment termination forms or the associated concurrent programs. In a typical EBS 12.1.1 / 12.2.2 deployment, the invocation occurs when the system detects that the person's type has become EX_EMP and the assignment status has become TERM_ASSIGN. ETRM records show the package is referenced by one other package, confirming that it functions as a lower-level implementation detail behind a wrapper.

Because the package is defined with AUTHID CURRENT_USER, the executing session must have the appropriate HR and FND privileges. The metadata emphasizes that the caller must pass the person and assignment effective date ranges together with the respective IDs, and that the dates must be matched using equality, not a range predicate, against the date-tracked tables. The parameter values must reflect the date on which the person becomes an ex-employee (the day after termination), not the termination date itself. Customizations that bypass these rules will either fail the internal query or inactivate the wrong user account. Given the package's date of last header modification (2008), its logic is stable across both 12.1.1 and 12.2.2, though the surrounding FND user model and password-management features evolved between those releases.