Search Results per_spinal_point_placement_pk

Overview

PER_SPINAL_POINT_PLACEMENTS_F is a date-tracked (datetrack) table in the HR schema of Oracle E-Business Suite, owned by the PER — Human Resources product. It stores the details of assignment placements to a grade step and point, functioning as the subsystem that records where a specific assignment sits within a spinal point structure for a defined effective period. Spinal points are commonly used in public-sector and regulated compensation models where pay progression follows a fixed sequence of grades, steps, and points rather than free-form salary ranges. Because the object is a "_F" (federal/date-tracked) table, every row carries an EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, allowing historical reconstruction of placement decisions over time.

Per the ETRM metadata, the heuristic Data Vault classification is satellite-leaning. This is a modeling suggestion: the table behaves as a satellite that captures descriptive, time-variant attributes surrounding a core business key, rather than acting as a hub (which would hold uniquely identifiable entities) or a link (which would resolve many-to-many relationships). The presence of foreign keys to HR_ALL_ORGANIZATION_UNITS and PER_PARENT_SPINES reinforces this reading, since satellites typically attach to hubs via such references.

Key Information Stored

The table is physically documented with 51 columns in ETRM 12.2.2. The most significant columns are:

• PLACEMENT_ID — Surrogate identifier for the placement record; part of the primary key.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked boundaries that define the validity window of each placement; together with PLACEMENT_ID they form the compound primary key PER_SPINAL_POINT_PLACEMENT_PK.
• BUSINESS_GROUP_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the business group that owns the placement.
• ASSIGNMENT_ID — The assignment to which the spinal point placement applies.
• STEP_ID — The grade step associated with the placement.
• PARENT_SPINE_ID — Foreign key to PER_PARENT_SPINES, linking the placement to its parent spine definition.
• AUTO_INCREMENT_FLAG — Indicates whether the placement was generated automatically through incremental progression.
• INCREMENT_NUMBER — Tracks the increment sequence applied within the spinal structure.
• REASON — Free-text or coded justification for the placement.
• REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — Standard concurrent program audit columns capturing the process that created or modified the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, OBJECT_VERSION_NUMBER — Standard WHO and optimistic-locking columns.
• INFORMATION1 through INFORMATION30 and INFORMATION_CATEGORY — Descriptive flexfield (DFF) attribute columns supporting client-specific extensions.

The unique index (business-key candidate) is PER_SPINAL_POINT_PLACEMENT_PK on (PLACEMENT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE), distinguishing the surrogate identity from the effective-dated business key.

Common Use Cases and Queries

Typical usage includes auditing assignment pay progression, reporting on current versus historical spinal placements, and reconciling automatic increments against manual overrides. A common query pattern retrieves the currently effective placement for an assignment:

• Join PER_SPINAL_POINT_PLACEMENTS_F to PER_ASSIGNMENTS_F on ASSIGNMENT_ID where SYSDATE is between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
• Filter by BUSINESS_GROUP_ID to isolate a single enterprise or legislative group.
• Aggregate INCREMENT_NUMBER to measure progression velocity across a population.
• Interrogate INFORMATION1–INFORMATION30 for client-specific DFF reporting.

Reporting extracts frequently feed payroll and compensation analytics, where the effective-dated nature requires careful use of the primary key window to avoid double counting.

Related Objects

• HR_ALL_ORGANIZATION_UNITS — joined on BUSINESS_GROUP_ID; supplies the business group context.
• PER_PARENT_SPINES — joined on PARENT_SPINE_ID; defines the parent spinal structure.
• PER_ASSIGNMENTS_F — joined on ASSIGNMENT_ID; the assignment being placed.
• PER_SPINAL_POINT_PLACEMENT_PK — the primary key constraint and unique index.
• PER_GRADE_STEPS / PER_GRADES — referenced via STEP_ID to resolve grade and step definitions.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the concurrent process that created or updated each row.