Results for “csc_customers”

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

Overview

CSC_CUSTOMERS is a table owned by the CSC schema within the Oracle E-Business Suite Customer Care (CSC) module. It stores parties for which criticality values have been overridden, forming the persistence layer behind the Customer Care feature that allows agents or administrators to deviate from the default criticality assigned to a customer or party. The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and contains 32 columns.

From a Data Vault modeling perspective, the mined heuristic classification for CSC_CUSTOMERS is hub-leaning. This reflects the fact that its primary key is a single business identifier (PARTY_ID) rather than a composite junction key, and that it anchors descriptive state (override flags, reasons) around that identifier. In a Data Vault 2.0 design this table would most naturally decompose into a hub keyed on PARTY_ID, with the override-related attributes modeled as a satellite. For EBS implementations, however, the table should be treated as a standalone operational entity in the CSC schema.

Key Information Stored

The primary key is defined by the constraint CSC_CUSTOMER_PK on the PARTY_ID column, which identifies the party (customer, prospect, or organization) whose criticality is being overridden. A unique index, CSC_CUSTOMER_U1, also exists on PARTY_ID, reinforcing its role as the business-key candidate.

The most significant columns include:

• PARTY_ID — surrogate primary key and business key; the party reference.
• CUST_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS, linking the party to its customer account.
• OVERRIDE_FLAG — indicates that an override is in effect for the party.
• OVERRIDDEN_CRITICAL_FLAG — the criticality value applied after the override.
• OVERRIDE_REASON_CODE — coded justification for the override decision.
• PARTY_STATUS — status of the party at the time of the override.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-tenant data segregation.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request and program audit context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard who-column audit trails.
• CREATION_DATE, CREATED_BY — record creation audit.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the standard EBS descriptive flexfield (DFF) columns.

Common Use Cases and Queries

Typical operational scenarios include identifying which customers have had their criticality manually overridden, auditing the reasons for those overrides, and joining override data to the customer master for reporting. A representative query joining to the customer account hub is:

• SELECT cc.party_id, cc.cust_account_id, cc.override_flag, cc.overridden_critical_flag, cc.override_reason_code FROM csc.csc_customers cc WHERE cc.override_flag = 'Y';
• Join to HZ_CUST_ACCOUNTS hca ON hca.cust_account_id = cc.cust_account_id to resolve account numbers and names.
• Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID for multi-org filtering.

Reporting use cases include exception reports on overrides lacking a reason code, trending overrides by request or program, and feeding the audit history table for compliance traceability.

Related Objects

The principal related objects, grounded in the documented foreign-key data, are:

• HZ_CUST_ACCOUNTS — referenced via CSC_CUSTOMERS.CUST_ACCOUNT_ID.
• FND_SECURITY_GROUPS — referenced via CSC_CUSTOMERS.SECURITY_GROUP_ID.
• CSC_CUSTOMERS_AUDIT_HIST — references CSC_CUSTOMERS.PARTY_ID, capturing the historical audit trail of overrides.
• CSC_CUSTOMER_PK and CSC_CUSTOMER_U1 — the constraint and unique index enforcing key integrity.
• HZ_PARTIES — the underlying party master conventionally joined via PARTY_ID to resolve party names and types.

Together these objects allow developers to trace a party from its core definition through its customer account, its criticality override record, and its full audit history.