Results for “csp_rs_cust_relations_u2”

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

Overview

CSP_RS_CUST_RELATIONS is a transactional configuration table owned by the CSP schema within the Spares Management module of Oracle E-Business Suite. Its documented purpose is to associate a resource (depot repair, field service, or spares resource) with a ship-to customer and a subinventory, effectively defining where and for whom a given resource operates. Each row represents a customer-resource relationship that governs sourcing, default shipping destination, and inventory allocation during spares fulfillment and returns processing.

The object carries a heuristic Data Vault classification of satellite-leaning. In Data Vault modeling terms, this suggests the table behaves primarily as a descriptive satellite attached to a business key — here the resource identified by RESOURCE_TYPE and RESOURCE_ID — rather than as a pure hub or link. Modelers designing a warehouse layer should treat the RESOURCE_TYPE/RESOURCE_ID pair as the durable business key and the customer, subinventory, and trip-related attributes as time-variant descriptive context.

Key Information Stored

The table contains 31 documented columns. The most significant are:

• RS_CUST_RELATION_ID — the surrogate primary key, enforced by CSP_RS_CUST_RELATIONS_PK.
• RESOURCE_TYPE and RESOURCE_ID — the resource identification pair; together they form a business-key candidate under the unique index CSP_RS_CUST_RELATIONS_U2.
• CUSTOMER_ID — foreign key to HZ_CUST_ACCOUNTS, identifying the ship-to customer account.
• DEFAULT_TRIP_START — defines the default starting point for trips associated with the resource-customer relationship.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS flexfield descriptor and 15 descriptive flexfield segments for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard Who columns for auditability.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — concurrent program tracking columns.

Two unique indexes are documented: CSP_RS_CUST_RELATIONS_U1 on RS_CUST_RELATION_ID (redundant with the PK) and CSP_RS_CUST_RELATIONS_U2 on (RESOURCE_TYPE, RESOURCE_ID), which enforces that a resource appears only once as a relationship owner.

Common Use Cases and Queries

Typical usage centers on resolving which subinventory and ship-to address should be used for a given spares resource. A common query joins the relationship to the customer master to retrieve ship-to details:

• SELECT r.RS_CUST_RELATION_ID, r.RESOURCE_TYPE, r.RESOURCE_ID, r.CUSTOMER_ID, r.DEFAULT_TRIP_START FROM CSP.CSP_RS_CUST_RELATIONS r, HZ_CUST_ACCOUNTS c WHERE r.CUSTOMER_ID = c.CUST_ACCOUNT_ID;
• Lookups by resource using the U2 index: WHERE RESOURCE_TYPE = :type AND RESOURCE_ID = :id.
• Reporting on active customer-resource coverage for depot repair scheduling.
• Auditing changes via LAST_UPDATE_DATE and LAST_UPDATED_BY for compliance reporting.
• Extracting flexfield data through ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for downstream analytics.

Related Objects

• HZ_CUST_ACCOUNTS — referenced via CSP_RS_CUST_RELATIONS.CUSTOMER_ID; the customer master providing ship-to identity.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data partitioning.
• FND_CONCURRENT_REQUESTS — implied by REQUEST_ID for program-run lineage.
• FND_APPLICATION — implied by PROGRAM_APPLICATION_ID.
• CSP_RS_RESOURCES — logical parent of the RESOURCE_TYPE/RESOURCE_ID key, though not documented as a formal FK.
• MTL_SECONDARY_INVENTORIES — logical reference for subinventory assignments associated with the relationship.
• CSP_RS_CUST_RELATIONS_PK / _U1 / _U2 — the enforcing constraints and unique indexes.