Results for “as_contacts_v”

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

Overview

AS_CONTACTS_V is a Sales Foundation (AS) view that presents contact information maintained in Oracle EBS. It consolidates contact records drawn from the Receivables contact tables and enriches them with decoded lookup meanings and the associated customer identification. The view is described in the ETRM metadata simply as "Contacts view," and is documented as not implemented within the reference database instance, meaning it is a seeded, shipped view rather than a customer-specific database object.

Its principal role is to provide a reporting and integration surface for contact data used across Sales Foundation, Order Management, Receivables, and CRM-adjacent flows. Because the view resolves codes into descriptive lookup meanings and joins to RA_CUSTOMERS, consumers can retrieve human-readable contact records without reproducing the decoding and join logic themselves. This is particularly relevant given the user's search term "managed_by," which corresponds to the MANAGED_BY column of RA_CONTACTS exposed directly by this view.

Underlying Base Objects

Although the ETRM metadata records no referenced base objects, the view text defines the actual dependency set. The primary driving table is RA_CONTACTS, aliased CONT1. A self-join to RA_CONTACTS, aliased CONT2, supplies the referenced contact-manager or related-person name fields (CONT2.FIRST_NAME, CONT2.LAST_NAME). RA_CUSTOMERS, aliased CUST, contributes CUSTOMER_NAME and CUSTOMER_NUMBER.

Lookup decoding is performed against two lookup sources: AS_LOOKUPS is used three times (ASLKP1, ASLKP2, ASLKP4) and AR_LOOKUPS four times (ARLKP1, ARLKP2, ARLKP3, ARLKP5). These joins translate stored codes into MEANING values. For example, ARLKP1 decodes the TITLE, and the remaining lookup aliases decode other coded attributes such as roles, status, or language-related values. The join predicate shown (CONT1.TITLE = ARLK...) confirms that decoding is keyed on the coded column with an appropriate lookup type restriction. The view therefore sits directly over the Receivables contact and customer model, adding lookup resolution and a related-contact join.

Key Columns

The view exposes the full RA_CONTACTS column set plus decoded and joined attributes. Central identifiers include CONTACT_ID, CONTACT_KEY, CONTACT_NUMBER, CUSTOMER_ID, ADDRESS_ID, MAILING_ADDRESS_ID, and ORIG_SYSTEM_REFERENCE (the source-system key used for integration and matching).

• MANAGED_BY — the column matching the user's search; references the manager responsible for the contact record.
• CONT2.FIRST_NAME / CONT2.LAST_NAME — the name of the joined contact (for example the managing contact).
• MEANING columns (ARLKP, ASLKP) — decoded values for TITLE, status, role, and similar coded fields.
• DECISION_MAKER_FLAG, PRIMARY_ROLE, RANK, REFERENCE_USE_FLAG — contact qualification and prioritization attributes.
• CUSTOMER_NAME, CUSTOMER_NUMBER — customer context from RA_CUSTOMERS.
• ATTRIBUTE1 through ATTRIBUTE25 and ATTRIBUTE_CATEGORY — descriptive flexfield content.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include contact reporting by customer, contact-manager relationship analysis, and reconciliation of contact records during data migration. Because MANAGED_BY is exposed, queries commonly filter or group contacts by their managing contact, joining the CONT2 name columns to display the manager. A representative query is:

SELECT contact_id, contact_number, first_name, last_name, managed_by, meaning, customer_name, customer_number FROM as_contacts_v WHERE managed_by IS NOT NULL ORDER BY customer_name, last_name;

Another common pattern is to restrict to decision makers or a specific customer account:

SELECT contact_id, contact_number, primary_role, decision_maker_flag FROM as_contacts_v WHERE customer_id = :p_customer_id AND decision_maker_flag = 'Y';

The view is suitable for read-only reporting; as with all EBS views, direct DML should not be performed, and updates must target the underlying base tables through supported APIs.