Results for “d_grade”

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

Overview

PER_GRADE_SPINES_V is a seeded Oracle E-Business Suite database view owned by the APPS schema in the PER (Human Resources) product. Its documented status is VALID, and the ETRM description states that it is "used to support user interface." This indicates that the view is a UI-support construct rather than an analytic or integration interface; it exists primarily to feed Oracle Forms or OAF-based grade-spine maintenance pages within the Compensation and Grade management functionality of Oracle HRMS.

The view presents the effective-dated rows of the PER_GRADE_SPINES_F table joined to descriptive and reference information such as the grade name, the parent spine name, the ceiling spinal point, its sequence, and its spinal point identifier. Because it embeds FND_SESSIONS and USERENV('SESSIONID'), the view is session- and date-aware: only rows whose effective date range covers the current session's effective date are returned, and only steps effective as of that date are joined. This behavior is typical of EBS "spine" or "slice" views constructed to support date-tracked user interfaces. The object is not intended for external reporting but can be queried for diagnostics and reconciliation when working with grade progression and spinal-point hierarchies.

Underlying Base Objects

The view is defined over the following objects, all referenced through synonyms in the APPS schema:

• PER_GRADE_SPINES_F — the driving base table storing grade spine definitions, effective dates, business group, parent spine, grade, and ceiling step.
• PER_GRADES_TL — the translated grade table providing the grade name (NAME) for the session language.
• PER_PARENT_SPINES — the parent spine definition table supplying the parent spine name.
• PER_SPINAL_POINTS — reference data for spinal points, providing the point name and identifier.
• PER_SPINAL_POINT_STEPS (VIEW) — a view used to validate that the grade spine's ceiling step maps to a spinal point effective on the session date.
• FND_SESSIONS — the Applications session table supplying the effective date for the current session.

Joins are keyed on GRADE_ID, PARENT_SPINE_ID, SPINAL_POINT_ID, and SESSION_ID, with date range predicates enforced on PER_SPINAL_POINT_STEPS and PER_GRADE_SPINES_F against FND.EFFECTIVE_DATE.

Key Columns

Key columns exposed include:

• GRADE_SPINE_ID — primary identifier of the grade spine record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective-dating window of the spine.
• BUSINESS_GROUP_ID — the HR business group (security organization) owning the record.
• PARENT_SPINE_ID — reference to PER_PARENT_SPINES.
• GRADE_ID — reference to the grade definition in PER_GRADES_TL.
• CEILING_STEP_ID — the step that defines the ceiling of the spine.
• D_GRADE, D_PARENT_SPINE, D_CEIL_SPINAL_POINT — descriptive name columns derived from the grade name, parent spine name, and spinal point name respectively.
• C_SPINAL_POINT_ID, NEW_CEILING_SEQUENCE — the spinal point identifier and sequence associated with the ceiling step.
• OBJECT_VERSION_NUMBER, ROW_ID — concurrency-control and row-addressing columns.
• Standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, etc.) and concurrent-program audit columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID).

Common Use Cases and Queries

Typical uses include diagnosing why a grade spine is not appearing in the Grade Spine UI, reconciling grade spine definitions for a business group, and confirming which spinal point represents the ceiling for a given spine on a given date.

SELECT grade_spine_id,
       d_grade,
       d_parent_spine,
       d_ceil_spinal_point,
       new_ceiling_sequence,
       effective_start_date,
       effective_end_date
FROM   apps.per_grade_spines_v
WHERE  business_group_id = :p_business_group_id
ORDER  BY d_parent_spine, d_grade;

Because the view filters on USERENV('SESSIONID') and FND_SESSIONS.EFFECTIVE_DATE, it behaves like a "current session" slice. Queries run outside an EBS session may return no rows unless a session row exists for the executing session. For point-in-time or cross-date analysis, querying PER_GRADE_SPINES_F directly and joining the descriptive tables explicitly is preferable. The view remains a useful, low-risk object for validating grade spine configuration in 12.1.1 and 12.2.2.