Results for “pay_annulization_factor”

44 results




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

Overview

BEN_CWB_PERSON_INFO is a table owned by the BEN schema within the Oracle E-Business Suite Advanced Benefits (BEN) product, documented as valid in releases 12.1.1 and 12.2.2. It stores "CWB Person Information" — the compensation workbench person-level data set used by Oracle Compensation Workbench and related Advanced Benefits compensation processes. The table acts as the person-centric staging and reference layer that Compensation Workbench and Benefits compensation reporting consume when evaluating a worker's assignment, salary, grade, performance, and market context for a compensation cycle.

The documented schema contains 206 columns, with the primary key defined as BEN_CWB_PERSON_INFO_PK on GROUP_PER_IN_LER_ID. From an analytical modeling perspective, the metadata's heuristic Data Vault classification is standalone (neither hub, link, nor satellite). This suggests modeling the table as a transaction-scoped staging or snapshot entity rather than as part of a normalized Data Vault construct, since its key is a group-level identifier rather than a durable business entity key.

Key Information Stored

The surrogate primary key is GROUP_PER_IN_LER_ID, which also serves as the single documented unique index and is the sole business-key candidate. The remaining columns capture the person's organizational and compensation context for a Compensation Workbench cycle. The most significant include:

Common Use Cases and Queries

Typical usage centers on Compensation Workbench reporting and salary/grade analysis. A common pattern joins the person info row to dependent CWB tables through GROUP_PER_IN_LER_ID, and to HR assignment classification for filtering:

  • Joining to BEN_CWB_PERSON_RATES on GROUP_PER_IN_LER_ID to retrieve component rates.
  • Joining to BEN_CWB_SUMMARY and BEN_CWB_RPT_DETAIL for summary and report output.
  • Joining to BEN_CWB_AUDIT to reconcile changes captured for the same group/person context.
  • Filtering on PEOPLE_GROUP_ID, BUSINESS_GROUP_ID, or EFFECTIVE_DATE to scope a compensation cycle.
  • Comparing BASE_SALARY against GRD_MID_POINT or MKT_MID_SALARY for compa-ratio and market position analysis.

Sample pattern: SELECT p.FULL_NAME, p.BASE_SALARY, p.GRD_COMPARATIO, r.* FROM ben.ben_cwb_person_info p JOIN ben.ben_cwb_person_rates r ON r.group_per_in_ler_id = p.group_per_in_ler_id WHERE p.business_group_id = :bg_id AND p.effective_date BETWEEN :start_dt AND :end_dt;

Related Objects

The FK metadata documents both outbound and inbound relationships.

  • BEN_CWB_RPT_DETAIL.GROUP_PER_IN_LER_ID → BEN_CWB_PERSON_INFO — detail lines for report output.
  • BEN_CWB_PERSON_RATES.GROUP_PER_IN_LER_ID → BEN_CWB_PERSON_INFO — component rate values per person.
  • BEN_CWB_AUDIT.GROUP_PER_IN_LER_ID → BEN_CWB_PERSON_INFO — audit trail rows.
  • BEN_CWB_SUMMARY.GROUP_PER_IN_LER_ID → BEN_CWB_PERSON_INFO — aggregated summary rows.
  • PAY_PEOPLE_GROUPS referenced via PEOPLE_GROUP_ID.
  • HR_SOFT_CODING_KEYFLEX referenced via SOFT_CODING_KEYFLEX_ID.
  • PER_ASSIGNMENT_STATUS_TYPES referenced via ASSIGNMENT_STATUS_TYPE_ID.

These relationships establish BEN_CWB_PERSON_INFO as the anchor record for the downstream Compensation Workbench reporting, rating, audit, and summary tables.