Search Results per_asg_ins




Overview
Explore in AI Chat

Overview

PER_ASG_INS is a private utility package in the APPS schema whose name reflects its responsibility: performing the low-level insert operations against the Oracle HRMS assignment tables on behalf of the higher-level Assignment APIs. It is not a public or user-facing API, and it is not registered as a business process owner in the EAI/API registry; the ETRM classification for the object is OTHER, which is consistent with an internal helper that exists to centralise the physical INSERT statement and the associated key-resolution logic for PER_ALL_ASSIGNMENTS_F.

Within Oracle E-Business Suite 12.1.1 and 12.2.2, date-effective entities such as assignments require particular care when rows are created. The insertion must populate primary and surrogate keys, set the correct EFFECTIVE_START_DATE/EFFECTIVE_END_DATE values, and preserve the intersection between the base table and its _S shadow table used for secure/dated access. PER_ASG_INS encapsulates these mechanics so that callers such as HR_ASSIGNMENT_INTERNAL and PER_ASG_UPD do not need to reimplement them. Its continued VALID status confirms that the package remains a live dependency of the Assignment API stack in both releases.

Key Procedures and Functions

The ETRM metadata documents four entry points. No parameter signatures are published, and none should be assumed.

  • INS — The primary insert routine. It performs the actual row creation against the assignment tables, taking a fully resolved record from the calling API and committing it as a new dated row.
  • INSERT_DML — The DML-specific implementation layer invoked by INS. Separating the generic insert driver from the concrete DML statement allows the package to be reused where the insert semantics differ slightly, and it aligns with the convention used throughout the HRMS API family.
  • SET_BASE_KEY_VALUE — A key-population helper. It establishes the base (surrogate) key value for the new assignment row, ensuring that the primary key on PER_ALL_ASSIGNMENTS_F and the relationship to the shadow table remain internally consistent.
  • (Fourth documented unit) — The metadata lists four total units; the three above are the operationally significant ones. Any additional unit is likewise internal and supports the same insert contract.

Tables Accessed

  • PER_ALL_ASSIGNMENTS_F — The base date-tracked assignment table. This is the primary target of the insert; every new assignment, whether entered through the Assignment form or generated by a payroll or benefits process, ultimately lands here.
  • PER_ASSIGNMENTS_S — The shadow/secure table associated with the assignment entity. Rows are mirrored here so that secure, date-effective queries and the datetracked view layer resolve correctly.
  • PER_ASG_SHD — Listed as a referenced object in the dependency information. This is the datetrack shadow package/table family used by the assignment datetrack infrastructure; PER_ASG_INS references it when establishing the temporal context of the new row.

The package also depends on SYS.STANDARD, the PL/SQL built-in package, which is a normal dependency for any compiled package body rather than a meaningful data relationship.

Usage Notes

PER_ASG_INS is never invoked directly by end users. It is called by the Assignment API stack, and the ETRM dependency list shows eight referencing packages: BEN_ASSIGNMENT_API, HR_ASSIGNMENT_INTERNAL, HR_ASSIGNMENT_SWI, IRC_OFFERS_API, IRC_OFFERS_SWI, IRC_PARTY_API, PER_ASG_INS itself (recursive reference within the body), PER_ASG_UPD, and PQH_FR_ASSIGNMENT_API.

This caller set shows the breadth of the contract. HR_ASSIGNMENT_INTERNAL and HR_ASSIGNMENT_SWI are the core HRMS assignment APIs; BEN_ASSIGNMENT_API creates benefit-related assignments; the IRC packages support iRecruitment offers and party creation; PQH_FR_ASSIGNMENT_API serves the French payroll/localisation variant. Custom code that needs to create assignments should call HR_ASSIGNMENT_API or HR_ASSIGNMENT_INTERNAL, never PER_ASG_INS, because the higher-level API performs validation, datetrack handling, and business-rule enforcement that the insert helper deliberately omits. Direct use bypasses those checks and risks orphaned or non-datetracked rows in PER_ALL_ASSIGNMENTS_F.