Results for “submit_attribute”

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

Overview

APPS.BEN_PNDG_WRKFLW_APPRVLS_V is a supplemental view in the Oracle E-Business Suite Benefits (BEN) module, present in both Release 12.1.1 and 12.2.2. Its registered FND Design Data name is BEN.BEN_PNDG_WRKFLW_APPRVLS_V, and its status is VALID. Oracle classifies the object as a "supplementary view used to simplify forms coding," and the documented metadata explicitly carries Oracle's standard warning that customers should not query or alter data through this view because its definition may change dramatically in subsequent minor or major releases. In practice, the view exposes pending Benefits workflow approval records — the values that have been proposed for an employee's benefits election or rate and are awaiting approval — together with their associated workflow status. It is therefore relevant to reporting and integration scenarios that need to surface in-flight benefits approvals, but it is not a sanctioned public interface. The user search term "bnft_typ_meaning" maps directly to the BNFT_TYP_MEANING column documented in this view, which carries the decoded (meaning) form of the benefits type associated with the pending approval row.

Underlying Base Objects

Per the documented dependency list, the view is defined over the following objects, all resolved through APPS synonyms:

• HR_API_TRANSACTION_STEPS (SYNONYM)
• HR_API_TRANSACTION_VALUES (SYNONYM)
• WF_ITEM_ACTIVITY_STATUSES (SYNONYM)
• WF_ITEM_ATTRIBUTE_VALUES (SYNONYM)
• WF_PROCESS_ACTIVITIES (SYNONYM)

The design pattern follows the standard Oracle HR/Benefits datetracked API-transaction model. HR_API_TRANSACTION_STEPS and HR_API_TRANSACTION_VALUES hold the staged, not-yet-applied transactional values (the proposed election or rate information) that originate from the Benefits forms and are queued for processing. The Workflow objects — WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ATTRIBUTE_VALUES, and WF_PROCESS_ACTIVITIES — supply the approval routing and status context, allowing the view to identify which of those pending values remain at an approval activity rather than having completed. The join effectively correlates a pending benefits transaction with its current workflow activity status. The metadata confirms that the view is not referenced by any other database object; it is a terminal, presentation-oriented object.

Key Columns

The view exposes seventeen columns. The identifying keys are PERSON_ID (documented as a foreign key to PER_PEOPLE_F) and ELIG_PER_ELCTBL_CHC_ID, which ties the row to a specific eligibility/electable choice record in the benefits model. Monetary and rate data are carried by BNFT_AMT, RT_VAL, and LIMIT_RT_VAL. Effective and rate dates are represented by ENRT_CVG_STRT_DT, RT_STRT_DT, and RT_END_DT, while PL_OPT_NAME and JUSTIFICATION provide plan option and explanatory text. The decoded/meaning columns — the class most relevant to the "bnft_typ_meaning" search — are RT_UOM_MEANING, BNFT_UOM_MEANING, ACTY_REF_PERD_MEANING, and BNFT_TYP_MEANING, each VARCHAR2(2000), alongside FREQUENCY. BNFT_TYP_MEANING is the translated display value of the benefits type for the pending approval. Standard WHO audit columns CREATION_DATE and CREATED_BY (foreign key to FND_USER.USER_ID) complete the structure.

Common Use Cases and Queries

Typical uses include Benefits administration dashboards that list elections awaiting workflow approval, troubleshooting of stalled approvals, and reconciliation extracts that must show proposed versus approved values. Because the meaning columns are pre-decoded, reporting can group by BNFT_TYP_MEANING without joining to lookup tables. A representative query is:

• SELECT person_id, bnft_typ_meaning, pl_opt_name, bnft_amt, rt_val, frequency, rt_strt_dt, rt_end_dt FROM apps.ben_pndg_wrkflw_aprvls_v WHERE person_id = :p_person_id;
• SELECT bnft_typ_meaning, COUNT(*) FROM apps.ben_pndg_wrkflw_aprvls_v GROUP BY bnft_typ_meaning;

Given the documented Oracle warning, consumers should treat the view as informational only, avoid DML, and validate column stability before promoting any query into a permanent interface or production report.