Results for “third_party_payment”

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

Overview

PQP_PROFESSIONAL_BODY_TEMP_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a product of the PQP (Public Sector Payroll) module and exposes the set of base element types that were created from the Professional Body element template. In effect, it presents a denormalized, ready-to-query picture of each professional body element, combining the element type definition with the associated professional body organization, classification, and template extra information.

Because it is a view rather than a table, it carries no stored data of its own; it is a query-time projection over the PAY and HR base tables. This makes it suitable for reporting, data extraction, and lightweight integration scenarios where an implementer needs to enumerate professional body elements without navigating several underlying tables. Only records valid for the current session effective date are returned, since the session effective date is constrained between the element type effective start and end dates.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed through APPS synonyms: FND_SESSIONS, HR_ALL_ORGANIZATION_UNITS, HR_ORGANIZATION_INFORMATION, PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_TYPES_F, and PAY_ELEMENT_TYPE_EXTRA_INFO.

The join structure is as follows:

• PAY_ELEMENT_TYPES_F (PETF) supplies the element type definition, including element name, reporting name, description, legislation, processing type, and classification.
• PAY_ELEMENT_TYPE_EXTRA_INFO (PETEI) supplies template-specific attributes through its EEI_INFORMATION1 to EEI_INFORMATION4 columns, filtered by INFORMATION_TYPE = 'PQP_PROFESSIONAL_BODY_INFO'.
• HR_ALL_ORGANIZATION_UNITS (HOU) provides the professional body name, matched by converting EEI_INFORMATION1 to the organization ID.
• HR_ORGANIZATION_INFORMATION (HOI) restricts organizations to those whose context is 'CLASS' with value 'PB' (professional body).
• PAY_ELEMENT_CLASSIFICATIONS (PEC) provides the human-readable classification name.
• FND_SESSIONS (SES) supplies the session effective date used to filter the element type version returned.

Key Columns

• ELEMENT_TYPE_ID – Primary identifier of the element type; the key used to join to other payroll objects.
• BUSINESS_GROUP_ID – Business group that owns the element type.
• LEGISLATION_CODE – Legislation the element applies to.
• CLASSIFICATION_ID / CLASSIFICATION_NAME – Element classification and its descriptive name.
• PROCESSING_TYPE – How the element is processed during payroll runs.
• ELEMENT_NAME / REPORTING_NAME / DESCRIPTION – Standard element type identifiers.
• ORGANIZATION_ID – Organization ID derived from EEI_INFORMATION1.
• PROFESSIONAL_BODY_NAME – Organization unit name of the professional body (from EEI_INFORMATION1).
• PROFESSIONAL_BODY_LEVEL_BAL – Professional body level (from EEI_INFORMATION2).
• OVERRIDE_AMOUNT – Override amount (from EEI_INFORMATION3).
• THIRD_PARTY_PAYMENT – Third-party payment indicator (from EEI_INFORMATION4).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE – Standard audit columns.

Common Use Cases and Queries

The view is typically used to list professional body elements and their configured attributes, to reconcile element template setup, or to drive downstream reporting on professional body deductions. A representative query follows:

• SELECT element_name, professional_body_name, professional_body_level_bal, override_amount, third_party_payment FROM pqp_professional_body_temp_v ORDER BY element_name;
• Filter by legislation or business group to scope the output for a specific payroll: WHERE legislation_code = :legislation AND business_group_id = :bg_id.
• Join to payroll results or run results on element_type_id to analyze amounts processed against each professional body element.

Because the view is session-effective-date sensitive, queries executed from different sessions may return different element type versions when multiple effective-dated rows exist.