Results for “lang_code”

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

Overview

OP_ORDR_STS_B is a foundational setup table owned by the GML schema (Process Manufacturing Logistics) in Oracle EBS 12.1.1 and 12.2.2. It stores the valid order status codes and their descriptions that govern the lifecycle of process manufacturing order headers and lines. Because both OP_ORDR_HDR and OP_ORDR_DTL reference this table through foreign keys, OP_ORDR_STS_B effectively acts as the controlled vocabulary for order state transitions — from entry through release, completion, and closure. Its primary key, OP_ORDR_STS_B_PK, is defined on the ORDER_STATUS column, and the table carries eleven documented columns.

From a Data Vault modeling perspective, this table is best classified as hub-leaning. The heuristic mining of the foreign-key structure indicates that ORDER_STATUS functions as a durable business key, and the surrounding descriptive attributes (LANG_CODE, ORDER_STATUS_CODE, TEXT_CODE, etc.) behave like satellite payload attached to that hub. In practice, the object is a low-volatility reference table rather than a transactional fact source.

Key Information Stored

The most significant columns documented for OP_ORDR_STS_B are:

• ORDER_STATUS — The surrogate primary key and sole column of OP_ORDR_STS_B_PK. It uniquely identifies each status code and is the value propagated into dependent tables. This column is simultaneously the PK and the business-key candidate (unique index).
• ORDER_STATUS_CODE — The human-readable or externally referenced status identifier used in reporting and interfaces.
• LANG_CODE — Language indicator supporting multilingual status descriptions.
• TEXT_CODE — Reference to translation or descriptive text maintained in the text/lookup infrastructure.
• TRANS_CNT — Transaction counter used for concurrency control and update tracking.
• CREATED_BY, CREATION_DATE — Standard WHO-column audit trail capturing record creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing the most recent modification and the responsible session.
• DELETE_MARK — Soft-delete flag indicating logical removal without physical deletion.

Note that ORDER_STATUS is both the surrogate primary key and the unique business key in this documented schema; the two roles are not separated by a distinct synthetic identifier. UPDATE_DATE and the WHO columns follow Oracle's standard Applications audit conventions.

Common Use Cases and Queries

Typical use cases center on status validation, joins to order headers and lines, and status-driven reporting. A frequent pattern joins the header to retrieve the status description:

SELECT h.ORDER_NO, h.ORDER_STATUS, s.ORDER_STATUS_CODE
FROM   GML.OP_ORDR_HDR h,
       GML.OP_ORDR_STS_B s
WHERE  h.ORDER_STATUS = s.ORDER_STATUS
AND    s.DELETE_MARK = 0;

The same pattern applies at line level against OP_ORDR_DTL.LINE_STATUS. Analysts commonly cross-reference status values to TEXT_CODE to obtain translated descriptions, and filter on DELETE_MARK to exclude logically retired codes. Because the table is small and stable, it is frequently cached in reporting extracts and used to populate list-of-values definitions in concurrent programs and OAF pages.

Related Objects

The following objects depend on or reference OP_ORDR_STS_B based on the documented FK/PK relationships:

• OP_ORDR_HDR — Foreign key on the ORDER_STATUS column; the header table consumes the status code to represent the overall order state.
• OP_ORDR_DTL — Foreign key on the LINE_STATUS column; each order line carries a status drawn from this table.
• OP_ORDR_STS_B_PK — The unique index enforcing the primary key on ORDER_STATUS and serving as the lookup path for all FK validation.

These three relationships constitute the documented dependency footprint. Because OP_ORDR_HDR and OP_ORDR_DTL are the principal transactional tables of Process Manufacturing Logistics, any modification to status codes in OP_ORDR_STS_B has an immediate and broad impact on order processing, validation logic, and status-based reporting across the GML module.