Results for “process_selected_transaction”

23 results




Overview
Explore in AI Chat

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

Overview

HR_NEW_USER_REG_SS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM taxonomy as an OTHER API. Its name and header comment (hrregwrs.pkh) indicate that it supports the registration of new users within Oracle Human Resources, specifically the workflow-driven processing that converts a self-service or administrative new-user request into a fully created Person and Assignment record. The package header is defined with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the package owner, a characteristic common to HR self-service (SS) packages that are called from workflow and concurrent processing contexts.

The package exposes a small, focused interface intended to be driven by Oracle Workflow. A package-level variable, g_ignore_emp_generation, initialized to 'NO', provides a global switch controlling whether employee number generation is bypassed during processing — a useful control when new users are created in bulk or in integration scenarios where the employee number is supplied externally.

Key Procedures and Functions

  • processNewUserTransaction — The principal entry point. It accepts a workflow item type and item key together with PersonId and AssignmentId parameters passed as IN OUT NOCOPY, and processes a new-user transaction end to end. Because the identifiers are returned to the caller, the procedure is designed to be invoked from a workflow function activity that subsequently uses the created Person and Assignment for downstream steps.
  • process_selected_transaction — A more general driver that processes a specific transaction identified by item type and item key. It exposes control parameters for ignoring warnings, performing validation only, updating object version, supplying an effective date, and naming the API being executed. This makes it suitable for both real processing and pre-validation from forms or custom code.
  • processExemptTransaction — Documented in the ETRM metadata but not present in the visible header excerpt; by convention it handles transactions flagged as exempt, allowing the registration to proceed without the standard validation or approval path.
  • getPPG_KFF_STRUCTCODE — A retrieval function returning the key flexfield structure code associated with a Payroll/People Group (PPG) context, used to resolve the correct flexfield structure during person or assignment creation.

Tables Accessed

  • PER_ALL_PEOPLE_F — The core HR person table; the package creates or validates the person record for the new user.
  • HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS — The HR API transaction framework tables used to record the transaction and its individual processing steps, providing restartability and auditability.
  • HR_ORGANIZATION_INFORMATION — Supplies organization-level attributes (such as business group context) needed to derive defaults for the new user's assignment.
  • FND_ID_FLEX_STRUCTURES — Resolves the key flexfield structure, consistent with the getPPG_KFF_STRUCTCODE function.
  • FND_SESSIONS — Provides session context information for the processing run.

Usage Notes

The package is not intended for direct ad hoc invocation. It is typically called from Oracle Workflow processes that orchestrate new-user registration in HR self-service, and the ETRM metadata records that it is referenced by eleven other packages, confirming its role as a shared utility within the HR registration flow. The presence of HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS indicates the package participates in the standard HR API transaction mechanism, so callers should respect transaction commit boundaries and error-handling conventions. Parameters such as p_ignore_warnings, p_validate, and p_update_object_version allow callers to run the logic in validation-only mode before committing, which is the recommended pattern when integrating from custom forms or concurrent programs. Customizations should call the package rather than manipulating the underlying HR tables directly, thereby preserving the transaction-step audit trail and any business rules enforced by the API layer.