Results for “column_size”

2 results




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

Overview

The SO_ATTRIBUTES table, owned by the OE (Order Entry) schema, defines the attribute metadata available to Oracle E-Business Suite's order entry security rules and standard value rule sets. Each row describes a single attribute — its code, display name, physical column binding, data type, and optional descriptive flexfield association — that can be referenced by security rules (SO_SECURITY_RULES) and standard value rules (SO_STANDARD_VALUE_RULES) to control order entry behavior, defaulting, and access.

Within the broader Order Management configuration model, SO_ATTRIBUTES acts as the definitional backbone for rules that evaluate order header, line, and related entity values. It anchors attributes to logical objects defined in SO_OBJECTS, allowing EBS to express rules against named business entities such as order headers, lines, or pricing attributes. From a Data Vault modeling perspective, the table's FK topology is hub-leaning: it is referenced by multiple dependent tables while carrying only a small number of outbound references, suggesting a natural candidate for a hub with supporting descriptive satellites.

Key Information Stored

The primary surrogate key is ATTRIBUTE_ID, enforced by SO_ATTRIBUTES_PK and reinforced by unique index SO_ATTRIBUTES_U1. Three additional unique indexes define business-key candidates:

Among the 36 documented columns, the most operationally significant are:

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE1–15 extension columns are also present.

Common Use Cases and Queries

Typical reporting and diagnostics include enumerating attributes per object, tracing which attributes drive a given security rule, and identifying flexfield-backed attributes.

  • List attributes for a specific order object: SELECT attribute_code, name, column_name, data_type_code FROM oe.so_attributes WHERE object_id = :p_object_id ORDER BY sequence_number;
  • Trace security rule usage: join SO_SECURITY_RULES on ATTRIBUTE_ID to see which attributes participate in rule sets.
  • Audit flexfield-derived attributes: SELECT a.attribute_code, a.descriptive_flexfield_name, a.desc_flex_application_id FROM oe.so_attributes a WHERE a.desc_flex_application_id IS NOT NULL;
  • Standard value rule linkage: join to SO_STANDARD_VALUE_RULES and SO_ATTRIBUTE_STD_VALUE_SOURCES on ATTRIBUTE_ID to enumerate value sources backing a given attribute.

Related Objects

  • SO_OBJECTS — parent object definition; joined via SO_ATTRIBUTES.OBJECT_ID and SO_ATTRIBUTES.REPRESENTED_OBJECT_ID.
  • FND_DESCRIPTIVE_FLEXS — flexfield linkage via DESCR_FLEX_APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME.
  • SO_ATTRIBUTE_USES — child table keyed by ATTRIBUTE_ID describing how attributes are consumed.
  • SO_ATTRIBUTE_STD_VALUE_SOURCES — child table keyed by ATTRIBUTE_ID listing available value sources.
  • SO_SECURITY_RULES — references ATTRIBUTE_ID to bind attributes into security rule predicates.
  • SO_STANDARD_VALUE_RULES — references ATTRIBUTE_ID to bind attributes into defaulting and validation rule sets.