Search Results sub_decision_maker_flag




Overview
Explore in AI Chat

Overview

CS_SR_CONTACT_DETAILS_V is a Service (CS) module reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that consolidates contact information for every contact associated with a service request. Its purpose is to expose party, contact point, and incident identifiers together with the caller's job title, formatted contact name, structured address, decision-maker flag, and contact role, resolving the differences between the two supported Caller Types: ORGANIZATION and PERSON. The view therefore provides a single, presentation-ready record per contact that service request queries, concurrent programs, and external integrations can consume without re-implementing the join logic against the underlying Oracle Customers Online (HZ) and JTF tables.

Because the view derives its rows from CS_HZ_SR_CONTACT_POINTS using a UNION of two distinct SELECT statements, consumers automatically receive a consistent column layout regardless of whether the contact is an organization-linked person (where job title and decision-maker information is available) or a standalone person contact (where those attributes are returned as NULL).

Underlying Base Objects

The view is defined over four documented base objects:

The first branch of the UNION returns contacts with organization-derived attributes; the second branch returns pure person contacts with NULL SUB_DECISION_MAKER_FLAG and NULL SUB_JOB_TITLE. DISTINCT is applied to each branch to suppress duplicates arising from the relationship join.

Key Columns

  • SUB_JOB_TITLE — the job title of the contact, sourced from HZ_ORG_CONTACTS.JOB_TITLE; this is the column most commonly matched when users search for "sub_job_title". It is NULL for person-type contacts.
  • SUB_TITLE — the person's title or salutation (PERSON_TITLE).
  • CONTACT — the concatenated full display name (title, first name, last name, suffix).
  • SUB_FIRST_NAME / SUB_LAST_NAME — individual name components for sorting or matching.
  • SUB_DECISION_MAKER_FLAG — indicates whether the contact is a decision maker at the organization; NULL for person contacts.
  • ADDRESS1 / ADDRESS2 — address lines formed by concatenating ADDRESS1 through ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, and COUNTRY into two derived fields.
  • PARTY_ID, CONTACT_POINT_ID, INCIDENT_ID — join keys back to the service request and party model.
  • PRIMARY_FLAG, CONTACT_TYPE — indicate whether the contact is the primary service request contact and its role classification.

Common Use Cases and Queries

Typical uses include service request contact lists, notification population, and customer-facing reports that require job title and address per contact. A frequent pattern filters on the searched column:

SELECT incident_id, contact, sub_job_title, address1, primary_flag
FROM   cs_sr_contact_details_v
WHERE  sub_job_title IS NOT NULL
ORDER BY incident_id, contact;

To list all contacts for a specific service request:

SELECT party_id, contact, sub_job_title, sub_decision_maker_flag, contact_type
FROM   cs_sr_contact_details_v
WHERE  incident_id = :incident_id;

Note that the documentation indicates the view is not implemented in every database, so availability should be confirmed against the target instance before reliance in reports or interfaces.

  • View: CS_SR_CONTACT_DETAILS_V 12.2.2

    product: CS - Service ,  description: This view obtains the contact information such as Job Title, Address etc. for each of the contacts pertaining to a service request depending on the Caller Type i,e. ORGANIZATION / PERSON. ,  implementation_dba_data: Not implemented in this database , 

  • View: CS_SR_CONTACT_DETAILS_V 12.1.1

    product: CS - Service ,  description: This view obtains the contact information such as Job Title, Address etc. for each of the contacts pertaining to a service request depending on the Caller Type i,e. ORGANIZATION / PERSON. ,  implementation_dba_data: Not implemented in this database , 

  • VIEW: APPS.CSC_HZ_PER_PROFILES_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_HZ_PER_PROFILES_V,  object_name:CSC_HZ_PER_PROFILES_V,  status:VALID, 

  • VIEW: APPS.CSC_HZ_PER_PROFILES_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_HZ_PER_PROFILES_V,  object_name:CSC_HZ_PER_PROFILES_V,  status:VALID, 

  • View: CSC_HZ_PER_PROFILES_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_HZ_PER_PROFILES_V,  object_name:CSC_HZ_PER_PROFILES_V,  status:VALID,  product: CSC - Customer Care ,  description: View of HZ_PERSON_PROFILES, HZ_PARTY_RELATIONSHIPS. Detailed information about a party. Refer to base table for details. ,  implementation_dba_data: APPS.CSC_HZ_PER_PROFILES_V , 

  • View: CSC_HZ_PER_PROFILES_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_HZ_PER_PROFILES_V,  object_name:CSC_HZ_PER_PROFILES_V,  status:VALID,  product: CSC - Customer Care ,  description: View of HZ_PERSON_PROFILES, HZ_PARTY_RELATIONSHIPS. Detailed information about a party. Refer to base table for details. ,  implementation_dba_data: APPS.CSC_HZ_PER_PROFILES_V , 

  • VIEW: APPS.CSC_CUSTOMER_RESPONSE_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_CUSTOMER_RESPONSE_V,  object_name:CSC_CUSTOMER_RESPONSE_V,  status:VALID, 

  • VIEW: APPS.CSC_CUSTOMER_RESPONSE_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_CUSTOMER_RESPONSE_V,  object_name:CSC_CUSTOMER_RESPONSE_V,  status:VALID, 

  • View: CSC_CUSTOMER_RESPONSE_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_CUSTOMER_RESPONSE_V,  object_name:CSC_CUSTOMER_RESPONSE_V,  status:VALID,  product: CSC - Customer Care ,  description: Contains Relationship information, Subject (Caller) and Object (Person/Group/Organization) information ,  implementation_dba_data: APPS.CSC_CUSTOMER_RESPONSE_V , 

  • View: CSC_CUSTOMER_RESPONSE_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CSC.CSC_CUSTOMER_RESPONSE_V,  object_name:CSC_CUSTOMER_RESPONSE_V,  status:VALID,  product: CSC - Customer Care ,  description: Contains Relationship information, Subject (Caller) and Object (Person/Group/Organization) information ,  implementation_dba_data: APPS.CSC_CUSTOMER_RESPONSE_V , 

  • VIEW: APPS.JTF_PARTIES_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:JTF.JTF_PARTIES_V,  object_name:JTF_PARTIES_V,  status:VALID, 

  • VIEW: APPS.JTF_PARTIES_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:JTF.JTF_PARTIES_V,  object_name:JTF_PARTIES_V,  status:VALID, 

  • View: JTF_PARTIES_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:JTF.JTF_PARTIES_V,  object_name:JTF_PARTIES_V,  status:VALID,  product: JTF - CRM Foundation ,  description: Party (Organization or Group or Person) and relationship information ,  implementation_dba_data: APPS.JTF_PARTIES_V , 

  • View: JTF_PARTIES_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:JTF.JTF_PARTIES_V,  object_name:JTF_PARTIES_V,  status:VALID,  product: JTF - CRM Foundation ,  description: Party (Organization or Group or Person) and relationship information ,  implementation_dba_data: APPS.JTF_PARTIES_V , 

  • eTRM - CSC Tables and Views 12.1.1

    description: Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown , 

  • eTRM - CSC Tables and Views 12.2.2

    description: Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown , 

  • eTRM - JTF Tables and Views 12.2.2

    description: Interface table to store data that needs to be displayed in Excel , 

  • eTRM - JTF Tables and Views 12.1.1

    description: Interface table to store data that needs to be displayed in Excel ,