Results for “pcr_pp”

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

Overview

APPS.PAY_KR_CONTACT_V is a Korean localization (KR) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes contact relationship information tied to employee assignments. It is designed to surface the dependants and other contacts registered against an employee for Korean statutory reporting requirements, most notably family-related deductions and national identifier (resident registration number) based reporting. The view joins the contact relationship infrastructure in Oracle HRMS to current assignment and person records, applying effective-dating through FND_SESSIONS so that results reflect the user's current effective date.

The view returns only records where the contact information category is 'KR' and where cont_information1 equals 'Y', meaning the contact has been flagged as active/relevant for Korean processing. In the context of reporting and integration, the view is typically consumed by Korean payroll and year-end reporting processes, and it also supports the pcr_pp alias used within the view for person records.

Underlying Base Objects

The documented base objects referenced by the view are:

• FND_SESSIONS (SYNONYM) — supplies the session context and the effective_date used throughout the view's effective-dating predicates.
• PER_CONTACT_RELATIONSHIPS (SYNONYM) — aliased as pcr, the primary driver of the view, holding the contact relationship and the cont_information1–14 flexfields.
• PER_ASSIGNMENTS_F (VIEW) — aliased as pa, providing assignment_id, assignment_number, and person_id for the employee.
• PER_PEOPLE_F (VIEW) — aliased as pcr_pp, providing the contact person's full_name and national_identifier.
• HR_GENERAL (PACKAGE) — used for DECODE_LOOKUP to translate the contact type into a display value.
• HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE) — HRMS utilities supporting name resolution and security.
• PAY_KR_ENTRIES_PKG (PACKAGE) — supplies the CALC_AGE function used to derive the contact's age.

Key Columns

• ROW_ID — the rowid of the underlying contact relationship record.
• CONTACT_RELATIONSHIP_ID — unique identifier for the contact relationship.
• ASSIGNMENT_ID / ASSIGNMENT_NUMBER — the employee's assignment identifiers.
• PERSON_ID — the employee's person identifier (from the assignment).
• CONTACT_PERSON_ID — the contact/dependant person identifier.
• CONTACT_TYPE / D_CONTACT_TYPE — the lookup code and its decoded display value (via DECODE_LOOKUP on 'CONTACT').
• FULL_NAME, NATIONAL_IDENTIFIER — the contact's name and Korean resident registration number.
• AGE — derived by PAY_KR_ENTRIES_PKG.CALC_AGE from the national identifier, date of birth, and effective date.
• CONT_INFORMATION_CATEGORY and CONT_INFORMATION1–14 — the descriptive flexfield values that encode Korean-specific contact attributes.
• OBJECT_VERSION_NUMBER — optimistic locking version column.

Common Use Cases and Queries

The view is primarily used for Korean dependant and contact reporting, where the age and national identifier of each registered contact must be produced against the current effective date. A typical query lists contacts for a given employee:

SELECT assignment_number, full_name, d_contact_type, age
FROM   apps.pay_kr_contact_v
WHERE  person_id = :p_person_id;

The effective date is controlled by FND_SESSIONS, which is populated during an EBS session; queries executed outside an initialized session may return no rows. Note the special handling of cont_information9 = 'D', which extends the date_end by one year (truncated to the start of the year) before the effective-date check, reflecting a Korean-specific expiry rule for certain contact types. Because results depend on session effective_date and HR security, the view is best queried from within the EBS application tier or a properly initialized session.