Search Results per_kr_grade_amount_f




Overview
Explore in AI Chat

Overview

PER_KR_GRADE_AMOUNT_F is a Korea-specific Human Resources table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores grade-level amount values tied to Korean grade definitions, providing the localization layer that links compensation amounts to the country-specific grade structures used by Korean payroll and human resources legislation. The table is part of the PER (Human Resources) product family and exists alongside other KR-prefixed localization objects that supplement the global PER_GRADES model for Korean business requirements.

The effective-dated primary key PER_KR_GRADE_AMOUNT_F_PK (GRADE_AMOUNT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE) establishes this table as a date-tracked record. Based on the mined foreign-key structure, the heuristic Data Vault classification is satellite-leaning: the table hangs off a parent grade hub (PER_KR_GRADES) and carries descriptive, time-variant attributes. Modelers may therefore treat PER_KR_GRADE_AMOUNT_F as a satellite of a Korean grade hub when designing warehouse or integration layers.

Key Information Stored

The physical schema documents 42 columns, comprising the primary key, the foreign-key column, the business attribute, the standard WHO audit columns, and a large ATTRibUTE1 through ATTRibUTE30 flexfield extension area.

  • GRADE_AMOUNT_ID — surrogate identifier for the amount record; part of the composite primary key.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-range columns that complete the primary key, enabling multiple dated versions of the same amount record and supporting date-tracked (DateTrack) queries.
  • GRADE_ID — foreign key to PER_KR_GRADES, identifying the parent Korean grade to which the amount applies.
  • GRADE_AMOUNT — the principal business attribute; the monetary or numeric amount associated with the grade.
  • ATTRIBUTE_CATEGORY and its related descriptive flexfield context.
  • ATTRIBUTE1 through ATTRIBUTE30 — the descriptive flexfield segment columns used for customer-specific extensions, the majority of the table's 42 columns.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO audit trail columns present on nearly every EBS transactional table.

The only unique index documented is the primary key itself, so GRADE_AMOUNT_ID combined with the two effective dates is the definitive business-key candidate. No standalone surrogate-only unique constraint is documented beyond the composite PK.

Common Use Cases and Queries

Typical usage centers on reporting grade-level Korean compensation and validating that a grade has an active amount for a given date. Because the table is effective-dated, queries must filter the effective range. A representative pattern:

  • Current-amount lookup: SELECT ga.grade_amount FROM per_kr_grade_amount_f ga WHERE ga.grade_id = :grade_id AND TRUNC(SYSDATE) BETWEEN ga.effective_start_date AND ga.effective_end_date;
  • Historical trend: select all effective rows for one GRADE_ID ordered by EFFECTIVE_START_DATE to build an amount-change history.
  • Join to the parent grade to obtain grade names: join on PER_KR_GRADE_AMOUNT_F.GRADE_ID = PER_KR_GRADES.GRADE_ID.
  • Descriptive flexfield extraction: query ATTRIBUTE_CATEGORY and the relevant ATTRIBUTE columns when a client has configured Korean-specific reporting fields.
  • Data migration and integration: extract via the surrogate key plus effective dates, since no alternate unique key exists.

Related Objects

The documented foreign key defines the principal relationship:

  • PER_KR_GRADES — parent table; joined via PER_KR_GRADE_AMOUNT_F.GRADE_ID = PER_KR_GRADES.GRADE_ID. This is the anchor of the grade hierarchy and the object the amount records roll up to.
  • The broader PER_GRADES and grade-step tables, which supply the global grade framework into which the KR localization is inserted.
  • Standard HR grade APIs (for example the grade and grade-amount business components) that maintain both the parent grade and these localized amount rows during data entry.

Because the metadata documents only one foreign key, these related objects should be verified against the specific patch level in use; additional KR localization objects may reference GRADE_AMOUNT_ID directly or indirectly through the parent grade.