Results for “so_attr_std_value_sources_u2”

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

Overview

The SO_ATTRIBUTE_STD_VALUE_SOURCES table resides in the OE (Order Entry) schema and is a core configuration object within Oracle EBS Order Management. It defines the sources from which standard values are derived for order line and order header attributes used by the attribute-based pricing, validation, and defaulting engine (commonly associated with Oracle Advanced Pricing and the attribute framework). Each row associates an ATTRIBUTE_ID defined in SO_ATTRIBUTES with a source identifier that determines how the standard value for that attribute is resolved at runtime.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this entity is satellite-leaning. Because it carries descriptive attributes keyed by a surrogate identifier and references a parent attribute definition, it behaves more like a descriptive satellite than a pure hub or link, though analysts may model it flexibly depending on integration requirements.

Key Information Stored

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

• ATTRIBUTE_STD_VALUE_SOURCE_ID — the surrogate primary key (SO_ATTR_STD_VALUE_SOURCES_PK / SO_ATTR_STD_VALUE_SOURCES_U1) that uniquely identifies each source-binding record.
• ATTRIBUTE_ID — foreign key to SO_ATTRIBUTES, identifying the order attribute whose standard value source is being defined. Together with STANDARD_VALUE_SOURCE_ID it forms the business-key unique index SO_ATTR_STD_VALUE_SOURCES_U2.
• STANDARD_VALUE_SOURCE_ID — the second half of the composite unique key, designating the source entity or definition used to resolve the attribute value.
• CONTEXT — the descriptive flexfield context segment that carries the DFF structure for the row.
• ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) segment columns, used for customer-defined extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns providing audit and change-tracking information.

The composite unique index on (ATTRIBUTE_ID, STANDARD_VALUE_SOURCE_ID) enforces that a given attribute maps to a source only once, which is the primary integrity rule governing configuration.

Common Use Cases and Queries

Typical usage centers on validating attribute-to-source configuration, troubleshooting defaulting behavior, and generating setup reports. A sample query retrieving all sources for a given attribute:

• SELECT s.ATTRIBUTE_STD_VALUE_SOURCE_ID, s.ATTRIBUTE_ID, a.ATTRIBUTE_CODE, s.STANDARD_VALUE_SOURCE_ID FROM OE.SO_ATTRIBUTE_STD_VALUE_SOURCES s, OE.SO_ATTRIBUTES a WHERE s.ATTRIBUTE_ID = a.ATTRIBUTE_ID;
• Reporting on all configured standard value sources to audit attribute setup during implementation or upgrade.
• Joining to source tables (e.g., pricing lists or qualifier definitions) to reconcile which sources populate order attributes.
• Investigating duplicate or conflicting source bindings using the SO_ATTR_STD_VALUE_SOURCES_U2 unique constraint.
• Data migration validation to confirm attribute-source relationships before loading into a target environment.

Related Objects

The most significant related objects, based on the documented foreign-key relationship, include:

• SO_ATTRIBUTES — referenced via SO_ATTRIBUTE_STD_VALUE_SOURCES.ATTRIBUTE_ID; the parent definition of order attributes.
• SO_ATTRIBUTE_STD_VALUE_SOURCES indexes (SO_ATTR_STD_VALUE_SOURCES_PK, U1, U2) — enforce uniqueness and drive lookups.
• Attribute framework tables such as SO_ATTRIBUTES-related source definitions and pricing attribute qualifiers that reference STANDARD_VALUE_SOURCE_ID.
• Order Management setup and validation APIs that read this configuration when defaulting and validating attribute values.
• Reporting views in the OE schema that expose attribute-source associations for administrative dashboards.

Because the documented metadata is concentrated on this configuration entity, administrators should treat SO_ATTRIBUTES as the primary join partner and exercise caution when altering existing rows, as changes directly affect order attribute defaulting and validation behavior.