Results for “update_ru_previous_job”

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

Overview

APPS.PER_RU_PREVIOUS_EMPLOYER is a PL/SQL package body that supports the Russian (RU) localization of Oracle Human Resources within Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to maintain the "previous employer" and "previous job" records that Oracle HRMS stores for employees, applying validations specific to Russian statutory reporting requirements. The package body carries a header indicating version 120.1 (dated 2006/09/20), and the module is classified under ETRM as OTHER, meaning it is an internal supporting package rather than a public, fully supported API. A guard check using hr_utility.chk_product_install('Oracle Human Resources', 'RU') confirms that the logic executes only when the Russian HR localization is installed, which reflects a fix introduced under GSI Bug 5472781. The procedures accept a P_START_DATE and P_END_DATE pair that define the period of interest; these parameters drive the date-overlap cursors used for validation.

Key Procedures and Functions

The documented API exposes four procedures, of which two deal with employers and two with jobs:

• CREATE_RU_PREVIOUS_EMPLOYER — creates a new previous-employer record for a person within a business group, using the supplied start and end dates and an information-category identifier. Before insertion it validates against existing employer and assignment data for date overlaps.
• UPDATE_RU_PREVIOUS_EMPLOYER — modifies an existing previous-employer record, applying the same overlap and business-group/person validation rules.
• CREATE_RU_PREVIOUS_JOB — creates a previous-job record linked to an existing previous-employer entry, ensuring the job's date range does not conflict with existing previous jobs.
• UPDATE_RU_PREVIOUS_JOB — modifies an existing previous-job record, re-validating against overlapping job and employer data.

The body's cursor logic demonstrates that each procedure verifies whether the requested date range overlaps prior employer or job entries, and whether it overlaps current assignment records for the person. Per the source, the comparison uses the four-way BETWEEN pattern so that any partial or full overlap is detected rather than only exact-date matches.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• PER_PREVIOUS_EMPLOYERS — stores prior employer history for a person; queried for date-overlap validation and the target of insert/update operations.
• PER_PREVIOUS_JOBS — stores prior job details associated with a previous employer; joined to PER_PREVIOUS_EMPLOYERS via PREVIOUS_EMPLOYER_ID for overlap checks and maintenance.
• PER_ALL_ASSIGNMENTS_F — provides the person's current assignment records, filtered on business group, person, and non-terminated status, to prevent conflicting previous-employer entries.
• HR_SOFT_CODING_KEYFLEX — joined to assignments (outer join) to inspect key flexfield segments, notably segment2, as part of Russian localization checks.

Usage Notes

The package is referenced by four other packages in the ETRM repository, indicating it is called programmatically rather than executed directly by end users. It is typically invoked from Russian-localized HR forms or localization-specific concurrent processes that capture an employee's prior employment history for statutory reporting. Because the procedures are internal and not classified as a public API, customizations should not call them directly without a full regression assessment. The P_START_DATE and P_END_DATE parameters are central to every call, since all validation cursors depend on them to detect overlaps; callers must supply meaningful dates or the checks may fail to identify existing records.