Results for “insert_batch_lines”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.PER_RI_CREATE_CRP_EMPLOYEE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an "OTHER" API within the ETRM repository. Its name indicates its role within the Oracle Human Resources "Rapid Implementation" (RI) toolset, specifically the component responsible for creating CRP (Conference Room Pilot) employee records. In Oracle EBS 12.1.1 and 12.2.2, Rapid Implementation allows implementers to load setup and transactional data — including employees — from spreadsheets into the HRMS tables through a data pump mechanism. This package supports that mechanism by inserting employee-related rows into the pump batch line structures that are later processed to generate the actual PER_ALL_PEOPLE_F and related records.
The package is defined with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the definer, an important security consideration for a package that touches HR data during implementation accelerators.
Key Procedures and Functions
The ETRM metadata documents two procedures/functions for this package:
- INSERT_BATCH_LINES — This is the primary workhorse of the package. It accepts a batch identifier and an extensive set of employee data attributes (hire date, last name, sex, date of birth, email address, employee number, first name, marital status, nationality, national identifier, prior last name, title, work telephone, and numerous descriptive flexfield attributes) and inserts corresponding rows into the HR pump batch line table. It is the entry point through which a caller supplies employee information for eventual pump processing.
- SET_USER_ACCT_DETAILS — This procedure manages the user account details associated with the creation process. The search term "set_user_acct_details" maps directly to this routine. Its purpose is to establish or populate the user account linkage/details required when the CRP employee is created, ensuring that the record is associated with the correct application user and responsibility context.
No parameter lists beyond those visible in the package specification excerpt for INSERT_BATCH_LINES are reproduced here, and the exact signature of SET_USER_ACCT_DETAILS is not enumerated in the metadata.
Tables Accessed
The documented tables referenced through APPS synonyms are:
- HR_PUMP_BATCH_LINES — Receives the employee attribute rows inserted by INSERT_BATCH_LINES. This is the staging structure consumed by the HR data pump to create the actual employee records during Rapid Implementation.
- FND_RESPONSIBILITY — Consulted in connection with user account details, supporting SET_USER_ACCT_DETAILS in resolving responsibility information tied to the created employee/user.
- DBMS_UTILITY — A standard PL/SQL utility package used for internal purposes such as error formatting or stack/line information; not an application table.
- DUAL — The standard single-row dummy table used for expression evaluation and lookups.
Usage Notes
This package is typically invoked within the Oracle HR Rapid Implementation flow, where the Rapid Implementation spreadsheet loader and associated concurrent programs drive the pump process. INSERT_BATCH_LINES is called to stage employee rows into HR_PUMP_BATCH_LINES, and SET_USER_ACCT_DETAILS is called to resolve and set the user account context for those records. It is generally not invoked directly from end-user forms but is invoked by the Rapid Implementation concurrent programs or, in custom integrations, by external code that needs to programmatically stage CRP employee data.
Because the package runs AUTHID CURRENT_USER and references FND_RESPONSIBILITY, callers must execute it under an APPS-connected session with sufficient privileges. The metadata records no dependent packages referencing it, indicating it sits at the lower edge of the dependency chain and is called by the Rapid Implementation infrastructure rather than by other PL/SQL packages. Implementers should restrict its use to controlled setup activities, since it writes directly into pump staging tables.