Results for “ben_nnmntry_uom”

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

Overview

The view APPS.BENBV_BNFTS_BAL_V is a business-facing, read-only database view within the Oracle E-Business Suite Benefits module. It exposes the benefit balance definitions maintained in the Benefits setup, presenting translated and decoded values suitable for reporting, integration, and concurrent program output. The view is defined with a WITH READ ONLY clause, confirming that it is intended strictly as a query interface rather than as a DML target.

A distinguishing feature of this view is its use of the HR_BIS.BIS_DECODE_LOOKUP function, which transforms stored lookup codes into their descriptive meanings. This makes the view particularly useful for reports and interfaces where human-readable values are required rather than raw codes. The security predicate BNB.BUSINESS_GROUP_ID = NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, BNB.BUSINESS_GROUP_ID) enforces the current user's security profile, restricting output to benefit balances belonging to the user's accessible business group.

The view is of particular interest to users searching for ben_nnmntry_uom, as it explicitly decodes both UOM and NNMNTRY_UOM columns using that lookup type.

Underlying Base Objects

According to the ETRM metadata, the view is defined over two referenced objects:

• BEN_BNFTS_BAL_F (documented as a SYNONYM) — the base Benefits balance table supplying all stored data columns.
• HR_BIS (PACKAGE) — providing the BIS_DECODE_LOOKUP function for lookup translation and GET_SEC_PROFILE_BG_ID for business group security enforcement.

The view aliases the balance table as BNB and projects its columns with decoding and descriptive flexfield annotation applied. The reliance on BEN_BNFTS_BAL_F as the driving object means the view reflects the same effective-dating structure as the base balance table.

Key Columns

• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective boundaries for the balance definition, supporting date-tracked querying.
• BNFTS_BAL_DESC — description of the benefit balance.
• UOM — unit of measure code, accompanied by a decoded value via BIS_DECODE_LOOKUP('BEN_NNMNTRY_UOM', BNB.UOM).
• NNMNTRY_UOM — the monetary unit of measure, also decoded through the BEN_NNMNTRY_UOM lookup type. This is the column most directly associated with the search term ben_nnmntry_uom.
• NAME — the balance name.
• BNFTS_BAL_USG_CD — usage code, decoded using the BEN_BNFTS_BAL_USG lookup type.
• BNFTS_BAL_ID / BUSINESS_GROUP_ID — identifier columns for the balance and its owning business group.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard WHO audit columns.

The view also carries a descriptive flexfield annotation, '_DF:BEN:BEN_BNFTS_BAL_F:BNB', indicating support for DFF display in the underlying form context.

Common Use Cases and Queries

Typical scenarios include benefit balance reporting, lookup validation of unit-of-measure values, and integration extracts requiring decoded benefit balance attributes. A representative query retrieving balance definitions with decoded units of measure follows:

• SELECT BNFTS_BAL_ID, NAME, BNFTS_BAL_DESC, UOM, NNMNTRY_UOM, BNFTS_BAL_USG_CD FROM APPS.BENBV_BNFTS_BAL_V;
• Filtering for monetary unit of measure values: SELECT BNFTS_BAL_ID, NAME, NNMNTRY_UOM FROM APPS.BENBV_BNFTS_BAL_V WHERE NNMNTRY_UOM IS NOT NULL;
• Date-effective lookups: SELECT NAME, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM APPS.BENBV_BNFTS_BAL_V WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

Because the view is read-only and applies security profile filtering automatically, it is safe for concurrent program and BI Publisher use without additional business group predicates.