Results for “csc_customers_audit_hist_v”

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

Overview

CSC_CUSTOMERS_AUDIT_HIST_V is a valid Oracle E-Business Suite view owned by the APPS schema, delivered as part of the CSC (Customer Care) product module. It exposes a denormalized, presentation-ready projection of the CSC_CUSTOMERS_AUDIT_HIST audit trail, joining the underlying base records to FND_USER, HR_EMPLOYEES, and CSC_LOOKUPS in order to resolve raw identifiers into human-readable values. The view is documented in ETRM 12.2.2 and is specifically identified as the data source for the Customer Override Criticality form. In EBS 12.1.1 and 12.2.2, that form is used by customer service agents to review and justify overrides applied to system-determined criticality for a customer account. Because the view returns both the numeric audit identifiers and the associated user name, employee full name, and override reason description, it removes the need for downstream presentation code to perform secondary lookups. Reporting tools, concurrent programs, and the form's block queries can all select from it without joining back to FND_USER or CSC_LOOKUPS manually.

Underlying Base Objects

The view is defined primarily over CSC_CUSTOMERS_AUDIT_HIST, the transactional audit history table that stores one row for each criticality evaluation and override event. Its documented base objects are CSC_CUSTOMERS_AUDIT_HIST (synonym), CSC_LOOKUPS (view), FND_USER (synonym), HR_EMPLOYEES (view), and the FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. The view text performs three outer joins: CH.CHANGED_BY equals FU.USER_ID, FU.EMPLOYEE_ID equals HR.EMPLOYEE_ID, and CH.OVERRIDE_REASON_CODE equals CL.LOOKUP_CODE where CL.LOOKUP_TYPE is 'CSC_CRITCUST_OVERRIDE_REASONS'. All three joins are outer, so audit rows are never dropped when the changed-by user, the associated HR employee record, or the lookup value is missing or invalid. This design preserves the integrity of the audit trail while still enriching it with descriptive attributes; the HR view and packages are referenced indirectly through the FND_USER to HR_EMPLOYEES linkage and enforce HR security when employee details are resolved.

Key Columns

• ROW_ID — the base table ROWID, used to identify the exact audit row.
• CUST_HIST_ID, PARTY_ID, CUST_ACCOUNT_ID — the audit record identifier and the party and customer account against which the criticality decision was made.
• CHANGED_DATE, CHANGED_BY — when and by whom the criticality record was changed; CHANGED_BY is the user_id keyed to FND_USER.
• USER_NAME — the FND_USER user_name of the changing user (FU.USER_NAME).
• FULL_NAME — the HR employee full name associated with that user (HR.FULL_NAME).
• SYS_DET_CRITICAL_FLAG, OVERRIDE_FLAG, OVERRIDDEN_CRITICAL_FLAG — the system-determined value, whether it was overridden, and the overridden criticality value.
• OVERRIDE_REASON_CODE, OVERRIDE_REASON_DESC — the stored lookup code and its translated meaning from CSC_LOOKUPS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard EBS WHO/Audit columns.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the DFF/SDF descriptor columns carried through from the base table.

Values returned in USER_NAME, FULL_NAME, and OVERRIDE_REASON_DESC are null when no matching reference record exists, reflecting the outer-join semantics.

Common Use Cases and Queries

The principal consumer is the Customer Override Criticality form, which uses the view to render the override audit history for a given customer account. Beyond that form, the view is commonly queried in custom reports and concurrent programs that need a readable audit trail of criticality overrides, including who changed the value, under what reason, and the resulting flags. A typical query retrieves the override history for a specific customer account:

SELECT cust_hist_id,
       cust_account_id,
       party_id,
       changed_date,
       user_name,
       full_name,
       override_reason_desc,
       sys_det_critical_flag,
       override_flag,
       overridden_critical_flag
FROM   apps.csc_customers_audit_hist_v
WHERE  cust_account_id = :p_cust_account_id
ORDER  BY changed_date DESC;

A second common pattern counts overrides by reason for a period, using OVERRIDE_REASON_DESC as the grouping label. Teams investigating exceptions frequently filter on OVERRIDE_FLAG = 'Y' with a non-null OVERRIDE_REASON_DESC to isolate rows where criticality was deliberately overridden. Because the view is a simple non-materialized definition over the base audit table, it should not be treated as a high-volume source without appropriate date and account predicates; the CSC_CUSTOMERS_AUDIT_HIST table can grow large, and the outer joins to FND_USER, HR_EMPLOYEES, and CSC_LOOKUPS add cost to unfiltered scans.