Results for “technical_contact_id”

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

Overview

The APPS.CS_SYSTEM_PARTY_LINKS_V view is a denormalized reporting and integration construct within the Oracle E-Business Suite Service (CS) module. It exposes the association between a party record (customer, contact, or user) and a service system by joining the CS_SYSTEM_PARTY_LINKS intersection table to the HZ_PARTIES party master, the CS_SYSTEMS_ALL_VL system definition, and FND_USER. The view is owned by the APPS schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2.

Its principal value is convenience: rather than requiring a developer or report author to reconstruct the many-to-many relationship between parties and installed-base systems manually, the view presents system attributes, party/contact attributes, and the corresponding application user in a single row set. This makes it useful for service contract reporting, installed-base analysis, contact validation, and interfaces that need to resolve which users or contacts are linked to which customer systems. The presence of the TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID, CUSTOMER_ID, and ORG_ID columns makes the view especially relevant when investigating ownership and contact assignments at the system level.

Underlying Base Objects

The view definition references four documented base objects:

• CS_SYSTEM_PARTY_LINKS (SYNONYM) — the driving intersection table aliased CS_PARTY_LINK, supplying PARTY_ID, SYSTEM_ID, START_DATE, END_DATE, and audit columns.
• HZ_PARTIES (SYNONYM) — the Trading Community Architecture party master, supplying party name, person name components, address, and email attributes.
• CS_SYSTEMS_ALL_VL (SYNONYM) — the translated service system definition, supplying NAME, PARENT_SYSTEM_ID, CUSTOMER_ID, TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID, active dates, COTERMINATE_DAY_MONTH, and ORG_ID.
• FND_USER (SYNONYM) — the application user repository, supplying USER_ID, USER_NAME, and LAST_LOGON_DATE.

The joins are equi-joins on CS_PARTY_LINK.PARTY_ID = HZ_PARTY.PARTY_ID, F_USER.CUSTOMER_ID = CS_PARTY_LINK.PARTY_ID, and CS_PARTY_LINK.SYSTEM_ID = CS_SYSTEM.SYSTEM_ID. Note that the FND_USER join is driven through CUSTOMER_ID, so only parties that also exist as application users will appear.

Key Columns

• PARTY_ID / SYSTEM_ID — the two key identifiers linking a party to a system; the primary relationship keys for the view.
• START_DATE / END_DATE — effective dating of the party-to-system link, taken from CS_SYSTEM_PARTY_LINKS.
• USER_ID / USER_NAME / LAST_LOGON_DATE — the application user associated with the party, useful for login and activity reporting.
• TECHNICAL_CONTACT_ID / SERVICE_ADMIN_CONTACT_ID — the contact party identifiers designated as technical and service-administration contacts on the system record.
• CUSTOMER_ID — the customer party owning the system; note that in the join it is also matched against FND_USER.CUSTOMER_ID.
• ORG_ID — the operating unit context of the system, enabling multi-org filtered reporting.
• NAME / PARENT_SYSTEM_ID — the system name and its parent system, supporting hierarchy analysis.
• START_DATE_ACTIVE / END_DATE_ACTIVE / COTERMINATE_DAY_MONTH — system-level active dating and cotermination configuration.

Common Use Cases and Queries

Typical uses include identifying all parties linked to a given system, retrieving contact details for a customer's installed base, and resolving technical or service-admin contacts by system or operating unit.

Example — list parties and contacts for a system:

SELECT party_id, party_name, email_address, user_name, name, technical_contact_id, service_admin_contact_id
FROM apps.cs_system_party_links_v
WHERE system_id = :p_system_id;

Example — find linked users for an operating unit:

SELECT user_name, party_name, name, last_logon_date
FROM apps.cs_system_party_links_v
WHERE org_id = :p_org_id
ORDER BY last_logon_date DESC;

Because the view does not itself filter on active dates, callers should generally add predicates on END_DATE or END_DATE_ACTIVE when only current associations are required.