Search Results per_spinal_point_placements_s
Overview
PER_SPINAL_PT_PLCMT_PKG is an Oracle EBS Human Resources (PER) package body owned by the APPS schema. It provides the server-side processing logic that supports maintenance of spinal point placements — the records that associate an employee assignment with a specific spinal point and step on a grade spine. Spinal point placement is the mechanism used by public-sector and other grade-structured organizations to determine an employee's position on a pay spine and, by extension, their progression, increment eligibility and associated pay value.
The package operates on the PER_SPINAL_POINT_PLACEMENTS_F base table and the PER_SPINAL_POINT_PLACEMENTS_S (or _S) intersection table, which is the object named in the user's search. This _S table stores the placement records keyed to assignments and spine entities, and the package encapsulates the validation, insert, update, lock and delete operations against it. The API classification is documented as OTHER, indicating that it is an internal supporting package rather than a formally published public API, although its procedures are callable from other PL/SQL units.
Key Procedures and Functions
The ETRM metadata documents ten procedures and functions:
- INSERT_ROW — Creates a new spinal point placement record, deriving defaults and validating the placement against the assignment, spine and point before writing to the placement tables.
- UPDATE_ROW — Modifies an existing placement row, typically after re-validation of grade spine and spinal point data.
- DELETE_ROW — Removes a placement record subject to the deletion validity rules enforced by the package.
- LOCK_ROW — Acquires a row-level lock on the placement record to provide concurrency control during maintenance transactions.
- CHK_EXIST — Verifies whether a placement already exists for the given assignment/spine combination, supporting duplicate prevention.
- POP_FLDS — Populates the derived and display fields required by the placement record, resolving lookups and spine attributes.
- POP_CTRL — Populates control or context information used by the calling form or process, including session and lookup context.
- B_DELETE_VALID — Implements the business rule validation that determines whether a placement may be deleted.
- CHECK_ASS_END — Checks assignment end-date conditions, ensuring placement changes respect effective dating and assignment termination.
- TEST_PATH_TO_PERWSSPP — A diagnostic helper that traces the navigation path to the placement maintenance form (PERWSSPP), used to confirm form-to-package wiring.
Tables Accessed
The package reads and writes PER_SPINAL_POINT_PLACEMENTS_F and PER_SPINAL_POINT_PLACEMENTS_S, the effective-dated placement table and its key/intersection companion. It references PER_SPINAL_POINTS, PER_SPINAL_POINT_STEPS_F, PER_GRADE_SPINES_F and PER_PARENT_SPINES to resolve the spine hierarchy, valid points and steps for a placement. Grade information is validated against PER_GRADES_VL. Assignment context is obtained from PER_ALL_ASSIGNMENTS_F and PER_ASSIGNMENTS_F. FND_LOOKUPS and HR_LOOKUPS provide lookup values, FND_MESSAGE supplies message text, FND_SESSIONS and HR_UTILITY provide session and utility services, BEN_PGM_F relates benefit program applicability, and APP_EXCEPTION and STANDARD are used for error handling and PL/SQL built-ins.
Usage Notes
PER_SPINAL_PT_PLCMT_PKG is not referenced by any database object, confirming it is invoked directly by the Oracle HRMS forms layer responsible for spinal point placement maintenance (PERWSSPP) and by related grade/spine maintenance processes. Custom code may call INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW, CHK_EXIST, POP_FLDS, POP_CTRL, B_DELETE_VALID or CHECK_ASS_END when maintaining placements programmatically, but callers must honour effective dating (DATE_FROM/DATE_TO) and validate against PER_SPINAL_POINT_PLACEMENTS_F and _S. Because the object status is VALID, the compiled body is present and available in the 12.1.1 and 12.2.2 environments. Modifications should be limited to custom wrapper packages that call this API rather than altering the seeded APPS package body.
-
SEQUENCE: HR.PER_SPINAL_POINT_PLACEMENTS_S
12.1.1
owner:HR, object_type:SEQUENCE, object_name:PER_SPINAL_POINT_PLACEMENTS_S, status:VALID,
-
SYNONYM: APPS.PER_SPINAL_POINT_PLACEMENTS_S
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PER_SPINAL_POINT_PLACEMENTS_S, status:VALID,
-
SEQUENCE: HR.PER_SPINAL_POINT_PLACEMENTS_S
12.2.2
owner:HR, object_type:SEQUENCE, object_name:PER_SPINAL_POINT_PLACEMENTS_S, status:VALID,
-
SYNONYM: APPS.PER_SPINAL_POINT_PLACEMENTS_S
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PER_SPINAL_POINT_PLACEMENTS_S, status:VALID,
-
PACKAGE BODY: APPS.PER_SPINAL_PT_PLCMT_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PER_SPINAL_PT_PLCMT_PKG, status:VALID,
-
PACKAGE BODY: APPS.PER_SPINAL_PT_PLCMT_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PER_SPINAL_PT_PLCMT_PKG, status:VALID,
-
PACKAGE BODY: APPS.PER_SPP_INS
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PER_SPP_INS, status:VALID,
-
PACKAGE BODY: APPS.PER_SPP_INS
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PER_SPP_INS, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
APPS.PER_SPP_INS dependencies on PER_SPINAL_POINT_PLACEMENTS_S
12.1.1
-
APPS.PER_SPP_INS dependencies on PER_SPINAL_POINT_PLACEMENTS_S
12.2.2
-
APPS.PER_SPINAL_PT_PLCMT_PKG dependencies on PER_SPINAL_POINT_PLACEMENTS_S
12.2.2
-
APPS.PER_SPINAL_PT_PLCMT_PKG dependencies on PER_SPINAL_POINT_PLACEMENTS_S
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1