Results for “hr_user_acct_bk2”

26 results




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

Overview

APPS.HR_USER_ACCT_BK2 is a PL/SQL package body belonging to the Oracle HRMS API Hook pre-processor layer within the Oracle E-Business Suite. Its header comment block indicates that the source file, hrusrapi.pkb, was code-generated by the Oracle HRMS API Hook Pre-processor and that the body itself was created on 2009/03/30. The package is classified under the API classification "OTHER" in the ETRM metadata for release 12.2.2, and it is owned by the APPS schema. The "BK2" suffix in the object name is significant: in Oracle HRMS API Hook architecture, "BK" denotes a "Before" (pre-processing) hook body, and the numeric suffix identifies a specific generation or layer of that hook. Consequently, HR_USER_ACCT_BK2 exists to supply user-defined pre-processing logic that executes immediately before the corresponding user account API performs its principal business validation and DML operations. In its shipped form, the package body deliberately contains no substantive business logic; it consists solely of diagnostic entry and exit markers wrapped in calls to hr_utility.set_location.

Key Procedures and Functions

Two procedures are documented for this package body:

  • UPDATE_USER_ACCT_A — The first hook procedure associated with the user account update operation. It accepts the full set of context parameters required to identify the person, the period of effectiveness, the assignment, the business group, date ranges, the organization structure and version, parent and single organization identifiers, the run type, and an inactivation date. In the delivered body, the procedure only records an entry and exit location via hr_utility.set_location and performs no additional processing.
  • UPDATE_USER_ACCT_B — The second hook procedure for the same user account update operation. It exposes an identical parameter signature to UPDATE_USER_ACCT_A and likewise contains only the entry and exit location markers in the shipped code.

Both procedures are deliberately empty of functional logic and exist as extension points. Customers and implementers may populate them to enforce organization-specific validation or to derive additional values before the corresponding user account API proceeds with its standard processing.

Tables Accessed

The ETRM metadata for HR_USER_ACCT_BK2 does not document any tables referenced through APPS synonyms. This is consistent with the shipped implementation, which contains no SQL statements, no cursor definitions, and no DML operations. The package therefore reads from and writes to no database tables in its delivered form. Any table access would only arise from customizations applied by a customer.

Usage Notes

This package is not intended to be called directly by end users or by application forms. It is invoked implicitly by the Oracle HRMS API framework as part of the pre-processing phase of the user account update operation, at the point where the framework dispatches the "Before" hooks around the core user account logic. The parameters supplied to the procedures are passed by the calling API, which has already resolved the person, assignment, organization structure, and effective dating context. Because the metadata records that the package is referenced by one other package, its execution is driven entirely through that internal dependency rather than through direct invocation.

From a customization perspective, HR_USER_ACCT_BK2 serves as a supported extension point. Developers attaching customer-specific logic should preserve the existing location markers to maintain diagnostic traceability, and should ensure that any added code does not commit transactions, as committing within an API hook can corrupt the transactional integrity of the parent API. Because the body is regenerated by the Oracle HRMS API Hook Pre-processor when patches are applied, customer modifications to the generated package body risk being overwritten; the recommended practice is to place custom logic in a separate, independently versioned package and call it from within this hook.