Results for “set_user_acct_details”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.PER_RI_CREATE_CRP_EMPLOYEE package body is an Oracle E-Business Suite database object that supports the creation of employee records within the context of a CRP (Conference Room Pilot) or rapid implementation environment. The prefix "RI" denotes "Rapid Implementation," a methodology and supporting toolset used during EBS deployments to accelerate the loading of foundational Human Resources data such as employees, person addresses, user accounts, and salary proposals. This package acts as an orchestration and staging layer that bridges batch-driven data pump operations with the underlying HR Data Pump (HRDPP) and HR Data Pump View (HRDPV) APIs.
The package is classified under the APPS schema with a status of VALID and is categorized as an OTHER API type within the ETRM documentation for release 12.2.2. Its primary architectural role is to assemble and normalize input data into batch lines, then invoke the appropriate HRDPP procedures that perform the actual inserts and updates against the HR schema.
Key Procedures and Functions
- INSERT_BATCH_LINES — This procedure is responsible for populating batch line records that feed the HR Data Pump processing framework. It writes into the HR_PUMP_BATCH_LINES staging structure, preparing rows that subsequent HRDPP entity-specific procedures consume during the employee creation cycle.
- SET_USER_ACCT_DETAILS — This procedure manages the population or initialization of user account detail attributes associated with the employee being created. It complements the account creation logic exposed through HRDPP_CREATE_USER_ACCT and HR_USER_ACCT_UTILITY, ensuring that the user account context is correctly established before or during employee record generation.
Both procedures are documented as the sole exposed units in the package body. No parameter lists are documented in the ETRM metadata, and none are inferred here.
Tables Accessed
- FND_RESPONSIBILITY — A read against the standard Oracle Application Object Library responsibility definition table. It is referenced, most likely, to resolve or validate responsibility assignments used during user account provisioning.
- HR_PUMP_BATCH_LINES — The core staging table for HR Data Pump operations. The package writes batch line entries here via INSERT_BATCH_LINES to queue records for downstream processing.
- DBMS_UTILITY — Although technically a PL/SQL-supplied package rather than a table, the dependency listing includes DBMS_UTILITY under both PUBLIC and SYS. This dependency is directly relevant to the user's search term "dbms_utility." DBMS_UTILITY provides a range of low-level server utilities, most commonly used here for purposes such as formatted error stack retrieval (FORMAT_ERROR_STACK, FORMAT_ERROR_BACKTRACE) or name resolution helpers, which is a common defensive coding pattern in APPS APIs that must report errors clearly during batch loading.
- DUAL — The standard SYS-provided single-row pseudo-table, typically referenced for scalar evaluations or to obtain system values such as SYSDATE or sequence-next-value lookups.
The package also references, by dependency, the HRDPP_CREATE_EMPLOYEE, HRDPP_CREATE_PERSON_ADDRESS, HRDPP_CREATE_USER_ACCT, HRDPP_UPDATE_EMP_ASG, HRDPP_UPDATE_EMP_ASG_CRITERIA, HRDPP_UPLOAD_SALARY_PROPOSAL, HRDPV_CREATE_EMPLOYEE, and HRDPV_CREATE_PERSON_ADDRESS APIs, which it drives to perform the substantive HR operations. Per ETRM, the package is not referenced by any other database object.
Usage Notes
PER_RI_CREATE_CRP_EMPLOYEE is invoked within the Rapid Implementation framework rather than through standard end-user forms. It is typically called from concurrent programs or batch drivers that load employee data from staging tables populated by Rapid Implementation spreadsheets or interface files. Administrators running an EBS implementation or re-implementation in releases 12.1.1 or 12.2.2 would trigger the associated Rapid Implementation concurrent process, which in turn calls this package to stage batch lines and dispatch to the HRDPP creation APIs.
Because the package depends on DBMS_UTILITY and DUAL, custom extensions that mimic or wrap this package should also anticipate DBMS-specific error handling. Direct invocation from custom PL/SQL is possible but is generally discouraged; implementations should use the supported Rapid Implementation concurrent programs to preserve data integrity across the employee, address, assignment, and user account entities processed by HRDPP.