Results for “override_reason_desc”

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

Overview

CSC_CUSTOMERS_V is a VALID view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, delivered as part of the CSC – Customer Care product family. Per the documented metadata, it is described as a "View of CSC_CUSTOMERS" and is used specifically by the Customer Override Criticality form. Its purpose is to present a joined, presentation-ready result set that combines the customer override record, party identity attributes, the system-determined critical customer check result, and the decoded override reason, so that the form (and any downstream reporting) can display the net criticality of a customer along with the effective override state.

Because the view exposes a single consolidated row per party, it is useful for reporting and integration scenarios where the business must determine whether a customer is treated as critical after applying manual overrides on top of the system-detected critical flag. The view name is commonly encountered when troubleshooting the derived column SYS_DET_CRITICAL_FLAG, which is the system-determined criticality value sourced from the profile-driven check result.

Underlying Base Objects

The view is defined over the following documented base objects:

• CSC_CUSTOMERS (SYNONYM) — the primary driver table, aliased CC, holding override flag, overridden critical flag, reason code, and the 15 descriptive flexfield attribute columns and CONTEXT.
• CSC_PROF_CHECK_RESULTS (SYNONYM) — aliased PC, outer-joined on PARTY_ID and on CHECK_ID equal to FND_PROFILE.VALUE_WNPS('CSC_CRITICAL_CUSTOMER_CHECK'). This join supplies the system-determined critical value and restricts results to rows where CUST_ACCOUNT_ID IS NULL.
• HZ_PARTIES (SYNONYM) — aliased HZ, inner-joined on PARTY_ID to supply PARTY_NAME, PARTY_NUMBER, and STATUS.
• CSC_LOOKUPS (VIEW) — aliased CL, outer-joined on OVERRIDE_REASON_CODE with LOOKUP_TYPE 'CSC_CRITCUST_OVERRIDE_REASONS', supplying the MEANING used as OVERRIDE_REASON_DESC.
• FND_PROFILE (PACKAGE) — invoked through FND_PROFILE.VALUE_WNPS to resolve the CSC_CRITICAL_CUSTOMER_CHECK profile option value at runtime.

The outer joins (+) on CSC_PROF_CHECK_RESULTS and CSC_LOOKUPS mean that a customer row is still returned when no check result or no matching reason lookup exists, with NULLs substituted accordingly.

Key Columns

• ROW_ID — the ROWID of the underlying CSC_CUSTOMERS row, useful for direct updates.
• PARTY_ID / CUST_ACCOUNT_ID — keys identifying the party and, where applicable, the customer account.
• OVERRIDE_FLAG — indicates whether a manual override has been applied.
• OVERRIDDEN_CRITICAL_FLAG — the value the user manually set when overriding criticality.
• OVERRIDDEN_NONCRITICAL_FLAG — a derived column, DECODE of the overridden critical flag ('Y' returns 'N', otherwise 'Y'), giving the inverse view of the manual override.
• NET_CRITICAL_FLAG — the effective criticality after override: DECODE of OVERRIDE_FLAG, returning OVERRIDDEN_CRITICAL_FLAG when overridden, otherwise NVL of the profile check result and 'N'.
• SYS_DET_CRITICAL_FLAG — the system-determined critical flag taken directly from CSC_PROF_CHECK_RESULTS.VALUE (nullable when no check result exists).
• OVERRIDE_REASON_CODE / OVERRIDE_REASON_DESC — the coded reason for the override and its decoded lookup meaning.
• PARTY_NAME, PARTY_NUMBER, STATUS — identity and status attributes from HZ_PARTIES.
• ATTRIBUTE1–15 / CONTEXT — descriptive flexfield segments carried through from CSC_CUSTOMERS.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include validating the effect of overrides, reconciling system-detected versus net criticality, and feeding downstream critical-customer reporting. A representative query retrieving the net status for a party is:

• SELECT party_id, party_name, party_number, override_flag, sys_det_critical_flag, net_critical_flag FROM csc_customers_v WHERE party_id = :p_party_id;
• SELECT party_number, party_name, override_reason_desc, net_critical_flag FROM csc_customers_v WHERE override_flag = 'Y' AND sys_det_critical_flag = 'N'; — a listing of customers manually made critical despite a non-critical system result.
• SELECT net_critical_flag, COUNT(*) FROM csc_customers_v GROUP BY net_critical_flag; — a summary of effective criticality across the customer population.

Note that results depend on the runtime value of the CSC_CRITICAL_CUSTOMER_CHECK profile option, and the check-result join filters to rows where CUST_ACCOUNT_ID IS NULL.