Results for “access_cd”

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

Overview

BEN_CWB_PERSON_TASKS is a table within the BEN — Advanced Benefits product module of Oracle E-Business Suite, documented in ETRM 12.2.2 and valid in the 12.1.1 / 12.2.2 release line. The table stores CWB Person Tasks — that is, the work-list or task assignments generated by the Compensation Workbench (CWB) process for individual persons participating in a benefits or compensation enrollment cycle. Each row links a person (through the group person-in-learner identifier) to a specific task definition, and records the state, access rights, and lifecycle timestamps for that assignment.

Because the object is a table (not a view or API), it is a persistent transactional store rather than a derived reporting structure. Its documented relationship classification, mined heuristically from foreign-key structure, is standalone; there is no parent-child dependency chain expressed in the catalog. As a modeling suggestion, this pattern resembles a link entity in Data Vault terms — a junction that resolves the many-to-many association between a person enrolment and a task definition — though the standalone classification means it should be treated as an independent subject area rather than as a satellite attached to a single hub.

Key Information Stored

The documented physical schema contains 14 columns. The primary key is BEN_CWB_PERSON_TASKS_PK, a composite unique index over GROUP_PER_IN_LER_ID and TASK_ID. This composite key is the only documented business-key candidate, and it also serves as the surrogate row identifier for the table.

• GROUP_PER_IN_LER_ID — the group person-in-learner identifier; identifies the person for whom the task was generated. Part of the composite primary key.
• TASK_ID — the identifier of the CWB task definition assigned to that person. Part of the composite primary key.
• GROUP_PL_ID — the associated group plan identifier, tying the task assignment to a benefits plan context.
• LF_EVT_OCRD_DT — the date the underlying life event occurred, where the task was triggered by a life-event change.
• STATUS_CD — the current status of the person task, indicating whether it is open, complete, or otherwise dispositioned.
• ACCESS_CD — the access code that governs whether the task may be viewed or acted upon.
• TASK_LAST_UPDATE_DATE and TASK_LAST_UPDATE_BY — the timestamp and user identifier for the most recent change to the task itself, distinct from row-level audit.
• OBJECT_VERSION_NUMBER — the optimistic locking counter used by the Oracle Applications framework to detect concurrent modification.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO-column audit set capturing row creation and last modification.

Common Use Cases and Queries

Typical usage centres on reporting outstanding or completed compensation workbench tasks per participant, and on reconciling task status against life-event occurrence dates.

• Identifying all open tasks for a person: SELECT task_id, status_cd, lf_evt_ocrd_dt FROM ben.ben_cwb_person_tasks WHERE group_per_in_ler_id = :p_id AND status_cd = :open_cd;
• Auditing tasks updated after a cutoff: SELECT group_per_in_ler_id, task_id, task_last_update_date, task_last_update_by FROM ben.ben_cwb_person_tasks WHERE task_last_update_date >= :cutoff;
• Aggregating task volume by status and plan for a cycle: SELECT group_pl_id, status_cd, COUNT(*) FROM ben.ben_cwb_person_tasks GROUP BY group_pl_id, status_cd;

Because OBJECT_VERSION_NUMBER is populated, any programmatic update must supply the current value to avoid a concurrency conflict.

Related Objects

The catalog documents BEN_CWB_PERSON_TASKS as standalone, so no explicit foreign keys are recorded. The following related objects are the most significant by convention and by the columns present:

• BEN_CWB_PERSON_TASKS_PK — the primary-key index enforcing uniqueness of (GROUP_PER_IN_LER_ID, TASK_ID).
• BEN_CWB_TASKS — the CWB task definition referenced through TASK_ID.
• Person/participant tables in the BEN schema keyed by GROUP_PER_IN_LER_ID.
• Benefits plan tables keyed by GROUP_PL_ID.
• Life-event tables providing the value stored in LF_EVT_OCRD_DT.