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 theirMEANINGvalues.PAY_RATES(synonym) — suppliesPR.NAME, exposed asTP_SAFEGUARDED_RATE_NAME.PAY_USER_TABLES(synonym) — resolved four times to obtainUSER_TABLE_NAMEfor company car rate, secondary table, private car rate, and private car essential user tables.PER_SPINAL_POINTS(synonym) — suppliesPSP.SPINAL_POINT, exposed asTP_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:
- Identity and dates:
ASSIGNMENT_ATTRIBUTE_ID,ASSIGNMENT_ID,BUSINESS_GROUP_ID,EFFECTIVE_START_DATE,EFFECTIVE_END_DATE, and the standard audit columns (CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,OBJECT_VERSION_NUMBER). - Teachers' pension attributes:
TP_IS_TEACHERflags whether the assignment is treated as a teacher; companion columnsTP_SAFEGUARDED_GRADE,TP_SAFEGUARDED_GRADE_ID,TP_SAFEGUARDED_RATE_TYPE,TP_SAFEGUARDED_RATE_ID,TP_SAFEGUARDED_RATE_NAME,TP_SAFEGUARDED_SPINAL_POINT_ID,TP_SAFEGUARDED_SPINAL_POINT,TP_ELECTED_PENSION,TP_FAST_TRACK, andTP_HEADTEACHER_GRP_CODEcapture safeguarded and election details. - Vehicle information: primary, secondary, and private car registration, make, and model; fuel benefit and capital/private contribution amounts; Class 1A values; and calculation method meanings.
- Contract and work pattern:
CONTRACT_TYPE,WORK_PATTERN, andSTART_DAY. - Descriptive flexfield:
AAT_ATTRIBUTE_CATEGORYandAAT_ATTRIBUTE1throughAAT_ATTRIBUTE15.
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_pointFROM apps.pqp_assignment_attributes_vWHERE business_group_id = :p_bg_idAND 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, modelFROM apps.pqp_assignment_attributes_vWHERE effective_end_date = hr_api.g_effective_end_dateAND 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.
-
View of table PQP_ASSIGNMENT_ATTRIBUTES_F.
APPS.PQP_ASSIGNMENT_ATTRIBUTES_V·↳ HR_API·↳ HR_LOOKUPS·↳ PAY_RATES·Explore PQP module →
-
View of table PQP_ASSIGNMENT_ATTRIBUTES_F.
APPS.PQP_ASSIGNMENT_ATTRIBUTES_V·↳ FND_GLOBAL·↳ HR_API·↳ HR_LOOKUPS·Explore PQP module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.PAY_RATES 12.1.1
-
SYNONYM: APPS.PAY_RATES 12.2.2
-
eTRM - PQP Tables and Views 12.1.1
Entity used to store the information types for Vehicle Repository Extra information.
-
eTRM - PQP Tables and Views 12.2.2
Entity used to store the information types for Vehicle Repository Extra information.
-
VIEW: APPS.HR_LOOKUPS 12.1.1
-
VIEW: APPS.HR_LOOKUPS 12.2.2
-
eTRM - PQP Tables and Views 12.1.1
Entity used to store the information types for Vehicle Repository Extra information.
-
eTRM - PQP Tables and Views 12.2.2
Entity used to store the information types for Vehicle Repository Extra information.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person