Search Results ben_per_ler_f

Overview

BEN.BEN_CWB_RPT_DETAIL is a transactional detail table in the Oracle E-Business Suite Benefits module that stores processing detail for each worker when the Compensation Workbench (CWB) post process is executed for a CWB Plan. It resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10, and is owned by the BEN schema. The object is registered under FND Design Data as BEN.BEN_CWB_RPT_DETAIL and is documented as VALID across EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a standalone classification. Although the table carries numerous foreign keys — to BEN_BENEFIT_ACTIONS, BEN_CWB_PERSON_RATES, BEN_CWB_PERSON_INFO, PER_PAY_PROPOSALS, and PER_PAY_BASES — its 165 columns describe the changing state of a worker's CWB allocation across a processing run (prior, posted, and proposed values). This profile is best treated as a satellite-style detail store capturing row-level processing outcomes for a CWB plan lifecycle, rather than a pure hub or link.

Key Information Stored

The table is uniquely identified by the surrogate primary key CWB_RPT_DETAIL_ID, enforced by the unique index CWB_RPT_DETAIL_PK on APPS_TS_TX_IDX. No additional business-key unique indexes are documented; the remaining indexes (CWB_RPT_DETAIL_FK1 through FK5 and BEN_CWB_RPT_DETAIL_N1 through N14) are non-unique and support query access paths.

The most significant documented columns include:

• CWB_RPT_DETAIL_ID — surrogate primary key for the detail row.
• PERSON_ID — the worker whose CWB detail is being recorded (FK1).
• PL_ID and GROUP_PL_ID — the CWB plan and group plan context for the post process.
• BENEFIT_ACTION_ID — foreign key to BEN_BENEFIT_ACTIONS, linking to the governing benefit action.
• PERSON_RATE_ID — foreign key to BEN_CWB_PERSON_RATES, connecting to the individual's rate record.
• STATUS_CD — processing status of the detail row, also used by FK4.
• AMOUNT, UNITS, ADJUSTED_AMOUNT, and AMOUNT_POSTED — monetary and unit values resulting from CWB processing.
• BASE_SALARY, ELIG_SALARY, PREV_SAL, and NEW_SAL — salary baselines used in allocation and reporting.
• FULL_NAME and EMPLOYEE_NUMBER — worker identification attributes used in CWB reporting (N2, N3).
• PAY_PROPOSAL_ID and PAY_BASIS_ID — links to PER_PAY_PROPOSALS and PER_PAY_BASES respectively.
• ERROR_OR_WARNING_TEXT — diagnostic message captured during the post process.
• POSTED_RATING and PERFORMANCE_RATING — rating values carried through posting.
• PRIOR_FLEX1 through PROPOSED_FLEX30 — descriptive flexfield captures of prior, posted, and proposed segment values.

Common Use Cases and Queries

The primary use case is CWB post-process reconciliation and audit. Benefit administrators query this table to confirm what was posted for each worker, identify rows with errors or warnings, and reconcile proposed versus posted values.

• Plan-level status review: select rows by PL_ID and STATUS_CD to see which workers posted successfully and which remain flagged.
• Error triage: filter on ERROR_OR_WARNING_TEXT IS NOT NULL scoped to a specific PL_ID and BUSINESS_GROUP_ID to isolate failed workers.
• Worker-level history: join on PERSON_ID and PERSON_RATE_ID to trace a single worker's allocation across plans.
• Reporting by manager or hierarchy: use WS_MGR_ID and MANAGER_NAME together with FULL_NAME/EMPLOYEE_NUMBER for Compensation Workbench worksheets.

A representative pattern joins the detail to a person plan to reassemble the report:

SELECT d.FULL_NAME, d.EMPLOYEE_NUMBER, d.AMOUNT, d.AMOUNT_POSTED, d.STATUS_CD, d.ERROR_OR_WARNING_TEXT FROM BEN.BEN_CWB_RPT_DETAIL d WHERE d.PL_ID = :plan_id AND d.STATUS_CD = 'ERROR';

Because the table partitions its descriptive flexfields by state (prior vs. posted vs. proposed), reporting SQL frequently selects only the relevant trio of columns rather than all thirty slots.

Related Objects

The following objects are the most significant dependencies of BEN_CWB_RPT_DETAIL, based on documented foreign-key relationships:

• BEN_BENEFIT_ACTIONS — joined via BENEFIT_ACTION_ID; the benefit action governing the CWB processing row.
• BEN_CWB_PERSON_RATES — joined via PERSON_RATE_ID; the individual's rate and allocation record.
• BEN_CWB_PERSON_INFO — joined via GROUP_PER_IN_LER_ID; the person-in-plan/group info context.
• PER_PAY_PROPOSALS — joined via PAY_PROPOSAL_ID; proposed pay information resulting from CWB.
• PER_PAY_BASES — joined via PAY_BASIS_ID; the pay basis used in allocation and salary calculations.
• PER_ALL_PEOPLE_F — logically joined via PERSON_ID to resolve worker name, employee number, and assignment context.

Together these objects provide the reference and context data that transform the CWB post-process detail rows into actionable Compensation Workbench reporting.