Results for “per_bf_balance_types_efc”

26 results




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

Overview

PER_BF_BALANCE_TYPES_EFC is a table owned by the HR schema within the PER (Human Resources) product family of Oracle E-Business Suite. It participates in the balance and compensation framework that underpins Oracle Payroll, Advanced Benefits, and the broader Total Compensation architecture. The table name follows the EFC (Electronic File Collection / interface) naming convention used in HRMS balance feeds, indicating that it acts as a relationship or mapping table associating balance types with EFC actions. It stores three columns, making it a compact, purpose-built linking structure rather than a transactional or master-data repository.

Based on the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a satellite-leaning entity. In Data Vault terms, a satellite captures descriptive attributes that change over time and attach to a hub or link, rather than serving as a pure hub (unique business entity) or a pure link (many-to-many association). Practitioners designing a warehouse layer should treat PER_BF_BALANCE_TYPES_EFC as a descriptive companion to the balance type and EFC action hubs, carrying the currency attribute and the association between them as context. This is a modeling suggestion, not a declaration of Oracle's internal design intent.

Key Information Stored

The table is documented with three physical columns and one primary key:

  • BALANCE_TYPE_ID — Surrogate identifier referencing an HR balance type. It forms part of the composite primary key and is a business-key candidate.
  • EFC_ACTION_ID — Surrogate identifier referencing the HR_EFC_ACTIONS table. It also forms part of the composite primary key and is the sole documented foreign key column.
  • CURRENCY — The currency associated with the balance type / EFC action pairing. This is the descriptive attribute that gives the record its satellite (rather than pure link) character.

The composite primary key PER_BF_BALANCE_TYPES_EFC_PK is defined over (BALANCE_TYPE_ID, EFC_ACTION_ID). Both key columns are documented as unique business-key candidates via the unique index of the same name. The foreign key maps EFC_ACTION_ID to HR_EFC_ACTIONS.EFC_ACTION_ID, establishing a parent-child relationship where one EFC action may be referenced by multiple balance type associations. Because no independent surrogate single-column key exists, the natural business key is the combination of the two identifier columns.

Common Use Cases and Queries

Typical scenarios include reconciling balance feeds against EFC actions, reporting which balance types are eligible for a given electronic file action, and validating currency configuration before running payroll or benefits extraction processes. A representative join pattern is:

  • Join PER_BF_BALANCE_TYPES_EFC to HR_EFC_ACTIONS using EFC_ACTION_ID to retrieve action descriptions alongside balance type identifiers.
  • Filter by CURRENCY to isolate balance type / action combinations for a specific ledger or reporting currency.
  • Use the composite primary key columns in EXISTS or INTERSECT constructs when de-duplicating balance type mappings during migration or setup validation.
  • Drive extracts that populate downstream EFC staging tables by selecting DISTINCT BALANCE_TYPE_ID values per EFC_ACTION_ID.

Reporting users should be aware that this table is small and administrative; it is generally queried in combination with balance type and EFC action lookup tables rather than in high-volume operational joins.

Related Objects

The most significant relationships documented or implied by the metadata are:

  • HR_EFC_ACTIONS — Parent table via PER_BF_BALANCE_TYPES_EFC.EFC_ACTION_ID → HR_EFC_ACTIONS.EFC_ACTION_ID. This is the sole documented foreign key.
  • PER_BF_BALANCE_TYPES — The balance type definitions referenced by BALANCE_TYPE_ID, providing name and classification attributes.
  • PER_BF_BALANCE_TYPES_EFC_PK — The unique index enforcing the composite business key.
  • Payroll and Benefits balance feed processes — Oracle Payroll and Advanced Benefits routines that consume EFC action mappings when constructing balance feeds.

Because the object is a narrow association table, its dependent set is limited; integrators should rely on the documented FK to HR_EFC_ACTIONS as the authoritative join path and treat the balance type side as an inferred relationship based on the BALANCE_TYPE_ID naming convention.