Search Results op_ordr_sts_b




Overview
Explore in AI Chat

Overview

The OP_ORDR_STS_B table is a foundational data object within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It functions as a master reference table, storing the definitive list of valid status codes for orders and their associated lines. This table is critical for maintaining data integrity and enforcing business rules across the order management lifecycle in a manufacturing context. By centralizing status definitions, it ensures consistent validation and reporting for order headers and detail lines, serving as a key component in the application's data model for tracking order progression from creation through to fulfillment and completion.

Key Information Stored

The table's primary purpose is to store status codes and their descriptions. While the specific column list is not detailed in the provided metadata, the structure of such reference tables in Oracle EBS typically includes a code column, a meaning or description column, and standard WHO columns. Based on the documented foreign key relationships, the core data elements are:

  • ORDER_STATUS: This is the primary key column (OP_ORDR_STS_B_PK) containing the short code that uniquely identifies an order status (e.g., 'ENTERED', 'RELEASED', 'CLOSED').
  • DESCRIPTION or MEANING: A complementary column providing the full, user-friendly name or explanation for the status code stored in ORDER_STATUS.
  • Additional columns likely include standard EBS attributes for enabling/disabling records (ENABLED_FLAG), controlling display sequence (DISPLAY_SEQUENCE), and tracking creation and modification details (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).

Common Use Cases and Queries

This table is primarily used for validation, reporting, and user interface support. A common use case is populating list of values (LOVs) in forms for the Order Status field on order headers and lines. For reporting, analysts frequently join this table to order transaction tables to translate status codes into readable descriptions. A typical query pattern involves joining to the main order tables to get a status description for all open orders:

SELECT hdr.order_number, sts_b.description AS order_status
FROM gml.op_ordr_hdr hdr,
     gml.op_ordr_sts_b sts_b
WHERE hdr.order_status = sts_b.order_status
AND sts_b.enabled_flag = 'Y';

Another critical use is in data validation scripts or API logic to verify that a status being applied to an order or line is a valid code present in this master table.

Related Objects

As documented in the provided metadata, OP_ORDR_STS_B has direct foreign key relationships with two primary transaction tables in the GML module, establishing its role as a key reference entity:

  • OP_ORDR_HDR (Order Header): The OP_ORDR_HDR.ORDER_STATUS column references OP_ORDR_STS_B.ORDER_STATUS. This defines the overall status of a manufacturing order.
  • OP_ORDR_DTL (Order Detail/Line): The OP_ORDR_DTL.LINE_STATUS column references OP_ORDR_STS_B.ORDER_STATUS. This defines the status of individual lines within a manufacturing order, allowing line-level status tracking independent of the header.

These relationships enforce referential integrity, ensuring that every status code on an order header or detail line exists in the OP_ORDR_STS_B master table.