Search Results user_table_id




Overview
Explore in AI Chat

Overview

APPS.PQP_ASSIGNMENT_ATTRIBUTES_D is a reporting and inquiry view in the Oracle E-Business Suite (EBS) HRMS/Payroll schema, exposed in both Release 12.1.1 and 12.2.2. It presents assignment-level statutory and payroll attributes held in the PQP_ASSIGNMENT_ATTRIBUTES_F base table, together with resolved descriptive values for coded foreign keys. The "_D" suffix indicates a denormalized, display-oriented view: rather than returning raw identifiers, it resolves lookups, rate names, spinal points, user table references, and the updating user's name.

The view is primarily a query-only construct intended for reporting, concurrent program extraction, and integration payloads. Because the underline table PQP_ASSIGNMENT_ATTRIBUTES_F is date-tracked (it carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE), the view exposes those date-tracked rows directly and is therefore typically filtered by effective date in downstream queries. In the context of the user search term "user_table_id," the view is notable because it joins to PAY_USER_TABLES four times, exposing the USER_TABLE_ID values that back the car benefit rates and essential-car configuration on the assignment.

Underlying Base Objects

The documented base objects underlying the view are:

  • PQP_ASSIGNMENT_ATTRIBUTES_F (synonym) — the driving table, aliased AAT, which holds the assignment attribute rows.
  • PQP_VEHICLE_DETAILS (synonym) — joined three times (PVD1, PVD2, PVD3) for the primary company car, secondary company car, and private car.
  • PAY_USER_TABLES (synonym) — joined four times (UDT1–UDT4) to resolve the company car rates table, secondary car table, private car rates table, and private car essential table identifiers.
  • FND_USER_VIEW (view) — resolves LAST_UPDATED_BY to a user name.
  • HR_LOOKUPS (view) — resolves TP_IS_TEACHER against the PQP_GB_TEACHER_JOB_STATUS lookup type.
  • PAY_RATES (synonym) — resolves the safeguarded rate identifier to a rate name.
  • PER_SPINAL_POINTS (synonym) — resolves the safeguarded spinal point identifier to its descriptive point.
  • HR_API (package) — documented as a referenced base object, reflecting the HRMS API framework around the underlying table rather than a join predicate.

With the exception of the driving table, every join is an outer join (noted by the "(+)" operator), so attribute rows are retained even when the referenced car, user table, lookup, rate, or spinal point value is missing.

Key Columns

The four PAY_USER_TABLES joins reference the column USER_TABLE_ID on each alias (UDT1.USER_TABLE_ID, UDT2.USER_TABLE_ID, UDT3.USER_TABLE_ID, UDT4.USER_TABLE_ID) to resolve the car-related rate and essential tables. This is the element that matches the user's search term.

Common Use Cases and Queries

The view supports statutory-attribute reporting, pension and car-benefit audits, and integration extracts. A representative query retrieving current assignment attributes with resolved descriptions:

  • SELECT aa.assignment_attribute_id, aa.effective_start_date, aa.effective_end_date, aa.tp_safeguarded_grade, aa.tp_safeguarded_rate_name, aa.tp_safeguarded_spinal_point, aa.lgps_membership_number, aa.last_updated_by FROM apps.pqp_assignment_attributes_d aa WHERE TRUNC(SYSDATE) BETWEEN aa.effective_start_date AND NVL(aa.effective_end_date, TRUNC(SYSDATE)+1);
  • Filtering by contract type or work pattern for reconciliation against the HR assignment record.
  • Joining on ASSIGNMENT_ATTRIBUTE_ID back to the base table or to PER_ALL_ASSIGNMENTS_F for a full assignment picture.

Where the car-rate configuration is the focus, queries can inspect the resolved PAY_USER_TABLES rows opened by the USER_TABLE_ID joins. Because all secondary joins are outer, reports should apply NVL or null-checking on resolved descriptive columns. The view carries no Row Level Security of its own, so access is governed by grants on the APPS schema and by any security applied to the underlying PQP tables.