Results for “ceiling_step_id”

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

Overview

PER_GRADE_SPINES is a date-effective (dated) view owned by the APPS schema within the PER — Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a reporting and integration layer that exposes grade spine (grade ladder) records as they are valid on the current application session date, rather than returning every historical version of each row. The view is registered in E-Transaction Manager (ETRM) with a VALID status and is classified as a date-effective view, meaning its WHERE clause is driven dynamically by the effective date of the invoking session rather than by a user-supplied parameter.

Because the view resolves "as of today" automatically, it is the object that most forms, concurrent programs, and downstream integrations should query when they need the currently active grade spine definition. Transactions that must reason about historical or future-dated grade spine configurations query the underlying base table instead.

Underlying Base Objects

The view is defined over two documented referenced objects, both accessed through APPS synonyms: PER_GRADE_SPINES_F and FND_SESSIONS. PER_GRADE_SPINES_F is the _F (date-effective) base table that stores grade spine rows together with their EFFECTIVE_START_DATE and EFFECTIVE_END_DATE range and all descriptive and audit attributes. FND_SESSIONS is the standard Oracle Applications session table, and it supplies the effective date used to filter the rows.

The defining query selects all columns from PER_GRADE_SPINES_F and restricts the result set to rows whose effective range contains the session effective date:

• EFFECTIVE_START_DATE <= the session effective date from FND_SESSIONS (matched on USERENV('SESSIONID')).
• EFFECTIVE_END_DATE >= the same session effective date.

This is the canonical Oracle date-effective view pattern: a single row per grade spine is presented for the session's effective date, with the _F table holding the full dated history behind it.

Key Columns

The view exposes the primary key and effective-dating columns, the foreign keys that link a grade spine into the grade and business group hierarchy, and the standard Oracle who-columns for audit and concurrent processing.

• GRADE_SPINE_ID — Primary key uniquely identifying the grade spine record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date range within which this version of the row is valid; the filtered columns that make the view date-effective.
• BUSINESS_GROUP_ID — Business group that owns the grade spine, determining the HR security and legislative context.
• PARENT_SPINE_ID — Self-referencing pointer to a parent grade spine, supporting hierarchical spine structures.
• GRADE_ID — Grade associated with the spine, tying the row to the grade definition.
• CEILING_STEP_ID — Reference to the ceiling (top) step of the grade spine, defining the upper bound of the ladder.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent request and program context that last touched the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns.

Common Use Cases and Queries

Typical uses include validating grade ladder setup for a business group, rendering active spine hierarchies in reports, and feeding integrations that must respect date-effective grade data. A minimal query follows:

• SELECT grade_spine_id, business_group_id, parent_spine_id, grade_id, ceiling_step_id FROM apps.per_grade_spines WHERE business_group_id = :p_business_group_id;
• To retrieve the full dated history rather than the current row, query apps.per_grade_spines_f and constrain EFFECTIVE_START_DATE and EFFECTIVE_END_DATE explicitly.
• To resolve a hierarchy, join the view to itself on PARENT_SPINE_ID to walk from child spines to their parents.

Because the view filters on the FND_SESSIONS effective date for the current session, its output changes automatically at date boundaries; queries run outside a properly initialized session context may return no rows. Applications should therefore be run from within EBS, or the session effective date must be set explicitly.