Results for “cont_attribute1”

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

Overview

APPS.PER_JP_CONTACT_RELATIONSHIPS_V is a reporting view in the Oracle E-Business Suite Human Resources (PER) product. It is registered in the ETRM metadata with a status of VALID. Its documented purpose is to serve the JP Contact List folder and the JP Social Insurance and Income Tax on Dependent window — that is, the Japanese localization features that capture contact and dependent information required for Japanese statutory reporting and payroll processing.

Because the view carries the _V suffix, it is a denormalized, display-oriented construct rather than a transactional entity. It flattens the relationship between a person and a contact (or dependent), then joins to the person record so that descriptive attributes — name, sex, and date of birth — are available alongside the relationship data. The view performs code translation at query time via HR_GENERAL.DECODE_LOOKUP, returning both the stored lookup code and its translated meaning. This makes it convenient for folder-based forms and concurrent reports without requiring the caller to re-implement the lookup join.

Underlying Base Objects

The documented referenced base objects for this view are:

• PER_CONTACT_RELATIONSHIPS (synonym) — supplies the relationship rows: contact relationship ID, person ID, contact person ID, contact type, the CONT_ATTRIBUTE* and CONT_INFORMATION* descriptive flexfield columns, and the DATE_START/DATE_END and audit columns.
• PER_ALL_PEOPLE_F (synonym) — the date-tracked person record supplying LAST_NAME, FIRST_NAME, FULL_NAME, GLOBAL_NAME, LOCAL_NAME, SEX, DATE_OF_BIRTH, DATE_OF_DEATH, PER_INFORMATION18, PER_INFORMATION19, and the effective dates.
• PER_BUSINESS_GROUPS (view) — provides LEGISLATION_CODE, which identifies the legislative context of the record.
• FND_SESSIONS (synonym) — the session context, used to reflect the current application session.
• HR_GENERAL (package) — invoked for the DECODE_LOOKUP calls that translate the CONTACT_TYPE lookup and the SEX lookup into displayable values.

Key Columns

The view exposes a broad set of identifiers and descriptive attributes:

• Identifiers — CONTACT_RELATIONSHIP_ID, PERSON_ID, CONTACT_PERSON_ID, BUSINESS_GROUP_ID.
• Person attributes — LAST_NAME, FIRST_NAME, FULL_NAME, GLOBAL_NAME, LOCAL_NAME, PER_INFORMATION18, PER_INFORMATION19, DATE_OF_BIRTH, DATE_OF_DEATH.
• Relationship attributes — CONTACT_TYPE and its decoded form, DATE_START, DATE_END.
• Sex code column — the view exposes SEX (the stored code, e.g. M/F) together with its decoded equivalent obtained from the SEX lookup. This is the column most relevant to the search for sex_code: it should be understood as the person's gender code carried on PER_ALL_PEOPLE_F, not a column native to PER_CONTACT_RELATIONSHIPS.
• Derived age — a computed column applying MONTHS_BETWEEN between the earliest of date of death or effective date and the date of birth, divided by 12 and truncated to yield whole years.
• Descriptive flexfields — CONT_ATTRIBUTE1–CONT_ATTRIBUTE20 with CONT_ATTRIBUTE_CATEGORY, and CONT_INFORMATION1–CONT_INFORMATION20 with CONT_INFORMATION_CATEGORY.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus effective start and end dates.

Common Use Cases and Queries

The view is typically used where the JP localization requires reported dependent or contact data, for example when validating the relationship, sex, and age of a dependent before tax or social insurance submission. A representative query listing contacts for a person, including the sex code, follows:

• SELECT contact_relationship_id, person_id, contact_person_id, full_name, sex, date_of_birth, contact_type FROM per_jp_contact_relationships_v WHERE person_id = :p_person_id;

To identify dependents by legislative context:

• SELECT person_id, contact_person_id, full_name, sex FROM per_jp_contact_relationships_v WHERE legislation_code = 'JP' AND contact_type = :p_contact_type;

Where a report must present the translated meanings rather than codes, the decoded columns are selected directly, and the derived age column supports eligibility checks against statutory age thresholds. Because all descriptive flexfield segments are exposed, the view can also be used to surface JP-specific dependent attributes without additional joins.