Search Results so_general_std_val_sources_u1




Overview

OE.SO_GENERAL_STD_VALUE_SOURCES is a seed data table in the Oracle Order Management (OE) schema that stores information about standard value sources which are not associated with any specific object or attribute. In the Oracle E-Business Suite Order Management architecture, standard value sources are the lookup mechanisms used by the Order Management flexfield and defaulting framework to derive values dynamically at runtime. Whereas object- or attribute-specific value sources are tied to a particular entity, the general standard value sources defined in this table are global in scope and may be referenced from anywhere in the defaulting rule engine.

The documented sources supported by this table are Value, Profile Option, and Current Date. The table resides in the APPS_TS_SEED tablespace, consistent with its role as seeded reference data rather than transactional data. Under the heuristic Data Vault classification derived from its foreign key structure, this object is modeled as a standalone entity — it holds no enforced foreign key dependencies to other tables, functioning as an independent reference hub of general value source definitions. This classification should be treated as a modeling suggestion rather than a dictated schema design.

Key Information Stored

The table is documented with 24 columns. The most operationally significant are:

  • GENERAL_STD_VALUE_SOURCE_ID — the system-generated surrogate primary key, uniquely identifying each general standard value source. It is backed by the primary key constraint SO_GENERAL_STD_VALUE_SOURCE_PK and by the unique index SO_GENERAL_STD_VAL_SOURCES_U1, the index the user searched for.
  • NAME — the business name of the general standard value source, up to 40 characters. This column is a business-key candidate, enforced by the unique index SO_GENERAL_STD_VAL_SOURCES_U2.
  • DESCRIPTION — a free-text description of the source, up to 240 characters.
  • CONTEXT — the descriptive flexfield structure defining column, up to 30 characters.
  • ATTRIBUTE1 through ATTRIBUTE15 — the Descriptive Flexfield (DFF) segment columns, each VARCHAR2(150), used to capture additional, implementation-specific context about a source without modifying the table structure.
  • Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — providing audit trail information.

The DISTINCTION between the surrogate key (GENERAL_STD_VALUE_SOURCE_ID) and the business-key candidate (NAME) is important when building integrations or reports, since external references to a source should ideally resolve by the ID while user-facing configuration typically addresses it by NAME.

Common Use Cases and Queries

Typical use cases center on inspecting, validating, and reporting on the seeded value sources that drive Order Management defaulting behavior. A common query retrieves sources by name:

  • SELECT general_std_value_source_id, name, description FROM oe.so_general_std_value_sources WHERE name = :p_name;
  • SELECT * FROM oe.so_general_std_value_sources WHERE context IS NOT NULL ORDER BY name; — to enumerate sources carrying DFF context assignments.
  • Reporting on audit freshness: SELECT name, creation_date, last_update_date FROM oe.so_general_std_value_sources ORDER BY last_update_date DESC;

Because the table is seed data, administrators and technical consultants frequently query it to confirm that the standard sources (Value, Profile Option, Current Date) are present and correctly defined before troubleshooting defaulting rules. The DFF ATTRIBUTE columns are sometimes used to hold implementation-specific tagging, so queries filtering on those attributes appear in customer-specific reporting.

Related Objects

Although the documented FK structure places this table as standalone, it participates logically with other Order Management reference objects:

Consult the OE schema reference for exact join columns, since no enforced FK relationships are documented for this standalone seed table.