Search Results so_results




Overview
Explore in AI Chat

Overview

APPS.SO_VALID_RESULTS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema. It is a validation/results view that joins service request result definitions to the actions with which they are associated. The name SO_VALID_RESULTS_V indicates that it was created to expose validated or resolved result-to-action associations. Results in the EBS service request (SO) namespace are outcome values, such as MAILED, REJECTED, FIXED, or CLOSED, that record the disposition of a service request or its line. Actions are the workflow or activity records associated with a result. This view performs the join that links a result to an action and produces a flattened, denormalized row that can be consumed by reports, concurrent programs, and integrations without requiring custom SQL to traverse the two underlying tables.

This view is often located by searching for the term "so_results", which is consistent with its role as a convenience access path over the SO_RESULTS and SO_ACTION_RESULTS base tables. It is a read-only, non-inventoried view, and it does not maintain its own storage.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two objects referenced as synonyms in the APPS schema:

  • SO_RESULTS – the master table of result definitions.
  • SO_ACTION_RESULTS – the association table that maps results to actions.

The view's defining SQL is an inner join between these two objects:

SELECT NAME RESULT_NAME, DESCRIPTION, AR.RESULT_ID, AR.ACTION_ID
FROM   SO_RESULTS R, SO_ACTION_RESULTS AR
WHERE  AR.RESULT_ID = R.RESULT_ID

The join key is RESULT_ID, carried on both sides. Because the view uses an equi-join on that column, any row in SO_RESULTS that has no corresponding row in SO_ACTION_RESULTS is excluded, and vice versa. Consumers should therefore treat the view as representing only result-to-action pairings that are complete on both sides.

Key Columns

  • RESULT_NAME – the NAME attribute of the SO_RESULTS record. This is the human-readable label of the result, such as CLOSED or FIXED. It is aliased RESULT_NAME to distinguish it from other name columns and is the primary descriptive identifier returned by the view.
  • DESCRIPTION – the description text defined on the SO_RESULTS record, providing the semantic meaning of the result code.
  • RESULT_ID – the numeric primary key of the result definition. Returned from SO_ACTION_RESULTS but equal to the SO_RESULTS key used in the join, so it identifies the result itself.
  • ACTION_ID – the identifier of the action associated with the result. This column is sourced exclusively from SO_ACTION_RESULTS and provides the linkage to the action object. A given RESULT_ID may appear multiple times if multiple actions reference the same result.

Common Use Cases and Queries

Typical uses include enumerating the valid results for a given action, producing reference lists for service request reporting, and driving lookup validation in integrations. A simple listing follows:

SELECT RESULT_NAME, DESCRIPTION, RESULT_ID, ACTION_ID
FROM   APPS.SO_VALID_RESULTS_V;

To retrieve the results tied to one action:

SELECT RESULT_NAME, DESCRIPTION, RESULT_ID
FROM   APPS.SO_VALID_RESULTS_V
WHERE  ACTION_ID = :p_action_id;

To find all actions associated with a known result name:

SELECT RESULT_NAME, ACTION_ID
FROM   APPS.SO_VALID_RESULTS_V
WHERE  RESULT_NAME = 'CLOSED';

Because the view is read-only and supplied directly by Oracle, no modification statements should be issued against it. When additional result attributes beyond NAME and DESCRIPTION are required, the underlying SO_RESULTS table must be queried directly, as the view exposes only the four documented columns.