Search Results ben_submit_stat

Overview

APPS.BENBV_CWB_PERSON_GROUPS_V is a reporting view in Oracle E-Business Suite Advanced Benefits (Oracle HRMS / BEN) that exposes Compensation Workbench person group records in a denormalized, decode-enriched form. The view is defined as a read-only projection over BEN_CWB_PERSON_GROUPS, the base table that stores person group header information for a Compensation Workbench cycle. Its purpose is to present budget, worksheet, reserve, approval, and submission attributes for a person group alongside their decoded lookup meanings, so that reporting tools, concurrent programs, and OBIEE/BI Publisher extracts do not have to perform the decode join themselves.

The view carries the "BV" prefix convention used by Oracle for Benefits and Compensation Workbench business views intended for external consumption. All database objects are owned by APPS. Because the defining query terminates with WITH READ ONLY, the view cannot be used for DML; it is strictly a query surface. The user search term "ben_appr_stat" maps directly to the BEN_APPR_STAT lookup type referenced inside this view, which decodes the APPROVAL_CD column into a human-readable approval status.

Underlying Base Objects

The documented base objects referenced by this view are:

• BEN_CWB_PERSON_GROUPS (SYNONYM) — the primary source table supplying all column values. The synonym resolves to the underlying BEN schema table holding Compensation Workbench person group records.
• BEN_BIS_UTILS (PACKAGE) — supplies the functions GET_GROUP_PL_NAME and GET_GROUP_OIPL_NAME, which translate GROUP_PL_ID and GROUP_OIPL_ID into group plan and other/optional plan names effective as of the life event occurred date (LF_EVT_OCRD_DT).
• HR_BIS (PACKAGE) — supplies BIS_DECODE_LOOKUP, used to decode the BDGT_POP_CD, ACCESS_CD, APPROVAL_CD, and SUBMIT_CD columns against their respective lookup types.

Because two of the three dependencies are PL/SQL packages rather than tables, the view is not a simple join but a function-driven projection. The date-effective plan name lookups mean the view is sensitive to LF_EVT_OCRD_DT, which must be populated for the decode functions to return meaningful values.

Key Columns

The view exposes several logical column groups:

• Lifecycle dates — LF_EVT_OCRD_DT (life event occurred date), DUE_DT, SUBMIT_DATE, APPROVAL_DATE, and the budget issue dates DIST_BDGT_ISS_DATE and WS_BDGT_ISS_DATE establish the timeline of the Compensation Workbench cycle.
• Budget and reserve values — DIST_BDGT_VAL, WS_BDGT_VAL, and RSRV_VAL hold distributed budget, worksheet budget, and reserve amounts; MIN, MAX, and INCR variants (DIST_BDGT_MN_VAL, DIST_BDGT_MX_VAL, DIST_BDGT_INCR_VAL, and equivalents) define allocation ranges and increments.
• Audit columns — WS_BDGT_VAL_LAST_UPD_DATE, DIST_BDGT_VAL_LAST_UPD_DATE, RSRV_VAL_LAST_UPD_DATE and their _LAST_UPD_BY counterparts identify who last changed budget and reserve values and when.
• Decoded status columns — APPROVAL_CD decoded via BEN_APPR_STAT gives the approval status (the target of the "ben_appr_stat" search); SUBMIT_CD decoded via BEN_SUBMIT_STAT gives submission status; ACCESS_CD via BEN_CWB_TASK_ACCESS gives task access; BDGT_POP_CD via BEN_POP gives budget population.
• Identifiers and WHO columns — GROUP_PER_IN_LER_ID, GROUP_PL_ID, GROUP_OIPL_ID, plus LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE for standard audit tracing.

Common Use Cases and Queries

Typical usage includes Compensation Workbench status dashboards, approval workflow tracking, and reconciliation of allocated versus reserved budgets. To isolate approval status, query the decoded column directly:

• SELECT GROUP_PL_ID, LF_EVT_OCRD_DT, APPROVAL_DATE, DIST_BDGT_VAL, WS_BDGT_VAL, RSRV_VAL FROM APPS.BENBV_CWB_PERSON_GROUPS_V WHERE APPROVAL_CD = 'APPR' AND LF_EVT_OCRD_DT = :p_effective_date;
• Filtering by approval status meaning via the decoded lookup value returned by BIS_DECODE_LOOKUP('BEN_APPR_STAT', APPROVAL_CD).
• Joining to BEN_CWB_PERSON_GROUPS directly when the raw code is required, or using the view when the decoded label is needed for an extract.

Because the view is read-only and function-based, bulk extracts should pass a bounded LF_EVT_OCRD_DT range to constrain the plan-name lookups.