Results for “so_results_b”

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

Overview

SO_RESULTS_B is a foundational configuration table in the Oracle E-Business Suite Order Entry (OE) module, owned by the OE schema. In Oracle EBS 12.1.1 and 12.2.2, this table stores the cycle action results for order cycles. Order cycles are the sequential workflow stages that Oracle Order Management applies to sales orders—such as booking, fulfillment, invoicing, and shipping—and each cycle contains a set of actions whose outcomes must be evaluated before subsequent steps execute. SO_RESULTS_B persists the definition of those outcomes, providing the reference data against which order approval, security rule evaluation, prerequisite checking, and workflow transitions are validated.

From a dimensional modeling perspective, the provided metadata classifies this object as hub-leaning, mined heuristically from its foreign key structure. In Data Vault terms, SO_RESULTS_B behaves like a hub: it carries a single surrogate primary key (RESULT_ID) that is referenced by many surrounding tables, but it does not store relationships between multiple business entities itself. This classification is a modeling suggestion rather than an Oracle-declared designation; the table functions in practice as a central reference point for cycle and action result codes.

Key Information Stored

SO_RESULTS_B contains 24 documented columns. The most significant are listed below:

• RESULT_ID — The surrogate primary key of the table, enforced by the SO_RESULTS_B_PK constraint and also by the unique index SO_RESULTS_B_U1. RESULT_ID is the single column that every dependent foreign key references, making it the business-key candidate and the join anchor for all related objects.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating columns that define the active window during which a result definition is valid. These support date-ranged lookups and prevent obsolete results from being applied to new order cycles.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO-column audit fields that capture row creation and modification history.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle descriptive flexfield (DFF) columns. These hold client-specific extensions configured when the descriptive flexfield is enabled on the results entity, allowing organizations to store additional result metadata without schema changes.

The table does not carry a natural-language description or name column in the documented column list; the semantic meaning of each RESULT_ID is established through the dependent tables and their reference to this hub.

Common Use Cases and Queries

The primary use case is resolving the outcome associated with order cycle actions. Typical queries join SO_RESULTS_B to the approval, security, and prerequisite tables that carry RESULT_ID:

• Listing active results for a given point in time: SELECT RESULT_ID, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OE.SO_RESULTS_B WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Determining which security rules resolve to a result: SELECT s.SECURITY_RULE_ID, r.RESULT_ID FROM OE.SO_SECURITY_RULES s, OE.SO_RESULTS_B r WHERE s.RESULT_ID = r.RESULT_ID;
• Auditing approval outcomes by joining SO_ORDER_APPROVALS or SO_LINE_APPROVALS to SO_RESULTS_B on RESULT_ID.
• Validating cycle action prerequisites through SO_ACTION_PRE_REQS.RESULT_ID.
• Inspecting DFF content via ATTRIBUTE1–ATTRIBUTE15 where the results flexfield has been configured.

Because RESULT_ID is both the primary key and a unique-indexed business key, lookups by RESULT_ID are efficient and are the preferred access path for integration and reporting queries.

Related Objects

Seven documented foreign keys reference SO_RESULTS_B through RESULT_ID (or the equivalently typed PASSING_RESULT_ID and ENTERED_STATE_ID columns), identifying the most significant related objects:

• SO_ACTIONS — references SO_RESULTS_B via PASSING_RESULT_ID, linking cycle actions to the result they produce.
• SO_ACTION_PRE_REQS — references SO_RESULTS_B via RESULT_ID, defining prerequisite results for cycle actions.
• SO_ACTION_RESULTS — references SO_RESULTS_B via RESULT_ID, associating actions with their result definitions.
• SO_HEADERS_INTERFACE_ALL — references SO_RESULTS_B via ENTERED_STATE_ID, tying interface order headers to an entered state result.
• SO_LINE_APPROVALS — references SO_RESULTS_B via RESULT_ID for line-level approval outcomes.
• SO_ORDER_APPROVALS — references SO_RESULTS_B via RESULT_ID for header-level approval outcomes.
• SO_SECURITY_RULES — references SO_RESULTS_B via RESULT_ID, mapping security rule evaluation to a result.

These relationships confirm SO_RESULTS_B as a central hub within the Order Management cycle engine, with all dependent processing converging on the RESULT_ID key.