Search Results attribute_description




Overview

The SO_STANDARD_VALUE_SOURCES view is a seeded, read-only database object owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides within the Order Entry (OE) product family and exposes the set of standard value source rules that Oracle seeds to drive defaulting and validation logic in the ordering flow. A "standard value source" defines where an attribute value originates — for example, a system default, a related object attribute, or a general source — and is referenced by the attribute defaulting framework when populating order headers, lines, and related entities. Because the view consolidates both object-bound value sources and general system-level sources into a single result set, it provides a normalized reporting surface for the seeded defaulting configuration without requiring consumers to union the underlying tables manually.

In reporting and integration contexts, this view is typically used to answer configuration and traceability questions: which attributes have value sources defined, which represented objects they map to, and what the human-readable attribute and object names and descriptions are for a given source.

Underlying Base Objects

The documented view definition is a UNION of two SELECT statements over four referenced base objects (all exposed as synonyms in APPS): SO_ATTRIBUTES, SO_ATTRIBUTE_USES, SO_OBJECTS, and SO_GENERAL_STD_VALUE_SOURCES.

  • The first branch joins SO_OBJECTS to SO_ATTRIBUTES on OBJECT_ID, then to SO_ATTRIBUTE_USES on ATTRIBUTE_ID, filtering where ATTRIBUTE_USE_CODE equals 'STANDARD VALUE SOURCE'. This branch surfaces attribute-level value sources tied to a specific represented object.
  • The second branch selects directly from SO_GENERAL_STD_VALUE_SOURCES, returning general (non-object-specific) standard value sources with a literal REPRESENTED_OBJECT_ID and OBJECT_ID of -1 and NULL values for the attribute-specific columns.

The UNION yields a consistent column shape across both object-bound and general sources, which is central to how downstream defaulting logic resolves a value source regardless of its scope.

Key Columns

  • STANDARD_VALUE_SOURCE_ID — Primary identifier for the value source. In the first branch it is the attribute ID; in the second it is the general standard value source ID.
  • ATTRIBUTE_CODE — Code of the attribute that owns the value source; NULL for general sources.
  • ATTRIBUTE_NAME — Seeded display name of the attribute; NULL for general sources.
  • ATTRIBUTE_DESCRIPTION — Descriptive text for the attribute, the column most often targeted by searches such as "attribute_description"; NULL for general sources.
  • REPRESENTED_OBJECT_ID — Identifier of the object the attribute represents; returns -1 for general sources.
  • OBJECT_ID — Identifier of the owning object; -1 for general sources.
  • OBJECT_CODE, OBJECT_NAME, OBJECT_DESCRIPTION — Object-level metadata describing the entity to which the attribute belongs; OBJECT_NAME and OBJECT_DESCRIPTION are populated for general sources while OBJECT_CODE remains NULL.

Common Use Cases and Queries

Typical uses include auditing seeded defaulting configuration, tracing where an order attribute derives its value, and building custom lookups that present friendly attribute and object descriptions to end users.

  • Searching for a specific attribute by description:

    SELECT standard_value_source_id, attribute_code, attribute_name, attribute_description, object_name FROM so_standard_value_sources WHERE attribute_description IS NOT NULL;

  • Listing all object-bound value sources with their represented objects:

    SELECT attribute_code, object_code, object_name FROM so_standard_value_sources WHERE represented_object_id <> -1;

  • Isolating general (non-object) sources:

    SELECT standard_value_source_id, object_name, object_description FROM so_standard_value_sources WHERE object_id = -1;

Because the view is seeded and read-only, it should be queried rather than modified; underlying configuration changes are made through the Order Management setup forms that populate SO_ATTRIBUTES, SO_ATTRIBUTE_USES, and SO_GENERAL_STD_VALUE_SOURCES.