Results for “cont_information1”

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

Overview

PAY_KR_CONTACT_V is a PL/SQL view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) module. It is a Korea-localized (KR) view that returns contact data based on a combination of assignment_id and session_date. The view is classified as VALID and is delivered in both 12.1.1 and 12.2.2 ETRM environments.

Its role is narrowly scoped but deliberate: it exposes the "contact" records captured against a person's assignment, filtered to Korean statutory requirements, and joined to the current FND session so that date-effective resolution is automatic and session-consistent. Because effective dating depends on USERENV('SESSIONID') through FND_SESSIONS, the view is not a general-purpose data source; it is designed for form and concurrent-program logic that runs inside an active EBS session. The presence of the literal filters CONT_INFORMATION_CATEGORY = 'KR' and CONT_INFORMATION1 = 'Y' confirms that this view is intended to surface only the Korean contact information category, rather than all contact relationships. The user search term cont_information_category corresponds exactly to the column that drives this filter, making it the pivot of the view's meaning.

Underlying Base Objects

The documented base objects referenced by the view are: FND_SESSIONS (synonym), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PAY_KR_ENTRIES_PKG (package), PER_ASSIGNMENTS_F (view), PER_CONTACT_RELATIONSHIPS (synonym), and PER_PEOPLE_F (view). The primary SELECT joins PER_CONTACT_RELATIONSHIPS PCR to PER_ASSIGNMENTS_F PA on PCR.PERSON_ID = PA.PERSON_ID, to FND_SESSIONS FND via FND.SESSION_ID = USERENV('SESSIONID'), and to PER_PEOPLE_F PCR_PP on PCR_PP.PERSON_ID = PCR.CONTACT_PERSON_ID.

Effective dating is enforced at three points: the session effective date must fall within the assignment's effective range, within the contact relationship's derived date range (with a special "D" handling via CONT_INFORMATION9 that extends the end date to the year-end following a 12-month add), and within the contact person's effective range. The contact person's full name is retrieved from PER_PEOPLE_F, and the age is computed by PAY_KR_ENTRIES_PKG.CALC_AGE using the Korean national identifier and date of birth. HR_GENERAL.DECODE_LOOKUP supplies the decoded display value for CONTACT_TYPE.

Key Columns

• ROW_ID — the ROWID of the underlying contact relationship row, useful for direct updates.
• CONTACT_RELATIONSHIP_ID — primary key of PER_CONTACT_RELATIONSHIPS.
• ASSIGNMENT_ID / ASSIGNMENT_NUMBER / PERSON_ID — identify the assignment and person whose contact information is being retrieved.
• CONTACT_PERSON_ID — the person acting as the contact.
• CONTACT_TYPE / D_CONTACT_TYPE — the lookup code and its decoded up-to-80-character description.
• FULL_NAME / NATIONAL_IDENTIFIER / AGE — the contact's name, Korean identifier, and calculated age.
• CONT_INFORMATION_CATEGORY — the category that filters the view to 'KR'.
• CONT_INFORMATION1 — a flag (Y) that further restricts returned rows.
• CONT_INFORMATION2 … 14 — descriptive attributes (note the non-sequential listing: 6, 9 are handled internally, and 7/8/10/11 appear out of numeric order in the projection).

Common Use Cases and Queries

Typical uses include Korean payroll forms and concurrent programs that need the contacts declared for an employee's assignment within the session effective date. A minimal query is:

SELECT contact_relationship_id,
       assignment_id,
       full_name,
       d_contact_type,
       national_identifier,
       age
FROM   apps.pay_kr_contact_v
WHERE  assignment_id = :p_assignment_id;

Because the view already constrains by session and category, no additional effective-date predicate is required when invoked inside a standard EBS session. For debugging, administrators may inspect cont_information_category to confirm the KR filter, and use ROW_ID to trace back to PER_CONTACT_RELATIONSHIPS.