Results for “per_spinal_point_steps_x”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PER_SPINAL_POINT_STEPS_X is a date-effective (public) view owned by the APPS schema in Oracle E-Business Suite, registered under the PER — Human Resources product family. It is the "X" view corresponding to the "F" (base) table PER_SPINAL_POINT_STEPS_F. The "_X" suffix in Oracle HRMS naming convention denotes a view that filters rows by effective date so that consumers see only the record version in force at the current point in time. Its definition applies the predicate TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE, meaning the view returns the single effective-dated row valid today for each entity, normalizing date-tracked history into a current-state projection.
Functionally, this view exposes spinal point step definitions — the ordered steps that make up a spinal point / grade spine (collectively, the pay progression structure used in public-sector and other HR setups). It serves as the reporting and integration surface for these records, allowing concurrent programs, Oracle Reports, BI Publisher extracts, and interfaces to query current step data without manually applying date-range logic. The view exists in both EBS 12.1.1 and 12.2.2; the documented ETRM metadata is stated for 12.2.2, with identical structure observed across the release line.
Underlying Base Objects
The view resolves against a single documented base object:
- PER_SPINAL_POINT_STEPS_F (SYNONYM) — the date-tracked base table holding all versioned rows. APPS.PER_SPINAL_POINT_STEPS_X is a straight SELECT over this table, projecting every column and restricting output with the SYSDATE effective-date predicate.
Because the view reads only from the "_F" table and applies no joins, its performance is dominated by the effective-date filter. Standard EBS indexes on STEP_ID and the date-tracking columns (EFFECTIVE_START_DATE/EFFECTIVE_END_DATE) typically support efficient access. As a public view in the APPS schema, it is free of the multi-organization (business group) security enforcement that applies to some HR secured views; callers must supply their own BUSINESS_GROUP_ID filtering where business-group isolation is required.
Key Columns
The view exposes the complete column set of the base table, the most significant being:
- STEP_ID — surrogate primary key uniquely identifying a spinal point step record.
- EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range governing row validity. At runtime the view returns only rows where TODAY falls within this range.
- BUSINESS_GROUP_ID — the enterprise / business group owning the record; essential for cross-business-group segmentation.
- SPINAL_POINT_ID — foreign key to the parent spinal point definition.
- GRADE_SPINE_ID — association to the grade spine structure the step belongs to.
- SEQUENCE — ordering/position of the step within the spinal point progression.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit context identifying the process that last loaded or updated the row.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO columns for change auditing.
- INFORMATION1–INFORMATION30 and INFORMATION_CATEGORY — the DFF (Descriptive Flexfield) segment columns for extensible attribute storage.
Common Use Cases and Queries
Typical scenarios include extracting the current step structure for a spinal point, validating sequence integrity for pay progression, and feeding downstream integrations or interfaces with the effective step set.
- Current steps for a spinal point:
SELECT step_id, spinal_point_id, grade_spine_id, sequence FROM per_spinal_point_steps_x WHERE spinal_point_id = :p_spinal_point_id ORDER BY sequence; - Business-group-scoped listing:
SELECT step_id, sequence FROM per_spinal_point_steps_x WHERE business_group_id = :p_bg_id ORDER BY spinal_point_id, sequence; - Audit / DFF inspection:
SELECT step_id, information_category, information1, information2 FROM per_spinal_point_steps_x WHERE step_id = :p_step_id;
Because the view always reflects "as of today," it is unsuitable for historic point-in-time reporting; queries needing prior or future-dated versions must read the base table PER_SPINAL_POINT_STEPS_F directly and supply explicit date ranges against EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
-
Date-effective view.
APPS.PER_SPINAL_POINT_STEPS_X·↳ PER_SPINAL_POINT_STEPS_F·Explore PER module →
-
Date-effective view.
APPS.PER_SPINAL_POINT_STEPS_X·↳ PER_SPINAL_POINT_STEPS_F·Explore PER module →
-
View: HRFV_GRADE_SCALES 12.1.1
Business view template from which the flexfield view is generated.
APPS.HRFV_GRADE_SCALES·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ PER_GRADES_TL·Explore PER module →
-
VIEW: APPS.HRFV_GRADE_SCALES 12.1.1
-
View: HRFV_GRADE_SCALES 12.2.2
Business view template from which the flexfield view is generated.
APPS.HRFV_GRADE_SCALES·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ PER_GRADES_TL·Explore PER module →
-
VIEW: APPS.HRFV_GRADE_SCALES 12.2.2
-
Business view template from which the flexfield view is generated.
APPS.HRFV_GRD_PLACEMNT_PROG_PT_VALS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ HR_GENERAL·Explore PER module →
-
View: HRFV_GRADE_STEPS 12.2.2
Business view template from which the flexfield view is generated.
APPS.HRFV_GRADE_STEPS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ PER_GRADES_TL·Explore PER module →
-
View: HRFV_GRADE_STEPS 12.1.1
Business view template from which the flexfield view is generated.
APPS.HRFV_GRADE_STEPS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ PER_GRADES_TL·Explore PER module →
-
VIEW: APPS.HRFV_GRADE_STEPS 12.2.2
-
VIEW: APPS.HRFV_GRADE_STEPS 12.1.1
-
Business view template from which the flexfield view is generated.
APPS.HRFV_GRD_PLACEMNT_PROG_PT_VALS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·↳ HR_GENERAL·Explore PER module →
-
VIEW: APPS.HRFV_GRADE_STEPS 12.1.1
-
VIEW: APPS.HRFV_GRADE_SCALES 12.1.1
-
VIEW: APPS.HRFV_GRADE_STEPS 12.2.2
-
VIEW: APPS.HRFV_GRADE_SCALES 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person