Results for “oe_address”

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

Overview

PAY_JP_DEF_DEP_OE_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product family. Per Oracle's ETRM documentation (12.2.2), the object is defined exclusively for the Japanese localization, serving as the reporting and integration layer for dependent and other-eligible (OE) contact information captured during assignment action processing. The view returns records associated with the action context type 'AAP' (Assignment Action Processing) and the action information category 'JP_DEF_DEP_OE', meaning it surfaces the Japanese-specific dependent and other-eligible declarations recorded as action information on an assignment action. It is the documented, queryable interface over a DML view, presenting canonical (typed) rather than raw attribute values so that downstream reports, extracts, and interfaces can consume the data without performing their own datatype conversion.

Underlying Base Objects

The view is defined over three documented referenced objects:

• PAY_JP_DEF_DEP_OE_DML_V (VIEW) — the immediate source of all rows. PAY_JP_DEF_DEP_OE_V is a projection and filtering layer on top of this DML view, restricting output to ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_DEF_DEP_OE'.
• FND_DATE (PACKAGE) — invoked as FND_DATE.CANONICAL_TO_DATE on the stored date attributes, converting canonical date strings into proper DATE values for DATE_OF_BIRTH, DATE_OF_DEATH, and CHANGE_DATE.
• FND_NUMBER (PACKAGE) — invoked as FND_NUMBER.CANONICAL_TO_NUMBER on stored numeric identifiers, converting canonical number strings for CONTACT_EXTRA_INFO_ID, CEI_OBJECT_VERSION_NUMBER, CONTACT_RELATIONSHIP_ID, OE_CONTACT_RELATIONSHIP_ID, and OE_CONTACT_RELATIONSHIP_ID_O.

Because the view derives from a DML view and applies datatype conversion functions, it is intended for read and reporting access rather than direct maintenance; the underlying action information records are maintained through the standard assignment action framework.

Key Columns

• ROW_ID, ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER — primary identification and optimistic locking attributes for the action information row.
• ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, EFFECTIVE_DATE — the assignment action and assignment context, with the effective date of the declaration.
• ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, STATUS — classification and lifecycle state; the view is pre-filtered to 'AAP' and 'JP_DEF_DEP_OE'.
• CONTACT_RELATIONSHIP_ID, CONTACT_EXTRA_INFO_ID, CEI_OBJECT_VERSION_NUMBER — keys linking to the contact relationship and contact extra information entities.
• LAST_NAME_KANA, FIRST_NAME_KANA, LAST_NAME, FIRST_NAME — dependent or eligible person's name, including Japanese phonetic kana readings.
• CONTACT_TYPE, DATE_OF_BIRTH, DATE_OF_DEATH, ADDRESS — relationship type and personal detail, with dates returned as true DATE values.
• CHANGE_DATE, CHANGE_REASON — when and why the declaration changed.
• OCCUPATION, OCCUPATION_O — occupation and its "other" (O) counterpart, the column referenced by the search term "occupation_o".
• OE_CONTACT_RELATIONSHIP_ID, OE_FULL_NAME, OE_CONTACT_TYPE, OE_ADDRESS, OE_CONTACT_RELATIONSHIP_ID_O — the other-eligible contact's identifying and descriptive attributes.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical usage includes Japanese dependent registration reporting, audit extracts of declarations per assignment action, and integration feeds into external payroll or benefits systems. A frequently used pattern is to filter on an action or assignment and select the occupation fields, including OCCUPATION_O.

• Retrieve declarations for a specific assignment action:

SELECT assignment_action_id, assignment_id, effective_date,
       last_name, first_name, contact_type,
       occupation, occupation_o
FROM   apps.pay_jp_def_dep_oe_v
WHERE  assignment_action_id = :p_action_id;

• Report occupations, including the "other" value, for a given assignment:

SELECT assignment_id, effective_date, last_name, first_name,
       occupation, occupation_o, change_date
FROM   apps.pay_jp_def_dep_oe_v
WHERE  assignment_id = :p_assignment_id
ORDER  BY effective_date;

• Audit recently changed declarations using the audit columns and CHANGE_REASON.
• Join OE_CONTACT_RELATIONSHIP_ID to the relevant contact relationship entity to resolve the other-eligible contact's full details.

Oracle Proprietary, Confidential Information.