Results for “person_pre_name_adjunct”

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

Overview

WSH_CARRIER_CONTACTS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped as part of the WSH (Shipping Execution) product. It is a reporting and integration construct rather than a transactional entity: it exposes the contact persons associated with carriers (freight organizations) that participate in the shipping and transportation process. Carriers are modeled in Oracle EBS as organizations held in the Trading Community Architecture (TCA) registry, and their contact personnel are stored as party relationships. The view flattens that relationship model into a shape suitable for direct lookup — carrier identifier, contact party identifier, the person name components, and an active indicator.

Because the view is defined entirely over TCA synonyms (HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS), it is consistent across the 12.1.1 and 12.2.2 releases. No Online Patching editioning view wraps it; it is a simple SELECT view that resolves against the run-time TCA data in the same way in both releases. This makes it safe for use in custom reports, concurrent programs, and external integrations that need carrier contact information without navigating TCA internals.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents three referenced base objects, all exposed as APPS synonyms: HZ_ORG_CONTACTS, HZ_PARTIES, and HZ_RELATIONSHIPS. The view text confirms the join logic:

• HZ_PARTIES (HP) — the subject/contact side of the relationship, supplying the person's name and status.
• HZ_RELATIONSHIPS (HR) — the party-to-party relationship record linking the carrier to the contact, supplying PARTY_ID, OBJECT_ID, and SUBJECT_ID.
• HZ_ORG_CONTACTS — used only in a NOT EXISTS filter, excluding contacts that are assigned to a party site.

The relationship filter is the core of the view's semantics: SUBJECT_TABLE_NAME and OBJECT_TABLE_NAME are both constrained to 'HZ_PARTIES', and DIRECTIONAL_FLAG is fixed to 'F' (forward direction), so only forward party relationships between two parties are returned. The NOT EXISTS clause removes any relationship whose PARTY_RELATIONSHIP_ID also appears in HZ_ORG_CONTACTS with a non-null PARTY_SITE_ID, thereby excluding site-level contacts and leaving organization-level carrier contacts.

Key Columns

The documented column list is: RELATION_PARTY_ID, CARRIER_ID, CONTACT_PERSON_ID, PERSON_PRE_NAME_ADJUNCT, PERSON_FIRST_NAME, PERSON_LAST_NAME, and ACTIVE. Note that the view text aliases the TCA columns HR.PARTY_ID as RELATION_PARTY_ID, HR.OBJECT_ID as CARRIER_ID, and HR.SUBJECT_ID as CONTACT_PERSON_ID, while HP.PERSON_PRE_NAME_ADJUNCT, HP.PERSON_FIRST_NAME, and HP.PERSON_LAST_NAME carry the contact's name components unchanged. The HP.STATUS column is exposed as ACTIVE.

• RELATION_PARTY_ID — the TCA party identifier of the relationship subject (the contact party).
• CARRIER_ID — the TCA party identifier of the carrier organization (from OBJECT_ID).
• CONTACT_PERSON_ID — the party identifier of the contact person (from SUBJECT_ID).
• PERSON_PRE_NAME_ADJUNCT / PERSON_FIRST_NAME / PERSON_LAST_NAME — name components for display and address formatting.
• ACTIVE — the TCA party status value; the TCA convention is 'A' for active and 'I' for inactive, so consumers typically filter on this column.

Common Use Cases and Queries

Typical uses include populating carrier contact lookups in shipping reports, validating contact data before freight tendering integrations, and reconciling carrier contact lists for data-quality audits. A basic listing for a specific carrier follows:

SELECT contacts.carrier_id,
       contacts.contact_person_id,
       contacts.person_first_name,
       contacts.person_last_name,
       contacts.person_pre_name_adjunct,
       contacts.active
FROM   apps.wsh_carrier_contacts_v contacts
WHERE  contacts.carrier_id = :carrier_id
AND    contacts.active = 'A'
ORDER BY contacts.person_last_name, contacts.person_first_name;

Joining to HZ_PARTIES on the carrier party identifier supplies the carrier organization name, while joining on CARRIER_ID to WSH_CARRIERS (via its TCA party reference) links the contacts to carrier records used on shipments. Because the view filters out site-assigned contacts, code that requires a specific contact address should query HZ_ORG_CONTACTS directly rather than relying on this view. Requesters should also account for TCA party status when building outbound messages, since rows marked inactive remain present in the view.