Results for “csc_prof_block_results_v”

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

Overview

The CSC_PROF_BLOCK_RESULTS_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Customer Care (CSC) product family. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the object is a VIEW with a status of VALID. Its stated purpose is to expose the results of the Profile Check Variables whenever the Profile Engine is executed. In practical terms, the view captures the outcome computed for each profiling block evaluated against a party or customer account during a profile run.

The view is a straightforward projection over the CSC_PROF_BLOCK_RESULTS base object. Because the definition performs no joins, aggregations, or filters, it functions as a stable, read-only access layer that shields consuming reports and interfaces from direct dependency on the base table. Users searching for the identifier block_results_id will find that this column is the primary key exposed at the head of the view's SELECT list, making the view a natural entry point for lookups and joins keyed on profile block results.

Underlying Base Objects

The view is defined exclusively over CSC_PROF_BLOCK_RESULTS, which is documented as a SYNONYM referenced by the view. The view text is a simple column projection with no transformation logic:

• SELECT BLOCK_RESULTS_ID, BLOCK_ID, PARTY_ID, CUST_ACCOUNT_ID, VALUE, CURRENCY_CODE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN FROM CSC_PROF_BLOCK_RESULTS

Because the view carries no DISTINCT clause or WHERE predicate, it returns every row present in the underlying base object. Consequently, the view and the base table remain fully synchronized; there is no materialization, no snapshot refresh, and no filtering to reconcile. Any change committed to CSC_PROF_BLOCK_RESULTS is immediately visible through the view, and row-level concurrency behavior is governed entirely by the base object.

Key Columns

The eleven columns exposed by the view carry the full audit footprint and the core profiling outcome data:

• BLOCK_RESULTS_ID — Unique identifier for each profile block result row; the primary key and the column most frequently used in targeted lookups and foreign-key joins.
• BLOCK_ID — Reference to the profiling block definition that produced this result, linking the outcome to the configured check.
• PARTY_ID — Identifier of the party (person or organization) evaluated by the Profile Engine.
• CUST_ACCOUNT_ID — Identifier of the customer account associated with the evaluation, when applicable.
• VALUE — The computed result value returned for the profile check variable.
• CURRENCY_CODE — Currency applicable to the result value where the value is monetary.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row and when.

Common Use Cases and Queries

Typical scenarios include reviewing the outcomes of a specific profile run for a given customer, reporting profile results by party, and joining results back to block or party master data. Retrieving a single result by identifier is the most direct use:

• SELECT block_results_id, block_id, party_id, cust_account_id, value, currency_code FROM csc_prof_block_results_v WHERE block_results_id = :p_id;
• SELECT * FROM csc_prof_block_results_v WHERE party_id = :p_party_id ORDER BY creation_date DESC;
• SELECT v.block_id, COUNT(*) FROM csc_prof_block_results_v v GROUP BY v.block_id;

Because the view is a pass-through projection, performance characteristics match those of the base object; queries benefit from indexes defined on CSC_PROF_BLOCK_RESULTS, particularly on BLOCK_RESULTS_ID, BLOCK_ID, and PARTY_ID.