Results for “per_kr_g_points_uk1”

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

Overview

HR.PER_KR_G_POINTS is a Korean localization table within the Oracle E-Business Suite Human Resources (HR) schema. It stores the second grade point definitions that make up the Korean grade structure used by Korean payroll and grading functionality. The table operates as a child of PER_KR_GRADES, capturing the individual grade points that belong to a parent grade, along with the sequence in which they are displayed and the date range over which each point is valid. The table is registered under FND Design Data PER.PER_KR_G_POINTS and holds a VALID status in the documented 12.1.1 / 12.2.2 metadata.

In Data Vault terms, the heuristic classification for this object is satellite-leaning. It carries descriptive attributes (grade point name, sequence, enabled flag, effective dates) that describe a business key defined in the parent grade table, rather than acting as a standalone business hub. Modelers should treat it as a satellite-like detail structure attached to the grade entity, with its surrogate key retained for cross-reference.

Key Information Stored

The table's physical definition contains 13 documented columns. The most significant are:

• GRADE_POINT_ID — NUMBER(15). The surrogate primary key, uniquely identifying each grade point row. This is the column enforced by PER_KR_G_POINTS_PK.
• GRADE_ID — NUMBER(15). Foreign key to PER_KR_GRADES, linking each point to its parent grade definition.
• GRADE_POINT_NAME — VARCHAR2(80). The descriptive name of the grade point.
• SEQUENCE — NUMBER(15). Controls display ordering of grade points within a grade.
• ENABLED_FLAG — Indicates whether the grade point is active for selection.
• START_DATE_ACTIVE / END_DATE_ACTIVE — DATE columns defining the effective window; the point is invalid before START_DATE_ACTIVE and after END_DATE_ACTIVE.
• OBJECT_VERSION_NUMBER — System-maintained row version, incremented on each update to support optimistic locking.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, providing audit lineage.

Two business-key candidates beyond the surrogate key are documented. PER_KR_G_POINTS_UK1 enforces uniqueness on (GRADE_ID, SEQUENCE), guaranteeing a distinct ordering position within each grade. PER_KR_G_POINTS_UK2 enforces uniqueness on (GRADE_ID, GRADE_POINT_NAME), preventing duplicate point names inside the same grade. A user searching for "per_kr_g_points_uk1" is therefore looking at the constraint that governs the ordinal uniqueness of grade points per grade.

Common Use Cases and Queries

The primary reporting need is to enumerate the grade points belonging to a grade in display order, filtered to currently active rows. A typical query joins the grade point table to its parent grade and applies the effective-date window:

SELECT g.grade_id, g.grade_point_name, g.sequence, g.enabled_flag
FROM   hr.per_kr_g_points g
WHERE  g.grade_id = :p_grade_id
AND    g.enabled_flag = 'Y'
AND    TRUNC(SYSDATE) BETWEEN g.start_date_active
                           AND NVL(g.end_date_active, TRUNC(SYSDATE))
ORDER BY g.sequence;

Payroll and grading processes use the point amounts defined downstream, so a second common pattern resolves grade point identifiers before joining to the amount table:

SELECT p.grade_point_id, p.grade_point_name, a.amount
FROM   hr.per_kr_g_points p,
       hr.per_kr_g_point_amount_f a
WHERE  p.grade_point_id = a.grade_point_id
AND    p.grade_id = :p_grade_id;

Validation queries frequently target the unique-key constraints, for example detecting duplicate sequences or duplicate names within a grade before data load. Date-effective lookups and ENABLED_FLAG filtering are essential because historical rows for the same grade may remain stored while only the current generation is active.

Related Objects

The following objects have documented relationships to PER_KR_G_POINTS:

• HR.PER_KR_GRADES — Parent table. Joined on PER_KR_GRADES.GRADE_ID = PER_KR_G_POINTS.GRADE_ID.
• HR.PER_KR_G_POINT_AMOUNT_F — Child table containing the monetary values tied to each point. Joined on PER_KR_G_POINT_AMOUNT_F.GRADE_POINT_ID = PER_KR_G_POINTS.GRADE_POINT_ID.
• APPS.PER_KR_G_POINTS — Application-synonym view exposed to runtime code.
• APPS.PER_KR_G_POINTS_WHO — WHO-enabled view used by the Oracle Forms layer.
• PUBLIC.PER_KR_G_POINTS — Public synonym for cross-schema access.

These relationships confirm the table's role as the intermediate definition layer between the grade structure and the grade point monetary amounts in the Korean HR localization.