Results for “bnfts_bal_usg_cd”

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

Overview

BENBV_BNFTS_BAL_V is a read-only view owned by the APPS schema within the Oracle Advanced Benefits (BEN) module. Its documented purpose is to identify balance type information that is not readily derivable from information otherwise held in the system, or which may be supplied by a third-party agent. In practice the view exposes the benefits balance type flexfield definition together with decoded, human-readable descriptions for each coded value, so that balances configured for absence plans, accrual plans, and similar benefit constructs can be reported and integrated without the consumer having to resolve lookup codes independently.

The view declares WITH READ ONLY, so it is intended strictly for query, reporting, and outbound integration. It is available in the ETRM 12.1.1 and 12.2.2 code lines under the same name and structure, which makes it a stable reference point for custom reports, extracts, and interface programs that need balance type metadata.

Underlying Base Objects

The view is defined over two documented objects:

• BEN_BNFTS_BAL_F (referenced through a synonym) — the benefits balance type base table, aliased as BNB in the view text. This table holds the effective-dated balance type definitions, including the descriptive flexfield context and the usage code.
• HR_BIS (package) — supplies the BIS_DECODE_LOOKUP function used to translate coded values into their lookup meanings, and GET_SEC_PROFILE_BG_ID, which applies the security profile to restrict rows to the caller's permitted business group.

Because the view is a projection over BEN_BNFTS_BAL_F rather than a copy, all rows are effective-dated and subject to the base table's DateTrack behavior. The business group predicate BNB.BUSINESS_GROUP_ID = NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, BNB.BUSINESS_GROUP_ID) means a session with a security profile set sees only its own business group, while a null profile value leaves all business groups visible.

Key Columns

• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — effective dating of the balance type definition.
• BNFTS_BAL_DESC — description of the balance type.
• NAME — the balance type name, together with a descriptive flexfield token (_DF:BEN:BEN_BNFTS_BAL_F:BNB) used by the flexfield machinery.
• UOM / UOM_M — the unit of measure code and its decoded meaning.
• NNMNTRY_UOM / NNMNTRY_UOM_M — the non-monetary unit of measure code and its decoded meaning; both are decoded using the BEN_NNMNTRY_UOM lookup type. This pair is the direct answer to searches for the ben_nnmntry_uom lookup.
• BNFTS_BAL_USG_CD / BNFTS_BAL_USG_CD_M — the balance usage code and its decoded meaning, resolved through the BEN_BNFTS_BAL_USG lookup.
• BNFTS_BAL_ID — primary key of the balance type.
• BUSINESS_GROUP_ID — owning business group, subject to the security predicate.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reporting the master list of balance types with decoded units of measure, driving accrual and absence configuration reviews, and feeding downstream extracts where the consumer cannot call BIS_DECODE_LOOKUP directly. A basic listing looks like this:

• SELECT BNFTS_BAL_ID, NAME, UOM_M, NNMNTRY_UOM_M, BNFTS_BAL_USG_CD_M FROM BENBV_BNFTS_BAL_V ORDER BY NAME;
• SELECT NAME, NNMNTRY_UOM, NNMNTRY_UOM_M FROM BENBV_BNFTS_BAL_V WHERE NNMNTRY_UOM IS NOT NULL; — identifies balance types expressed in non-monetary units.
• SELECT BNFTS_BAL_ID, BNFTS_BAL_DESC, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM BENBV_BNFTS_BAL_V WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE; — returns only currently effective definitions.

Because the view is read-only and security-filtered, it is safe to expose to reporting users and to reference from PL/SQL extraction routines without risk of accidental DML against the underlying flexfield table.