Results for “per_cagr_entitlement_lines_d”

36 results




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

Overview

The PER_CAGR_ENTITLEMENT_LINES_D view belongs to the PER – Human Resources product family within Oracle EBS 12.1.1 and 12.2.2, and is owned by the APPS schema. It presents a descriptive, denormalized projection of the Collective Agreement (CAGR) entitlement lines defined by the PER_CAGR_ENTITLEMENT_LINES_F base table, enriching each line with decoded lookup values and related descriptive attributes.

The view is intended for reporting, integration and inquiry purposes rather than data maintenance. Each committed record from the transactional table is joined to grade spine, parent spine, spinal point step, eligibility profile and user information, producing readable codes rather than raw IDs. Notably, the cryptic lookup columns MANDATORY and STATUS in the base table are decoded through HR_GENERAL.DECODE_LOOKUP for the CAGR_MANDATORY and CAGR_STATUS lookup types, and exposed as MANDATORY_DESC and STATUS_DESC respectively. This decoding is central to the object's usefulness, and it explains why a search for status_desc surfaces this view.

Underlying Base Objects

Documented referenced base objects for the view are:

  • PER_CAGR_ENTITLEMENT_LINES_F (SYNONYM) – the transactional base table holding entitlement line records
  • PER_GRADE_SPINES_V (VIEW) – provides grade name (D_GRADE)
  • PER_PARENT_SPINES (SYNONYM) – provides parent spine name
  • PER_SPINAL_POINT_STEPS_V (VIEW) – joined three times to resolve the step, from-step and to-step spinal points
  • BEN_ELIGY_PRFL_V, BEN_PRTN_ELIG_PRFL_V, BEN_PRTN_ELIG_V (VIEWS) – eligibility profile chain used to derive the eligibility profile name
  • FND_USER (SYNONYM) – resolves the last-updating user
  • HR_GENERAL (PACKAGE) – supplies the DECODE_LOOKUP function that converts lookup codes to descriptions

All joins to the descriptive base objects are outer joins ((+) syntax), so an entitlement line is never dropped even when its referenced grade spine, spinal points, parent spine or eligibility profile is null. This makes the view safe for exhaustive listing.

Key Columns

Common Use Cases and Queries

The view is typically queried for entitlement-line listings, status monitoring and integration extracts where human-readable descriptions are required instead of coded values. A representative status-oriented query is:

  • SELECT cagr_entitlement_line_id, status_desc, mandatory_desc, grade_name, value
  • FROM apps.per_cagr_entitlement_lines_d
  • WHERE status_desc = 'Active'
  • AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Other common patterns include joining the view back to PER_CAGR_ENTITLEMENT_LINES_F on CAGR_ENTITLEMENT_LINE_ID to reconcile descriptions with underlying codes, filtering by ELIGIBLITY_PROFILE_NAME for eligibility audits, and extracting SPINAL_POINT, FROM_SPINAL_POINT and TO_SPINAL_POINT for pay-scale and progression analysis. Because all descriptive joins are outer joins, reports can be written without guarding against missing reference data.