Results for “party_cont1”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.CSD_INCIDENTS_NON_SEC_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes service request (incident) data from the CRM/TeleService schema without applying the row-level security clauses that constrain the underlying transactional view CS_INCIDENTS_ALL_VL. It is part of the CSD (Customer Service/Depot Repair) object family and predates the Service Request Management and Knowledge Management (CS/CSM) schema consolidation in Release 12. Because it omits the security predicate, it is used internally by concurrent programs, workflow, and diagnostic queries where the caller must already hold unrestricted access, or where data must be joined across organizations.
The view flattens a service request into a single denormalized row combining incident header attributes, item and product revision context, caller identity, and caller contact information. It resolves lookup codes to meanings and formats telephone numbers for display, making it convenient for direct report and interface consumption. Users searching for party_relationship typically encounter this view because caller and contact details are resolved through the TCA party model (HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS) rather than through the legacy customer tables, so any querying of caller identity against a party relationship traverses the HZ joins embedded here.
Underlying Base Objects
The view is defined over a mix of transactional base tables, public synonyms, and _VL (translated) views. Documented base objects include:
- Incident header: CS_INCIDENTS_ALL_VL (the multilanguage base view), plus lookup and reference views CS_INCIDENT_STATUSES_VL, CS_INCIDENT_TYPES_VL, CS_INCIDENT_SEVERITIES_VL, and synonyms CS_INCIDENT_URGENCIES_B / _TL.
- TCA / party model: HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOCATIONS, and HZ_TIMEZONES. CS_HZ_SR_CONTACT_POINTS provides the SR-to-contact-point association.
- Product / install base: CSI_ITEM_INSTANCES and CSI_INSTANCE_STATUSES, with MTL_SYSTEM_ITEMS_VL supplying item number and description.
- Human resources and security: PER_ALL_PEOPLE_F, PER_EMPLOYEES_CURRENT_X, PER_PHONES, and packages HR_API, HR_GENERAL, HR_LOOKUPS, HR_PERSON_NAME, HR_SECURITY.
- Utilities and lookups: CS_STD, CSD_PROCESS_UTIL, FND_GLOBAL, FND_USER, AR_LOOKUPS, CS_LOOKUPS, HR_LOOKUPS, plus JTF_CUST_ACCOUNTS_ALL_V and JTF_PARTIES_ALL_V.
The presence of HR_SECURITY and FND_GLOBAL is significant: although the view is "non-secured" relative to service request security, it still resolves the caller and owner through HR person name APIs and TCA party relationships, so row visibility for person records may depend on HR security profiles in the underlying joins.
Key Columns
- INCIDENT_ID, INCIDENT_NUMBER: Primary key and user-visible service request number.
- INCIDENT_STATUS_ID, INCIDENT_TYPE_ID, INCIDENT_URGENCY_ID, INCIDENT_SEVERITY_ID: Foreign keys to the incident lookup views; the view resolves meanings for reporting.
- ITEM, ITEM_DESC, INV_ITEM_ID, INV_ITEM_REVISION, INV_ORGANIZATION_ID: Product context, with revision resolved via NVL(INV_ITEM_REVISION, PRODUCT_REVISION).
- CALLER: Derived from party first/last name when the caller is a person, otherwise from the full name (FND2.FULL_NAME), reflecting caller type ORGANIZATION vs PERSON.
- CUST_PHONE, CUST_PHONE_LINE_CODE, CUST_PHONE_LINE_TYPE, EXT: Formatted phone attributes sourced from the contact point resolved through party relationships.
- CUSTOMER_PRODUCT_ID: Install base instance identifier from CSI_ITEM_INSTANCES.
- ORG_ID: Multi-org operating unit, used to partition the non-secured result set by organization.
- OWNER_TYPE, INCIDENT_OWNER_ID: Resource type derived via SUBSTR(RESOURCE_TYPE,4,30) and the internal owner identifier.
- RECORD_IS_VALID_FLAG: Indicates whether the incident record is logically active.
Common Use Cases and Queries
The view is appropriate for cross-organization reporting, data migration extraction, and diagnostics where the standard secured incident view returns incomplete results. A typical query selects open incidents with caller and item context:
SELECT incident_number, caller, cust_phone, item, item_desc, org_id FROM apps.csd_incidents_non_sec_v WHERE record_is_valid_flag = 'Y' AND incident_status_id NOT IN (SELECT incident_status_id FROM apps.csd_incidents_non_sec_v WHERE UPPER(status) LIKE 'CLOSED%');- Joining to HZ_RELATIONSHIPS to locate the party relationship linking a caller to an account:
SELECT v.incident_number, v.caller, r.relationship_code, r.subject_id, r.object_id FROM apps.csd_incidents_non_sec_v v, hz_relationships r WHERE v.incident_owner_id = r.subject_id AND r.relationship_code = 'CONTACT_OF' AND v.org_id = :p_org_id; - Extracting incidents by item for install base analysis:
SELECT v.incident_number, v.item, v.item_desc, v.inv_item_revision, c.instance_id FROM apps.csd_incidents_non_sec_v v, csi_item_instances c WHERE v.customer_product_id = c.instance_id;
Because the view bypasses service request security, use it only in trusted reporting contexts and always constrain by ORG_ID and valid-record flags. For end-user inquiries, prefer the secured CS_INCIDENTS_ALL_VL view so that TCA and HR security semantics remain enforced through HZ_RELATIONSHIPS and HR_SECURITY.
-
VIEW: APPS.CSD_INCIDENTS_V 12.2.2
-
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: APPS.CSD_INCIDENTS_V 12.1.1
-
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 →