Results for “per_spinal_point_steps_f”

50+ results




Overview
Explore in AI Chat

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

Overview

PER_SPINAL_POINT_STEPS_F is a Human Resources (PER) product table in the Oracle E-Business Suite HR schema. It stores the grade steps defined within a specific grade scale (spinal point) together with their incremental order, enabling organizations to model structured pay progression for a grade. Because the table carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns and participates in date-tracked (datetracked) key resolution, it functions as a dated child of the grade scale hierarchy rather than as a standalone entity.

Under a heuristic Data Vault classification derived from its foreign key structure, this object is best modeled as a link. It resolves the many-to-many relationship between grade scales (PER_SPINAL_POINTS) and the organizational business group (HR_ALL_ORGANIZATION_UNITS) within which the steps are defined, while the DATE_TRACKED columns and descriptive attributes behave in satellite fashion.

Key Information Stored

The primary key, PER_SPINAL_POINT_STEPS_F_PK, is a composite surrogate key comprising STEP_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. STEP_ID alone is the unique identifier for the grade step; the date pair provides the datetrack versioning dimension. Notable business-key candidates include STEP_ID combined with the effective dates, and the (SPINAL_POINT_ID, GRADE_SPINE_ID, SEQUENCE, EFFECTIVE_START_DATE) combination used to enforce ordering within a grade scale.

  • STEP_ID — unique identifier for the grade step.
  • SPINAL_POINT_ID — foreign key to PER_SPINAL_POINTS, identifying the grade scale to which the step belongs.
  • GRADE_SPINE_ID — identifier for the grade spine (the pay progression ladder) containing the step.
  • SEQUENCE — the incremental order of the step within the grade scale.
  • BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS, establishing the organization for which the step is defined.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — datetrack validity range; together with STEP_ID they complete the primary key.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program identifiers for row provenance.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Forms/ADF layer.
  • INFORMATION_CATEGORY and INFORMATION1–30 — descriptive flexfield (DFF) attribute columns supporting customer-specific extensions.

Common Use Cases and Queries

Typical scenarios include extracting the ordered list of steps for a grade scale, driving compensation and progression reports, and populating interfaces to payroll or grade-rate engines. A common query pattern returns the current effective version of each step for a given spinal point:

SELECT s.step_id, s.sequence, s.spinal_point_id, s.grade_spine_id
FROM per_spinal_point_steps_f s
WHERE s.spinal_point_id = :p_spinal_point_id
AND TRUNC(SYSDATE) BETWEEN s.effective_start_date AND s.effective_end_date
ORDER BY s.sequence;

Reporting use cases join to PER_SPINAL_POINTS to resolve the grade scale name and to HR_ALL_ORGANIZATION_UNITS to resolve the business group. Date-effective lookups should always filter on the effective dates, while descriptive flexfield value extraction uses FND_DFF APIs against INFORMATION_CATEGORY and the INFORMATIONn columns.

Related Objects

  • PER_SPINAL_POINTS — parent grade scale table; join via SPINAL_POINT_ID.
  • HR_ALL_ORGANIZATION_UNITS — owning business group; join via BUSINESS_GROUP_ID.
  • PER_GRADE_SPINES_F — related grade spine table referenced by GRADE_SPINE_ID.
  • PER_SPINAL_POINT_STEPS — business view over the _F table used by Forms and OAF.
  • FND_FLEX_VALUES / FND_DFF API — sources for the INFORMATION1–30 DFF columns.
  • FND_CONCURRENT_REQUESTS — provenance for REQUEST_ID and program columns.

Because the table is datetracked and protected by the composite PK, DELETE and UPDATE operations must honour the effective-date constraints, and business logic should generally be routed through the PER grade APIs rather than direct DML.