Results for “pqp_assignment_attributes_v”

32 results




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

Overview

The view APPS.PQP_ASSIGNMENT_ATTRIBUTES_V belongs to the PQP (Public Sector Payroll) product family within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents the effective-dated assignment-level attribute records used by UK public sector payroll processing, exposing the contents of the base table PQP_ASSIGNMENT_ATTRIBUTES_F together with descriptive information denormalized from related vehicle, lookup, rate, user table, and spinal point sources. The view is the primary reporting interface over the assignment attribute entity, and it is the object that surfaces fields such as TP_IS_TEACHER, which governs teachers' pension scheme treatment within an assignment.

Because the view joins lookup meanings and descriptive names, it removes the need for report authors and integrators to perform manual joins to decode lookup codes, vehicle details, or rate identifiers. It supports both ad hoc reporting through BI Publisher and Discoverer, and programmatic access through PL/SQL or concurrent programs.

Underlying Base Objects

The view is defined primarily over the synonym PQP_ASSIGNMENT_ATTRIBUTES_F, which supplies the effective-dated assignment attribute rows. The ETRM metadata documents the following referenced objects:

  • PQP_ASSIGNMENT_ATTRIBUTES_F (synonym) — the driving table containing the base attributes.
  • PQP_VEHICLE_DETAILS (synonym) — joined three times to resolve primary, secondary, and private company/private car registration, make, model, engine capacity, and fuel type.
  • HR_LOOKUPS (view) — accessed via the lookup mechanism to translate calculation method codes into their MEANING values.
  • PAY_RATES (synonym) — supplies PR.NAME, exposed as TP_SAFEGUARDED_RATE_NAME.
  • PAY_USER_TABLES (synonym) — resolved four times to obtain USER_TABLE_NAME for company car rate, secondary table, private car rate, and private car essential user tables.
  • PER_SPINAL_POINTS (synonym) — supplies PSP.SPINAL_POINT, exposed as TP_SAFEGUARDED_SPINAL_POINT.
  • HR_API (package) — the business logic layer associated with the underlying entity.

All joins are performed within the APPS schema, and the view returns the ROWID of the base table row along with the surrogate key ASSIGNMENT_ATTRIBUTE_ID.

Key Columns

The view exposes the full assignment attribute column set plus derived descriptive columns. Principal columns include:

Common Use Cases and Queries

Typical uses include reporting teacher pension eligibility, auditing safeguarded grade assignments, and reconciling company car benefits against payroll calculations. Because the view is effective-dated, queries must always constrain on the effective dates to isolate current records.

For example, to identify assignments flagged as teachers for a given date:

  • SELECT assignment_id, tp_is_teacher, tp_safeguarded_grade, tp_safeguarded_spinal_point
  • FROM apps.pqp_assignment_attributes_v
  • WHERE business_group_id = :p_bg_id
  • AND tp_is_teacher = 'Y'
  • AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

To report company car details alongside their calculated fuel benefit:

  • SELECT assignment_id, company_car_calc_method, primary_car_fuel_benefit,
  •        registration_number, make, model
  • FROM apps.pqp_assignment_attributes_v
  • WHERE effective_end_date = hr_api.g_effective_end_date
  • AND private_car = 'N';

Integrations typically extract these rows into external payroll or pension interfaces, joining on ASSIGNMENT_ATTRIBUTE_ID to maintain referential integrity with the base table.