Results for “dist_bdgt_iss_val”

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

Overview

BEN_CWB_PERSON_GROUPS is a table within the BEN (Advanced Benefits) product module of Oracle E-Business Suite, holding person group definitions used by the Compensation Workbench (CWB) feature. The CWB component of Advanced Benefits supports the distribution, submission, reservation, and approval of compensation budgets across defined populations of eligible persons. Each row in BEN_CWB_PERSON_GROUPS represents a person group tied to a specific compensation workbench lifecycle event, a plan, and a plan option, serving as the anchor record against which budget allocation and worksheet activities are tracked.

From a modeling perspective, the metadata classifies this object as standalone under the heuristic Data Vault classification mined from its foreign key structure. In Data Vault terms this suggests the table behaves predominantly as a standalone hub or reference entity rather than participating in richly defined link relationships within the documented schema. Its composite primary key defines the natural business grain of a person group record.

Key Information Stored

The table contains 43 documented columns. The primary key, BEN_CWB_PERSON_GROUPS_PK, is a composite of three columns: GROUP_PER_IN_LER_ID, GROUP_PL_ID, and GROUP_OIPL_ID. These three columns together form the business-key candidate and uniquely identify each person group row. GROUP_PL_ID, the value referenced in the user search, identifies the associated plan within the person group key. GROUP_OIPL_ID identifies the plan option, and GROUP_PER_IN_LER_ID identifies the person-in-learner relationship context.

The most significant remaining columns cluster into several functional areas:

• Lifecycle and timing: LF_EVT_OCRD_DT (life event occurred date), DUE_DT (due date), and BDGT_POP_CD (budget population code) define the temporal and population context of the group.
• Access and approval workflow: ACCESS_CD, APPROVAL_CD, APPROVAL_DATE, APPROVAL_COMMENTS, SUBMIT_CD, SUBMIT_DATE, and SUBMIT_COMMENTS track the submission and approval states and audit trail.
• Budget values: DIST_BDGT_VAL (distributed budget), WS_BDGT_VAL (worksheet budget), RSRV_VAL (reserve value), along with minimum, maximum, and increment variants (DIST_BDGT_MN_VAL, DIST_BDGT_MX_VAL, DIST_BDGT_INCR_VAL and equivalents for WS and RSRV).
• Issued and default values: DIST_BDGT_ISS_VAL, WS_BDGT_ISS_VAL, DFLT_DIST_BDGT_VAL, DFLT_WS_BDGT_VAL, and issue dates.
• Audit columns: OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, plus last-updated-by and last-updated-date fields for each of the WS, DIST, and RSRV budget values.

Common Use Cases and Queries

The table is typically queried to reconcile allocated versus reserved compensation budgets across person groups, to validate submission and approval state before period close, and to report on budget consumption for a plan option. A representative pattern retrieves all person groups for a given plan, plan option, and lifecycle event:

• Filter by GROUP_PL_ID and GROUP_OIPL_ID to isolate all person groups for a specific plan option.
• Compare DIST_BDGT_VAL against RSRV_VAL to determine remaining distributable budget.
• Join to plan and plan option tables through GROUP_PL_ID and GROUP_OIPL_ID for descriptive reporting.
• Filter on APPROVAL_CD or SUBMIT_CD to surface records pending approval or submission.
• Use LAST_UPDATE_DATE and the per-value update dates for incremental extraction into a reporting warehouse.

Related Objects

The documented relationship data describes BEN_CWB_PERSON_GROUPS as standalone, with no explicit foreign keys captured in the mined FK structure. In practice, joining objects in the Advanced Benefits schema include:

• BEN_PL_TYP_F — referenced through GROUP_PL_ID for plan definitions.
• BEN_OIPL_F — referenced through GROUP_OIPL_ID for plan option definitions.
• BEN_PER_IN_LER_F — referenced through GROUP_PER_IN_LER_ID for the person-in-learner relationship.
• BEN_CWB_* budget and worksheet tables — sibling CWB objects sharing the person group grain for distribution and worksheet activity.
• FND_USER — joined through CREATED_BY, LAST_UPDATED_BY, and the per-value update-by columns for user attribution.

Because the schema heuristic classifies this object as standalone, referential integrity is largely enforced at the application layer rather than through documented database constraints; this should be considered when designing extracts and reconciliation reports.