Search Results so_results_b




Overview
Explore in AI Chat

Overview

The SO_RESULTS_B table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for predefined results or outcomes of order cycle actions. An order cycle is a workflow that defines the sequence of statuses an order line passes through from entry to fulfillment. This table is essential for the Order Management engine, as it stores the discrete states (e.g., "Entered," "Awaiting Shipping," "Closed") that can be assigned to an order or order line during its lifecycle. The results defined in this table are referenced by various approval, security, and processing rules to govern order progression and enforce business logic.

Key Information Stored

While the provided metadata does not list specific columns beyond the primary key, the structure and relationships indicate the table's critical data elements. The primary key column is RESULT_ID, a unique identifier for each cycle action result. Based on its functional role and foreign key relationships, the table likely contains descriptive columns such as NAME, CODE, or DESCRIPTION to define the result (e.g., "APPROVED," "REJECTED," "PENDING"). It may also include columns for controlling the workflow sequence, such as SEQUENCE_NUMBER or TYPE. The data in this table is typically static, configured during implementation to reflect the organization's specific order fulfillment workflow stages.

Common Use Cases and Queries

This table is primarily used for setup, reporting, and troubleshooting the order workflow. A common administrative task is querying all available results to understand the order cycle. A typical query would be: SELECT result_id, name, description FROM oe.so_results_b ORDER BY name;. For troubleshooting, one might join to transactional tables to find orders stuck in a particular state. For instance, to see orders currently in an "Entered" state via the interface table: SELECT shia.header_interface_id, shia.order_number FROM so_headers_interface_all shia JOIN so_results_b sr ON shia.entered_state_id = sr.result_id WHERE sr.name = 'ENTERED';. Reporting use cases include analyzing approval outcomes by joining to SO_ORDER_APPROVALS or SO_LINE_APPROVALS on the RESULT_ID field.

Related Objects

The SO_RESULTS_B table has a central role, referenced by numerous key tables in the Order Entry schema. The documented foreign key relationships are as follows:

  • SO_ACTIONS: References SO_RESULTS_B via SO_ACTIONS.PASSING_RESULT_ID. Defines the result that allows an action to proceed.
  • SO_ACTION_PRE_REQS: References SO_RESULTS_B via SO_ACTION_PRE_REQS.RESULT_ID. Ties prerequisite conditions to a specific result.
  • SO_ACTION_RESULTS: References SO_RESULTS_B via SO_ACTION_RESULTS.RESULT_ID. Maps possible results to specific actions.
  • SO_HEADERS_INTERFACE_ALL: References SO_RESULTS_B via SO_HEADERS_INTERFACE_ALL.ENTERED_STATE_ID. Tracks the current cycle state of orders in the interface.
  • SO_LINE_APPROVALS: References SO_RESULTS_B via SO_LINE_APPROVALS.RESULT_ID. Stores the approval result (e.g., Approved/Rejected) for an order line.
  • SO_ORDER_APPROVALS: References SO_RESULTS_B via SO_ORDER_APPROVALS.RESULT_ID. Stores the approval result for an order header.
  • SO_SECURITY_RULES: References SO_RESULTS_B via SO_SECURITY_RULES.RESULT_ID. Associates security rules with specific order cycle results.
These relationships underscore the table's function as the definitive source for valid order statuses used across the order management system.