Results for “per_get_asg_pos”

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

Overview

PER_GET_ASG_POS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema, classified under the ETRM metadata model as an "OTHER" API rather than a formal public interface. Its name—an abbreviation of "get assignment position"—signals its core business purpose: deriving assignment-related date information, most notably the effective start and end dates associated with a worker's assignment record. Rather than serving as a transactional API that creates or updates HR data, PER_GET_ASG_POS functions as a utility or helper package that other database objects call to resolve assignment positioning logic.

In Oracle EBS Release 12.1.1 and 12.2.2, this package occupies a supporting role within the Oracle Human Resources (PER) schema objects. Assignment positioning is fundamental to HRMS because virtually all date-effective queries against assignments depend on correctly determining when an assignment becomes active and when it ceases—or is projected to cease—being effective. The package's status is documented as VALID, confirming it is a compiled, functioning object within the APPS schema at the time the ETRM metadata was captured.

Key Procedures and Functions

The ETRM metadata documents two program units within PER_GET_ASG_POS: START_DATE and END_DATE. Consistent with the ETRM convention, these are named without full parameter signatures, and no argument lists are reproduced here.

• START_DATE — Resolves the effective start date for a given assignment context. It provides callers with a single, consistent value representing when the assignment begins to be effective, allowing dependent objects to filter or anchor date-effective queries.
• END_DATE — Resolves the effective end date for an assignment context. This supports logic that requires the termination or end-of-effectiveness boundary of an assignment, such as determining whether an assignment is currently active or has lapsed.

Both routines are described in the metadata as functions/procedures without published parameter documentation; the package exposes no formally documented public API specification, which reinforces its internal-utility classification.

Tables Accessed

Per the documented ETRM metadata, PER_GET_ASG_POS references two tables through APPS synonyms:

• PER_ALL_ASSIGNMENTS_F — The primary date-tracked assignments table in Oracle HRMS. The package reads this table to obtain the effective date boundaries (effective_start_date and effective_end_date) that underlie the START_DATE and END_DATE logic.
• PER_ASSIGNMENT_STATUS_TYPES — The assignment status lookup table. Access to this table indicates that the package's date resolution may be conditioned on assignment status, distinguishing active statuses from inactive or terminated ones when determining an assignment's effective window.

The metadata does not indicate any write operations; the package should be treated as read-only with respect to these tables.

Usage Notes

PER_GET_ASG_POS is referenced by two other APPS packages, PER_ASSIGNMENTS_V9 and PER_ASSIGNMENTS_V11. These objects are assignment views whose versioned naming corresponds to successive datetrack schema generations in EBS R12. Their dependence on PER_GET_ASG_POS confirms that the package is invoked during query execution against assignment views—particularly when consumers request assignment start or end dates.

Typical invocation contexts include:

• Assignment views — PER_ASSIGNMENTS_V9 and PER_ASSIGNMENTS_V11 call the package to supply START_DATE and END_DATE values in view output, meaning any form, report, or concurrent program querying those views may transitively execute this code.
• Custom code — Developers writing PL/SQL that must replicate the standard assignment date-positioning rules may call PER_GET_ASG_POS directly rather than duplicating datetrack logic.
• Forms and concurrent programs — HRMS forms and processes that rely on the assignment views benefit from the package indirectly.

Because the package is classified as OTHER and has no documented public API, it should be regarded as an internal implementation dependency. Customizations that call it directly accept the risk that Oracle may alter its behavior between patch levels, although its documented VALID status in 12.2.2 confirms continued availability.