Results for “csp_rs_cust_relations_u1”

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

Overview

TABLE CSP.CSP_RS_CUST_RELATIONS is a transactional data object in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the CSP schema (Service/Field Service related components). Its documented title, "Resource with ship to address and subinventory assigned," indicates that the table establishes the association between a resource and a customer account, effectively capturing which customers a given resource is permitted or scheduled to serve. The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, consistent with the standard EBS transactional data conventions.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. This classification reflects the fact that the table carries descriptive attributes (such as the descriptive flexfield segments and the DEFAULT_TRIP_START flag) attached to one or more business keys, namely RS_CUST_RELATION_ID, and the composite key RESOURCE_TYPE with RESOURCE_ID. In practice, the table functions as a relationship or bridge table that links resources to customer accounts within the CSP application module.

Key Information Stored

The table contains 31 documented columns. The most significant are outlined below.

• RS_CUST_RELATION_ID (NUMBER) — The surrogate primary key and unique identifier for the resource-customer relation. Enforced by PK CSP_RS_CUST_RELATIONS_PK and unique index CSP_RS_CUST_RELATIONS_U1.
• RESOURCE_TYPE (VARCHAR2, 30) — Identifies the category of resource being associated. Forms part of the composite business key.
• RESOURCE_ID (NUMBER) — The identifier of the resource itself. Together with RESOURCE_TYPE, it forms unique index CSP_RS_CUST_RELATIONS_U2, making this pair the primary business-key candidate.
• CUSTOMER_ID (NUMBER) — The customer account identifier, along with a foreign key to HZ_CUST_ACCOUNTS. Indexed non-uniquely via CSP_RS_CUST_RELATIONS_N1 to support reverse lookups.
• SECURITY_GROUP_ID (NUMBER) — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or operating-unit data segregation.
• DEFAULT_TRIP_START — A flag indicating whether the associated resource-to-customer combination serves as a default trip origin.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide full audit lineage.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) structure and segment columns enabling customer-specific extension without schema changes.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying the batch process that last touched the row.

Common Use Cases and Queries

Typical scenarios involve determining which customers a resource is linked to, or conversely, which resources service a given customer. A common query joins the table to HZ_CUST_ACCOUNTS to resolve account names:

• SELECT r.RS_CUST_RELATION_ID, r.RESOURCE_TYPE, r.RESOURCE_ID, a.ACCOUNT_NAME FROM CSP.CSP_RS_CUST_RELATIONS r, HZ_CUST_ACCOUNTS a WHERE r.CUSTOMER_ID = a.CUST_ACCOUNT_ID;
• Filtering by RESOURCE_TYPE and RESOURCE_ID leverages the U2 unique index for efficient point lookups.
• Reporting on DEFAULT_TRIP_START supports field service routing and dispatch analysis.
• Auditing the DFF segment columns (ATTRIBUTE1–15) supports customer-specific reporting requirements.

Related Objects

• HZ_CUST_ACCOUNTS — Referenced by the foreign key on CUSTOMER_ID; supplies customer master data.
• FND_SECURITY_GROUPS — Referenced by the foreign key on SECURITY_GROUP_ID; governs data access partitions.
• FND_USER — Source of the CREATED_BY and LAST_UPDATED_BY user identifiers.
• CSP_RS_CUST_RELATIONS_PK — Primary key constraint on RS_CUST_RELATION_ID.
• CSP_RS_CUST_RELATIONS_U1 / U2 / N1 — Unique and non-unique indexes underpinning the access paths described above.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — Reference targets for the PROGRAM_ID and REQUEST_ID audit columns.