Results for “party_relationship”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AST_SALES_LEAD_CONTACTS_V is a TeleSales (AST) reporting view owned by the APPS schema and validated in Oracle EBS 12.1.1 and 12.2.2. It presents the contact-level detail for sales leads: each row links a sales lead to a contact party, that party's role on the lead, associated phone and e-mail contact points, organizational job information, and the underlying party relationship. The view is a denormalized, read-only projection intended for inquiry, concurrent-program extracts, and integration interfaces that require lead-contact information without joining the base tables directly.
The object is significant for the search term lead_contact_role because the role of each contact is exposed through CONTACT_ROLE_CODE and its decoded, user-facing value MEANING (aliased from AS_LOOKUPS as ROLE_LKUP). Consumers can therefore report or filter on lead contact roles without decoding lookups themselves.
Underlying Base Objects
The view is defined over seven documented base objects. The driving table is AS_SALES_LEAD_CONTACTS (referenced as the synonym LEAD_CONT), which supplies the lead-contact intersection records. Supporting objects are:
HZ_PARTIES(PARTY_CONT) joined onPARTY_ID = REL.SUBJECT_ID, providing the contact's first and last name.HZ_RELATIONSHIPS(REL), joined onLEAD_CONT.CONTACT_PARTY_ID = REL.PARTY_IDandLEAD_CONT.CUSTOMER_ID = REL.OBJECT_ID, supplying relationship identifiers and subject/object party keys.HZ_ORG_CONTACTS(ORG_CONT), supplying job title and job title code for organizational contacts.HZ_CONTACT_POINTSjoined twice —PHONEonLEAD_CONT.PHONE_ID = PHONE.CONTACT_POINT_ID(+)(outer join) for telephone data, andPHONE1for the e-mail address.AS_LOOKUPS(ROLE_LKUP) for the contact role meaning.AR_LOOKUPS(AR_LKUP1,AR_LKUP2,AR_LKUP3) for additional decoded meanings, including relationship and job title code descriptions.
The outer join on the phone contact point means lead contacts without a phone record still appear, with phone columns null.
Key Columns
LEAD_CONTACT_ID,SALES_LEAD_ID,CONTACT_ID,CONTACT_PARTY_ID— primary identifiers linking the lead-contact record to its lead, contact, and party.CONTACT_ROLE_CODEandMEANING— the lead contact role and its decoded display value; central to role-based reporting.PRIMARY_CONTACT_FLAG,ENABLED_FLAG,RANK— indicate the primary contact, record status, and ordering/priority of the contact.CUSTOMER_ID,ADDRESS_ID,PHONE_ID— customer, address, and phone references.PERSON_FIRST_NAME,PERSON_LAST_NAME,JOB_TITLE,JOB_TITLE_CODE— contact identity and organizational role.RELATIONSHIP_ID,RELATIONSHIP_CODE,SUBJECT_ID,OBJECT_ID— party relationship context.EMAIL_ADDRESS,RAW_PHONE_NUMBER, and the concatenated phone expression (PHONE_COUNTRY_CODE,PHONE_AREA_CODE,PHONE_NUMBER,PHONE_EXTENSION),PHONE_LINE_TYPE— communication details.- Standard WHO/audit columns:
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN, andATTRIBUTE1–ATTRIBUTE15withATTRIBUTE_CATEGORYfor descriptive flexfield data.
Common Use Cases and Queries
The view supports lead-contact reporting, role analysis, and data migration extracts. Typical queries include:
- Listing all contacts for a given sales lead with their roles:
SELECT sales_lead_id, contact_party_id, person_first_name,
person_last_name, contact_role_code, meaning
FROM apps.ast_sales_lead_contacts_v
WHERE sales_lead_id = :p_lead_id
AND enabled_flag = 'Y';
- Filtering by a specific lead contact role:
SELECT sales_lead_id, person_last_name, email_address, phone_line_type FROM apps.ast_sales_lead_contacts_v WHERE contact_role_code = :p_role_code;
- Identifying the primary contact for each lead:
SELECT sales_lead_id, person_first_name, person_last_name FROM apps.ast_sales_lead_contacts_v WHERE primary_contact_flag = 'Y' AND enabled_flag = 'Y';
Because the view joins multiple HZ and lookup tables, queries should be constrained by lead, customer, or role to limit result sets. No DML is permitted against the view.
-
APPS.AST_SALES_LEAD_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LOOKUPS·↳ AS_SALES_LEAD_CONTACTS·Explore AST module →
-
APPS.AST_SALES_LEAD_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LOOKUPS·↳ AS_SALES_LEAD_CONTACTS·Explore AST module →
-
VIEW: APPS.CSD_INCIDENTS_V 12.2.2
-
VIEW: APPS.CSD_INCIDENTS_V 12.1.1
-
The view for getting service request information.
APPS.CSD_INCIDENTS_NON_SEC_V·↳ AR_LOOKUPS·↳ CSD_PROCESS_UTIL·↳ CSI_INSTANCE_STATUSES·Explore CSD module →
-
View: CSD_INCIDENTS_V 12.1.1
The view for getting service request information.
APPS.CSD_INCIDENTS_V·↳ AR_LOOKUPS·↳ CSD_PROCESS_UTIL·↳ CSI_INSTANCE_STATUSES·Explore CSD module →
-
View: CSD_INCIDENTS_V 12.2.2
The view for getting service request information.
APPS.CSD_INCIDENTS_V·↳ AR_LOOKUPS·↳ CSD_PROCESS_UTIL·↳ CSI_INSTANCE_STATUSES·Explore CSD module →
-
The view for getting service request information.
APPS.CSD_INCIDENTS_NON_SEC_V·↳ AR_LOOKUPS·↳ CSD_PROCESS_UTIL·↳ CSI_INSTANCE_STATUSES·Explore CSD module →
-
View: CS_SR_HZ_CUST_CONT_V 12.2.2
This view lists all the customer contacts for party types PARTY_RELATIONSHIP and PERSON.
APPS.CS_SR_HZ_CUST_CONT_V·↳ CS_LOOKUPS·↳ FND_GLOBAL·↳ HZ_CUST_ACCOUNTS·Explore CS module →
-
View: CS_SR_HZ_CUST_CONT_V 12.1.1
This view lists all the customer contacts for party types PARTY_RELATIONSHIP and PERSON.
APPS.CS_SR_HZ_CUST_CONT_V·↳ CS_LOOKUPS·↳ FND_GLOBAL·↳ HZ_CUST_ACCOUNTS·Explore CS module →
-
VIEW: APPS.JTF_NOTES_VL 12.2.2
-
VIEW: APPS.JTF_NOTES_VL 12.1.1
-
VIEW: APPS.IMC_GROWTH_RPT_V 12.1.1
-
VIEW: APPS.IMC_GROWTH_RPT_V 12.2.2
-
OBSOLETED LOOKUP - Profile Type of Customer Contact
-
Valid Contact Types for creating a Service Request
-
Party Types
-
Party Types
-
OBSOLETED LOOKUP - Profile Type of Customer Contact
-
Valid Contact Types for creating a Service Request
-
View: AST_LM_CKEY_ACCT_V 12.2.2
APPS.AST_LM_CKEY_ACCT_V·↳ AR_LOOKUPS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCOUNT_ROLES·Explore AST module →
-
Lookup Type: PARTY_TYPE 12.1.1
Party Type
-
Lookup Type: PARTY_TYPE 12.2.2
Party Type
-
View: AST_LM_CKEY_ACCT_V 12.1.1
APPS.AST_LM_CKEY_ACCT_V·↳ AR_LOOKUPS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCOUNT_ROLES·Explore AST module →
-
View: HZ_PARTY_WF_ROLES_V 12.2.2
APPS.HZ_PARTY_WF_ROLES_V·↳ FND_LANGUAGES·↳ HZ_CONTACT_POINTS·↳ HZ_PARTIES·Explore AR module →
-
View: IBE_QUOTE_HEADERS_V 12.1.1
APPS.IBE_QUOTE_HEADERS_V·↳ ASO_QUOTE_HEADERS·↳ ASO_QUOTE_STATUSES_VL·↳ HZ_CUST_ACCOUNTS·Explore IBE module →
-
View: JTF_NOTES_VL 12.1.1
MLS view over JTF_NOTES_B and JTF_NOTES_TL. Main view to query up all Notes related to any object.
APPS.JTF_NOTES_VL·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_COMMON_PVT·Explore JTF module →
-
View: JTF_NOTES_VL 12.2.2
MLS view over JTF_NOTES_B and JTF_NOTES_TL. Main view to query up all Notes related to any object.
APPS.JTF_NOTES_VL·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_COMMON_PVT·Explore JTF module →
-
View: IBE_QUOTE_HEADERS_V 12.2.2
APPS.IBE_QUOTE_HEADERS_V·↳ ASO_QUOTE_HEADERS·↳ ASO_QUOTE_STATUSES_VL·↳ HZ_CUST_ACCOUNTS·Explore IBE module →
-
VIEW: APPS.OKX_ORG_PARTIES_V 12.2.2
-
View: JTF_RS_PTNR_MIGR_VL 12.1.1
Stores specific partner related data used for internal migration.
APPS.JTF_RS_PTNR_MIGR_VL·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore JTF module →
-
View: JTF_RS_PTNR_MIGR_VL 12.2.2
Stores specific partner related data used for internal migration.
APPS.JTF_RS_PTNR_MIGR_VL·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore JTF module →