Search Results per_spinal_point_steps




Overview
Explore in AI Chat

Overview

PER_SPINAL_POINT_STEPS is a date-effective (DATETRACK) view owned by the APPS schema in Oracle E-Business Suite, delivered under the PER (Human Resources) product family. It exposes configuration data for spinal point steps, which define the incremental steps that make up a spinal point within a grade spine. In Oracle HRMS compensation and grade structures, a spinal point represents a discrete pay position on a recognised pay spine, and each spinal point is subdivided into ordered steps that carry effective-dated definitions. PER_SPINAL_POINT_STEPS presents the currently effective row for each step, filtering out historical and future-dated versions, so that reports and integrations always read the record in force for the session's effective date.

The view is defined over the PER_SPINAL_POINT_STEPS_F datetrack base table and is classified in ETRM documentation as a date-effective view. Its status is VALID, and it is available in both Oracle EBS 12.1.1 and 12.2.2, where the underlying span columns and validation logic differ only in the standard DATETRACK versioning mechanics common to all date-tracked HRMS entities.

Underlying Base Objects

The documented referenced objects for this view are PER_SPINAL_POINT_STEPS_F (accessed through a synonym) and FND_SESSIONS (also a synonym). PER_SPINAL_POINT_STEPS_F is the physical date-tracked table holding both the "from" and "to" effective date columns (EFFECTIVE_START_DATE and EFFECTIVE_END_DATE). FND_SESSIONS is an application sessions table maintained by Oracle Application Object Library; it stores the effective date associated with each active runtime session, identified by SESSION_ID.

The view selects from PER_SPINAL_POINT_STEPS_F with a WHERE clause that compares the session effective date to the row's start and end dates, returning only the rows where EFFECTIVE_START_DATE is on or before the session effective date and EFFECTIVE_END_DATE is on or after it. This pattern is the standard DATETRACK view construct and is the same approach used by other Human Resources date-effective views, ensuring consistency in how effective-dated grade and spinal point data is surfaced to concurrent programs, forms, and external interfaces.

Key Columns

Common Use Cases and Queries

Typical usages include validating spinal point step configuration during grade spine setup, reporting step sequences alongside spinal points and grades, and extracting data for payroll or compensation interfaces that need the currently effective step definitions. Because the view is date-effective, queries automatically return the version valid for the caller's session effective date, eliminating the need for manual date filtering in most reporting scenarios.

A representative query retrieves the active steps for a business group:

  • SELECT sps.step_id, sps.spinal_point_id, sps.grade_spine_id, sps.sequence, sps.effective_start_date, sps.effective_end_date FROM apps.per_spinal_point_steps sps WHERE sps.business_group_id = :p_business_group_id AND sps.spinal_point_id = :p_spinal_point_id ORDER BY sps.sequence;

To include descriptive flexfield values, add the INFORMATION columns to the select list. Joins to PER_SPINAL_POINTS and PER_GRADE_SPINES on their respective IDs provide the full structural context of each step. For historical analysis, the underlying PER_SPINAL_POINT_STEPS_F base table should be queried instead, since the view masks past and future-dated rows.