Search Results so_orgn_code

Overview

GML_GASNO_ORDERS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the GML (Process Manufacturing Logistics) product family. Its documented purpose is to expose Sales Order Header information, consolidating header-level and selected first-line attributes from the Process Manufacturing order tables into a single, denormalized result set. The view is registered in ETRM with a VALID status, indicating it is a supported, compiled database object at the documented release level (12.1.1 / 12.2.2).

Because it returns order header context rather than transactional detail, the view serves primarily as a reporting and integration surface. It is commonly consumed by custom concurrent programs, Oracle Reports, BI Publisher data templates, and outbound interface logic that require a compact, query-friendly representation of Process Manufacturing sales orders without joining the underlying OP_ORDR tables directly. The name prefix (GML_GAS) reflects its origin in the Process Manufacturing Logistics schema, distinguishing it from the discrete Oracle Order Management (OE) order tables. A caller searching on the term order_comment is directed to this view because it exposes the ORDER_COMMENT column, which carries the free-text order-level comment captured on the order header.

Underlying Base Objects

The view text is defined over the following documented base objects:

• OP_ORDR_HDR (synonym) — the sales order header, aliased OH; supplies ORDER_ID, ORDER_STATUS, ORDER_NO, CUSTPO_NO, ORDER_DATE, ORGN_CODE, ORDER_COMMENT, and the twenty ATTRIBUTE columns. Filters require DELETE_MARK = 0 and ORDER_STATUS != -1.
• OP_ORDR_DTL (synonym) — the order detail/line table, aliased OD; joined on ORDER_ID and constrained to the minimum LINE_ID per order.
• OP_BILL_LAD (synonym) — billing/lading address data, aliased BL; joined via BOL_ID.
• OP_CUST_MST (synonym) — customer master, aliased CM; supplies customer context.
• OP_ORDR_STS (synonym) — order status codes, aliased OS; joined on ORDER_STATUS to translate the numeric status into ORDER_STATUS_CODE.
• GML_EC_CONTACT_V (view) — electronic commerce contact view, aliased ECC; provides contact information associated with the order.
• FND_PROFILE (package) — the standard EBS profile option API, referenced indirectly for profile-driven values.

The joins are driven by the header key ORDER_ID, and the detail join is deliberately restricted by a subquery so that only the first (minimum) LINE_ID of an order having shipment records is returned, preventing row multiplication at the header level.

Key Columns

• ORDER_ID — numeric primary key of the order header; the natural join key for downstream lookups.
• ORDER_NO — the human-readable order number.
• ORDER_STATUS / ORDER_STATUS_CODE — numeric status and its decoded status code from OP_ORDR_STS.
• CUSTPO_NO — the customer purchase order reference supplied on the order.
• ORDER_COMMENT — the free-text order-level comment; this is the column most relevant to searches for "order_comment".
• SO_ORGN_CODE — the order organization code.
• SO_DATE — the order date.
• SO_HEADER_CATEGORY and SO_HEADER_ATTRIBUTE1..30 — the descriptive flexfield context and the thirty attribute segments exposed for header-level DFF reporting.

Common Use Cases and Queries

Typical usage includes order-header extracts, order comment retrieval, and organization-level order reporting. A representative query returning the order comment and header context:

SELECT ORDER_NO, CUSTPO_NO, ORDER_STATUS_CODE,
       SO_ORGN_CODE, SO_DATE, ORDER_COMMENT
FROM   APPS.GML_GASNO_ORDERS_V
WHERE  ORDER_STATUS_CODE = 'ENTERED'
AND    SO_ORGN_CODE = 'M1';

To locate orders bearing a specific comment, a case-insensitive search is applied against ORDER_COMMENT combined with the order number and date for traceability. Reporting tools frequently select the DFF attributes to reproduce header flexfield values without navigating to the base table. Because the view enforces DELETE_MARK and status filtering, consumers receive only active, non-deleted orders, and the first-line restriction guarantees one row per qualifying order, making the view safe for header-level aggregation and interface staging.