Results for “actl_prem_id”

50+ results




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

Overview

BEN_ACTL_PREM_F_EFC is a table in the BEN schema (Advanced Benefits) within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a structural copy of the BEN_ACTL_PREM_F table, populated by the EFC (Euro as Functional Currency) process, which converts and stores monetary benefit premium values when the Euro is designated as the functional currency. The "_EFC" suffix denotes this purpose: the table preserves the same column layout as its parent so downstream benefits calculations, extracts, and reporting can reference Euro-denominated premium figures without altering the base table.

ETRM's heuristic Data Vault classification for this object is standalone. Examined through a Data Vault lens, this suggests the table behaves primarily as a satellite- or fact-style structure keyed by the natural business key ACTL_PREM_ID rather than acting as a hub or link, and no foreign-key relationships to other vault entities are documented.

Key Information Stored

The documented physical schema contains eight columns. The most significant include:

  • ACTL_PREM_ID — the actual premium identifier, the primary business key that the user searched for. It is the leading column of the primary key and of the unique index.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — date-effective range columns that make this a date-tracked (datetrack) table, enabling historical and current-row querying.
  • EFC_ACTION_ID — identifies the EFC process run that created the row, distinguishing separate conversion passes or action batches.
  • UPR_LMT_VAL and LWR_LMT_VAL — the upper and lower limit values applied to the premium amount.
  • UOM — the unit of measure associated with the stored value.
  • VAL — the stored premium or limit amount itself.

The surrogate/compound primary key is BEN_ACTL_PREM_F_EFC_PK, defined across ACTL_PREM_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and EFC_ACTION_ID. The unique index BEN_ACTL_PREM_F_EFC_N1 carries the same four columns and is the documented business-key candidate. Note that ACTL_PREM_ID alone is not unique — a single premium can have multiple rows across effective dates and EFC action identifiers.

Common Use Cases and Queries

Typical usage centers on Euro-conversion reporting and reconciliation. Analysts join this table back to BEN_ACTL_PREM_F to compare converted versus base-currency premium amounts, or filter by EFC_ACTION_ID to isolate a specific conversion run.

A representative pattern retrieves the current effective row for a given premium:

  • SELECT actl_prem_id, val, uom, upr_lmt_val, lwr_lmt_val FROM ben.ben_actl_prem_f_efc WHERE actl_prem_id = :p_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Reporting scenarios include validating that every EFC action produced complete premium records, auditing limit values (UPR_LMT_VAL/LWR_LMT_VAL) against policy rules, and feeding Euro-denominated premium figures into benefits statements or extracts. Because rows are date-tracked, point-in-time queries must always constrain on the effective date range to avoid returning duplicate historical versions.

Related Objects

The most significant associated objects, based on the documented metadata and the EFC design, include:

  • BEN_ACTL_PREM_F — the base table of which this is a copy; joined on ACTL_PREM_ID and matching effective dates.
  • BEN_ACTL_PREM_F_EFC_PK — the primary key constraint enforcing uniqueness of ACTL_PREM_ID, effective dates, and EFC_ACTION_ID.
  • BEN_ACTL_PREM_F_EFC_N1 — the unique index supporting the same business-key columns.
  • EFC process/action objects in the BEN schema — the conversion routines that populate EFC_ACTION_ID and the corresponding values.
  • Advanced Benefits calculation and premium-reporting views that read VAL, UOM, and limit columns.

Because the table is classified as standalone with no documented foreign keys, integration with other BEN entities is driven primarily through the shared ACTL_PREM_ID business key rather than enforced referential constraints.