Results for “cr_mnl_adj_flag”

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

Overview

BEN_PRTT_PREM_BY_MO_X is an APPS-owned view within the Oracle Advanced Benefits (BEN) product module. It exposes participant premium amounts broken down by month, and is a "date-tracked" (effective-dated) read-only presentation layer over the underlying premium-by-month entity. The "_X" suffix follows the standard Oracle EBS convention for a view that filters a "_F" (full) table to the row or rows currently in effect, so the view always returns the single active version of each premium-by-month record as of the query date.

The view plays a supporting role in benefits reporting and integration. It allows concurrent programs, extracts, and external interfaces to read monthly premium distributions without having to replicate the effective-date filtering logic themselves. Because the view already applies the TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE predicate, consumers receive only currently effective rows, which is the correct basis for most operational and payroll-facing reporting.

Underlying Base Objects

The view is defined solely over one base object, BEN_PRTT_PREM_BY_MO_F, which is referenced through a synonym in the APPS schema. The view text projects every column from the base table and appends the effective-date filter. No joins are performed, so the view does not enrich the data with descriptive lookups; it is a straight, date-filtered projection.

The relationship is therefore one-to-one at the current point in time: each active row in BEN_PRTT_PREM_BY_MO_F yields exactly one row in BEN_PRTT_PREM_BY_MO_X. Historical or future-dated versions of a premium-by-month record remain in the base table but are excluded by the view's predicate. This design keeps the view small and fast for read access while the base table retains the full temporal history.

Key Columns

• PRTT_PREM_BY_MO_ID — Primary identifier for the premium-by-month record.
• PRTT_PREM_ID — Foreign reference linking the monthly breakdown back to the parent participant premium record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-track boundaries governing which version is currently active.
• MO_NUM / YR_NUM — The month and year to which the premium amount applies.
• VAL / CR_VAL — The premium value and, where applicable, its calculated or credited value.
• UOM — Unit of measure qualifying the value.
• ANTCPD_PRTT_CNTR_UOM / ANTCPD_PRTT_CNTR_VAL — Anticipated participant contribution, expressed as a unit of measure and a value.
• MNL_ADJ_FLAG / CR_MNL_ADJ_FLAG / ALCTD_VAL_FLAG — Flags indicating manual adjustment and allocated-value status.
• COST_ALLOCATION_KEYFLEX_ID — Identifier of the cost allocation key flexfield used to distribute the premium.
• BUSINESS_GROUP_ID — The business group owning the record.
• PRM_ATTRIBUTE_CATEGORY and PRM_ATTRIBUTE1 through PRM_ATTRIBUTE30 — The descriptive flexfield (DFF) segment columns for the entity. These are the fields most relevant to a search on "prm_attribute1", which is the first DFF segment.
• Standard WHO and concurrency columns (LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, REQUEST_ID, PROGRAM_ID, and related program columns).

Common Use Cases and Queries

Typical scenarios include month-by-month premium reconciliation, cost allocation validation, and custom extracts that must honour effective dating automatically. A basic query retrieves the current monthly premium rows for a parent premium:

• SELECT prtt_prem_by_mo_id, prtt_prem_id, yr_num, mo_num, val, uom, prm_attribute1 FROM ben_prtt_prem_by_mo_x WHERE prtt_prem_id = :p_prem_id ORDER BY yr_num, mo_num;
• SELECT prtt_prem_by_mo_id, mo_num, yr_num, cr_val, alctd_val_flag FROM ben_prtt_prem_by_mo_x WHERE business_group_id = :p_bg_id AND mnl_adj_flag = 'Y';
• SELECT prtt_prem_by_mo_id, val, cost_allocation_keyflex_id FROM ben_prtt_prem_by_mo_x WHERE prm_attribute_category = :p_cat AND prm_attribute1 = :p_attr1;

Because the view applies the effective-date predicate using TRUNC(SYSDATE), queries cannot retrieve historical or future-dated breakdowns; those must read BEN_PRTT_PREM_BY_MO_F directly with an explicit date range. When using the DFF segment PRM_ATTRIBUTE1, note that meaningful values are only populated when PRM_ATTRIBUTE_CATEGORY is set, so filter on the category alongside the segment to obtain correct results.