Results for “party_last_update_date”

50+ results




Overview
Explore in AI Chat

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

Overview

AR_CONTACTS_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite, classified under the Receivables (AR) product family. ETRM documentation records the object as VALID and describes it as applicable to Release 11.5, though in Oracle EBS 12.1.1 and 12.2.2 the view remains registered and is resolved against the higher-release Customer Model objects. Its purpose is to present a consolidated, denormalized read of customer contact information — combining contact identity, job title, mail stop, and a set of descriptive attributes — so that Receivables forms, reports, and integrations can retrieve contact details associated with a customer account, account site, or party without joining the underlying HZ tables individually. The single most relevant column for the user's search term "responsibility" is the derived RESPONSIBILITY column, which is produced by the lookup function ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING using the lookup type 'RESPONSIBILITY' against HZ_ORG_CONTACTS.JOB_TITLE_CODE.

Underlying Base Objects

According to the documented 12.2.2 view metadata, AR_CONTACTS_V references the following base objects:

The view is therefore a thin projection layer over the TCA (Trading Community Architecture) customer model, with the Receivables lookup package used to decode code values at runtime.

Key Columns

  • ROW_ID / CONTACT_ID — the row identifier and the underlying CUST_ACCOUNT_ROLE_ID.
  • CUSTOMER_ID — the HZ_CUST_ACCOUNTS identifier for the account to which the contact belongs.
  • ADDRESS_ID — the CUST_ACCT_SITE_ID linking the contact to a specific account site.
  • TITLE / TITLE_MEANING — the party name prefix and its decoded lookup meaning ('CONTACT_TITLE').
  • FIRST_NAME / LAST_NAME — substring-bounded name fields (40 and 50 bytes).
  • RESPONSIBILITY — derived by NVL(GET_LOOKUP_MEANING('RESPONSIBILITY', JOB_TITLE_CODE), JOB_TITLE); returns the decoded responsibility meaning when a matching lookup exists, otherwise the stored job title.
  • JOB_TITLE / JOB_TITLE_CODE — the raw job title text and the lookup code that drives the RESPONSIBILITY derivation.
  • MAIL_STOP, STATUS, ORIG_SYSTEM_REFERENCE, CONTACT_KEY — mail routing, active/inactive role status, source system reference, and the party customer key.
  • OBJECT_VERSION, LAST_UPDATE_DATE, CREATED_BY — standard audit and optimistic-locking columns.
  • ATTRIBUTE1–ATTRIBUTE22 — descriptive flexfield segments carried from HZ_CUST_ACCOUNT_ROLES.

Common Use Cases and Queries

A typical query retrieves contacts and their decoded responsibility for a given customer account:

SELECT contact_id, customer_id, address_id,
       title_meaning, first_name, last_name,
       job_title, job_title_code, responsibility,
       mail_stop, status
  FROM apps.ar_contacts_v
 WHERE customer_id = :p_customer_id
   AND status = 'A';

To locate all contacts holding a specific responsibility across accounts, filter on the derived column:

SELECT customer_id, first_name, last_name, responsibility
  FROM apps.ar_contacts_v
 WHERE responsibility = 'AP Manager';

Because RESPONSIBILITY is derived through ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING, queries that filter or order on it invoke the lookup function per row; on large result sets this is best constrained first by CUSTOMER_ID or by JOB_TITLE_CODE, then filtered on the decoded value. The view is also convenient for extracting the descriptive flexfield payload (ATTRIBUTE1–ATTRIBUTE22) alongside contact identity, and for integration extracts in which the external system requires the responsibility meaning rather than the stored lookup code.