Search Results f_user

Overview

APPS.CS_SYSTEM_PARTY_LINKS_V is a reporting and integration view in the Oracle E-Business Suite customer service (CS) schema. It presents a denormalized, joined representation of the relationship between customer service "systems" and the parties (customers, contacts, and their associated application users) linked to those systems. The view consolidates data from the party-link association table, the party master, the system definition, and the FND user repository into a single queryable object.

In the context of Oracle EBS 12.1.1 and 12.2.2, this view supports operational reporting, data extraction, and integration workflows where a flat, joined result set is more convenient than querying the base tables directly. Because it is owned by APPS and defined over public synonyms, it is available to concurrent programs, BI Publisher data models, Oracle Reports, OA Framework pages, and custom SQL invoked through the standard APPS credentials.

Underlying Base Objects

The view is defined over four referenced objects, each resolved through a SYNONYM in the documented ETRM metadata:

• CS_SYSTEM_PARTY_LINKS — the driving association table, aliased CS_PARTY_LINK, holding the PARTY_ID-to-SYSTEM_ID relationship and its effective dating.
• HZ_PARTIES — the Trading Community Architecture party master, aliased HZ_PARTY, supplying the party name.
• CS_SYSTEMS_ALL_VL — the customer service system definition view, aliased CS_SYSTEM, supplying system attributes across organizations.
• FND_USER — the application user repository, aliased F_USER, supplying user identifiers and logon information.

The joins are defined as: CS_PARTY_LINK.PARTY_ID equals HZ_PARTY.PARTY_ID; F_USER.CUSTOMER_ID equals CS_PARTY_LINK.PARTY_ID; and CS_PARTY_LINK.SYSTEM_ID equals CS_SYSTEM.SYSTEM_ID. Note that the user join is on CUSTOMER_ID rather than a direct user-to-party key, which is a characteristic behavior of the CS data model and can affect row cardinality when a party maps to multiple users.

Key Columns

• PARTY_ID, SYSTEM_ID — the composite link identifiers from CS_PARTY_LINK.
• START_DATE, END_DATE — effective dating of the party-to-system link.
• PARTY_NAME — from HZ_PARTIES, the trading community party name.
• USER_ID, USER_NAME, LAST_LOGON_DATE — application user identity and most recent logon, from FND_USER.
• NAME, PARENT_SYSTEM_ID — the system name and its parent in the system hierarchy.
• CUSTOMER_ID, TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID — contacts and customer associated with the system.
• START_DATE_ACTIVE, END_DATE_ACTIVE, COTERMINATE_DAY_MONTH — activation and cotermination attributes of the system.
• ORG_ID — the operating unit (multi-org) identifier on the system record.
• LAST_UPDATED_BY, CREATED_BY — audit columns sourced from CS_PARTY_LINK.

Common Use Cases and Queries

Typical uses include validating party-to-system assignments, auditing which application users are associated with a given customer system, and reporting on system activation and cotermination dates. The following query lists active party-system links with user logon information:

SELECT party_name,
       name            AS system_name,
       user_name,
       last_logon_date,
       start_date,
       end_date
  FROM apps.cs_system_party_links_v
 WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date, SYSDATE)
                          AND NVL(end_date, SYSDATE)
 ORDER BY party_name, system_name;

To identify orphaned or missing links within an operating unit, query by ORG_ID and compare against the party and system masters. Because the view joins FND_USER on CUSTOMER_ID, reports involving users should be validated for multiplicity. The view is read-only and intended for querying; DML must be performed against the underlying base tables.