Search Results general_std_value_source_id

Overview

SO_GENERAL_STD_VALUE_SOURCES is an Oracle E-Business Suite table owned by the OE (Order Entry) schema. It stores the predefined standard value rule sources used by Oracle Order Management's Standard Value functionality. In EBS 12.1.1 and 12.2.2, this table acts as a configuration repository: each row defines a named source that the Standard Value engine can resolve to a business value when processing an order, such as sourcing a default price list, salesperson, warehouse, or similar attribute from a predefined origin rather than manual entry.

The ETRM metadata documents the table under product OE - Order Entry with status VALID. The heuristic Data Vault classification mined from its foreign key structure is standalone, which suggests modeling this object as an independent reference (lookup) table rather than as a hub, link, or satellite. That classification reflects the absence of documented inbound or outbound foreign key relationships: the table functions primarily as a seeded, code-driven lookup list of standard value sources.

Key Information Stored

The table contains 24 documented columns. The most significant are:

• GENERAL_STD_VALUE_SOURCE_ID — the surrogate primary key, enforced by SO_GENERAL_STD_VALUE_SOURCE_PK and mirrored by the unique index SO_GENERAL_STD_VAL_SOURCES_U1. This is the internal identifier referenced by dependent configuration records.
• NAME — the business-key candidate, enforced by the unique index SO_GEN_STD_VALUE_SOURCE_UK1 / SO_GENERAL_STD_VAL_SOURCES_U2. The name is the human-readable label of the standard value source.
• DESCRIPTION — the descriptive text for the source, typically explaining its intended behavior.
• CONTEXT — the descriptive flexfield context column, which selects the applicable DFF structure for a row.
• ATTRIBUTE1 through ATTRIBUTE15 — the fifteen descriptive flexfield attribute segments available for customer-defined extensions. These allow sites to attach additional source metadata without schema change.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard EBS Who columns recording row creation and modification history.

A clear distinction exists between the surrogate key (GENERAL_STD_VALUE_SOURCE_ID) and the business keys. While the unique index U1 is built on the surrogate ID, U2 and the UK1 constraint establish NAME as the meaningful, user-facing identifier. Applications typically resolve sources by NAME when names are stable, and by ID when referential integrity with dependent configuration tables is required.

Common Use Cases and Queries

Typical usage centers on inspecting or validating Order Management Standard Value setup. A common query returns all available sources by name:

• SELECT general_std_value_source_id, name, description FROM oe.so_general_std_value_sources WHERE UPPER(name) LIKE 'SALES%' ORDER BY name;
• Verifying the surrogate-to-business-key mapping: SELECT name, general_std_value_source_id FROM oe.so_general_std_value_sources;
• Discovering site-defined extensions via DFF: SELECT name, context, attribute1, attribute2 FROM oe.so_general_std_value_sources WHERE context IS NOT NULL;
• Auditing change history: SELECT name, created_by, creation_date, last_updated_by, last_update_date FROM oe.so_general_std_value_sources ORDER BY last_update_date DESC;

Because the table is seeded and largely static, it is most often used as a lookup in joins that resolve a source ID to a source name in custom reports and diagnostic queries. Reporting use cases include generating configuration inventories of Standard Value sources, validating that every source ID referenced elsewhere resolves to a valid row, and confirming DFF context assignments before migration or upgrade testing.

Related Objects

The documented metadata describes this table as standalone, meaning no foreign key relationships were mined. In practice, dependent objects reference the source through the GENERAL_STD_VALUE_SOURCE_ID column, or through the NAME business key. Significant related objects include:

• Order Management Standard Value rule and setup tables in the OE schema that store a GENERAL_STD_VALUE_SOURCE_ID reference to this source.
• The corresponding _TL translation table, where multilingual installations store translated NAME and DESCRIPTION values keyed by GENERAL_STD_VALUE_SOURCE_ID.
• Descriptive flexfield metadata objects in the FND schema (FND_DESCRIPTIVE_FLEXS, FND_DESCR_FLEX_COL_USAGE) that define the CONTEXT and ATTRIBUTE segment structure.
• The OE_ORDER_HEADERS_ALL and order line tables, whose sourced attribute values may originate from a standard value source configured in this table.
• Concurrent programs and Standard Value Manager setup forms under the Order Management responsibility that insert and maintain rows here through the application layer, rather than direct DML.

Because the ETRM extraction records no explicit FK constraints, all joins to this table should be validated against the seeded data set, and direct DML should be avoided in favor of supported Order Management setup interfaces.