Results for “hr_new_user_reg_ss”

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

Overview

HR_NEW_USER_REG_SS is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, shipped in valid status for both 12.1.1 and 12.2.2. The suffix "_SS" denotes a supplemental (non-public) package: it is an internal implementation container rather than a published, supported API callable directly by customers. Its business purpose is to support the self-service user registration flow within Oracle Human Resources / self-service HR, orchestrating the creation and processing of API transactions that register a new user, generate the corresponding person record, and manage transaction steps in the HR transaction framework.

The package is classified as OTHER in the ETRM API classification scheme, indicating it is not one of the major documented public APIs (such as HR_EMPLOYEE_API or HR_PERSON_API) but rather an auxiliary package used by the new-user registration transaction processing. It is not referenced by any database object, confirming its role as a leaf-level implementation unit invoked by higher-level packages and concurrent processes rather than being invoked indirectly through database triggers or views.

Key Procedures and Functions

The ETRM metadata documents four procedures and functions within this package body:

• PROCESSNEWUSERTRANSACTION — The principal entry point for handling a new-user registration transaction. It is responsible for driving the transaction through its processing steps, coordinating with the HR transaction API and the person processing logic.
• PROCESS_SELECTED_TRANSACTION — Processes a specific, already-selected transaction record. This supports scenarios where an existing or queued transaction must be reprocessed or advanced, as opposed to initiating a brand-new registration.
• PROCESSEXEMPTTRANSACTION — Handles the case where a transaction is exempt from normal processing rules. This likely addresses transactions that bypass standard validation or step execution, a common requirement in HR data conversion and self-service flows where certain registrations are flagged as exempt.
• GET_PPG_KFF_STRUCTCODE — A helper function that retrieves the key flexfield structure code for the person/party group (PPG) context. It supplies the descriptive flexfield or key flexfield structure identifier required when validating or building person-related flexfield data during registration.

No parameter lists are documented in the ETRM metadata, and none should be assumed; callers must obtain signatures from the source or the database dictionary.

Tables Accessed

The package references several base and interface tables through APPS synonyms:

• HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS — The core transaction framework tables that store the header and step-level state of each registration transaction processed by the package.
• PER_ALL_PEOPLE_F — The primary person table, read and written as part of creating and validating the new user's person record.
• FND_ID_FLEX_STRUCTURES — Accessed by GET_PPG_KFF_STRUCTCODE to resolve the key flexfield structure for the person/party group.
• FND_SESSIONS — Used to obtain session context, consistent with Oracle EBS standards for recording who performed the transaction.
• HR_ORGANIZATION_INFORMATION — Read for organizational context relevant to the registration, such as business group or organization classification data.

In addition, the dependency listing shows references to HR_TRANSACTION_API, HR_TRANSACTION_SS, HR_PROCESS_PERSON_SS, HR_EMP_ERROR_UTILITY, HR_MESSAGE, HR_GENERAL, HR_UTILITY, FND_MESSAGE, and FND_PROFILE, which supply message handling, profile option lookups, error utilities, and person processing services used throughout the package.

Usage Notes

HR_NEW_USER_REG_SS is an internal package and is not intended for direct invocation by custom code; Oracle does not publish it as a supported API, and its procedures may change between releases. It is typically invoked indirectly by self-service HR registration flows, by concurrent programs that process pending HR API transactions, and by higher-level wrapper packages (the ETRM metadata records it as referenced by eleven other packages). In 12.1.1 and 12.2.2 environments, practitioners encountering this object are usually investigating errors during new-user registration or person creation, where transaction rows in HR_API_TRANSACTIONS fail to progress through their steps. Because it is classified as OTHER and not published, any customization should be routed through supported public APIs such as HR_PERSON_API, HR_EMPLOYEE_API, or the HR_TRANSACTION_API framework rather than through direct calls to this package.