Results for “contact_of”

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

Overview

APPS.XLE_LEGAL_CONTACTS_V is a reporting and integration view in the Oracle E-Business Suite Legal Entity Configurator (XLE) module. It presents the contacts associated with legal entities and establishments, resolving the underlying Oracle Trading Community Architecture (TCA) relationship model into a flat, consumable structure. The view derives its records from relationships in HZ_RELATIONSHIPS where the relationship code equals CONTACT_OF, which is the term most commonly searched when users investigate how contacts are attached to legal entities. In ETRM 12.1.1 and 12.2.2 the view is owned by APPS and is treated as a read-only reporting object; it does not store data itself but projects data held in the TCA and XLE schema.

Its principal role is to expose, for each legal entity or establishment, the list of persons acting as legal contacts together with their identifying attributes. This supports legal reporting, compliance extracts, and downstream integrations that require an authoritative list of contacts per registered entity.

Underlying Base Objects

The view is defined over several synonyms and one packaged function. The documented base objects are:

• HZ_PARTIES — supplies the contact person's identity, party name, party number, and fiscal code.
• HZ_PERSON_PROFILES — provides person-specific attributes such as the pre-name adjunct (title).
• HZ_RELATIONSHIPS — the central relationship table that links the contact person to the entity through the CONTACT_OF relationship code.
• HZ_ORG_CONTACTS — joins the relationship to the organization-contact assignment record.
• XLE_ENTITY_PROFILES — supplies the legal entity identifier and party for the LEGAL_ENTITY branch of the query.
• XLE_ETB_PROFILES — supplies the establishment identifier and party for the ESTABLISHMENT branch of the query.
• XLE_CONTACT_GRP — a PL/SQL package whose CONCAT_CONTACT_ROLES function concatenates the roles assigned to the contact and is invoked as the JOB_TITLE column.

The view is a UNION of two near-identical queries: one resolving contacts for legal entities and one resolving contacts for establishments. Both branches filter on active relationships using TRUNC(NVL(rel.end_date, SYSDATE)) > TRUNC(SYSDATE).

Key Columns

• ENTITY_ID — the legal entity ID (from XLE_ENTITY_PROFILES) or establishment ID (from XLE_ETB_PROFILES).
• ENTITY_TYPE — literal value LEGAL_ENTITY or ESTABLISHMENT, indicating which branch produced the row.
• ENTITY_PARTY_ID — the HZ_PARTIES party ID of the entity.
• CONTACT_PARTY_ID — the party ID of the contact person.
• CONTACT_NAME — the party name of the contact.
• CONTACT_LEGAL_ID — the fiscal code (JGZZ_FISCAL_CODE) of the contact.
• ROLE — literal value LEGAL CONTACT.
• TITLE — the person's pre-name adjunct.
• CONTACT_NUMBER — the party number of the contact.
• JOB_TITLE — the concatenated contact roles returned by XLE_CONTACT_GRP.CONCAT_CONTACT_ROLES.

Common Use Cases and Queries

Typical uses include verifying which person is designated as the legal contact of a legal entity, producing compliance extracts, and feeding downstream systems that require contact details per registered entity.

List all legal contacts for a given entity:

• SELECT entity_id, entity_type, contact_party_id, contact_name, contact_number, job_title FROM apps.xle_legal_contacts_v WHERE entity_type = 'LEGAL_ENTITY' AND entity_id = :entity_id;

Retrieve contacts across all establishments:

• SELECT entity_id, contact_name, contact_legal_id, title FROM apps.xle_legal_contacts_v WHERE entity_type = 'ESTABLISHMENT';

Find the entity associated with a known contact name:

• SELECT entity_id, entity_type, contact_name FROM apps.xle_legal_contacts_v WHERE contact_name LIKE '%NAME%';

Because the view relies on TRUNC(SYSDATE) in its predicates, query results always reflect contacts whose relationships are currently active; historical or ended relationships are excluded by design.