Search Results order_category




Overview
Explore in AI Chat

Overview

SO_HEADERS_IOP_115_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It is registered under the Order Entry (OE) product family and carries a VALID status in the ETRM object repository. The view exposes a horizontal projection of order header data drawn from SO_HEADERS_ALL, including the ORDER_CATEGORY attribute that users frequently search on when classifying and filtering sales orders. Its defining characteristic is that it is an organization-scoped (multi-org secured) view: the WHERE clause evaluates the session context held in USERENV('CLIENT_INFO') and restricts returned rows to the organization identifier recorded there. Because the IOP views were originally created to support the Oracle Order Entry/Order Management integration with Process Manufacturing and related Oracle Applications flows, SO_HEADERS_IOP_115_V functions as a runtime-facing API view consumed by internal forms, concurrent programs, and interface routines rather than as a standalone data dictionary object. For the purposes of reporting, it presents a lightweight, security-filtered subset of header-level columns suitable for joins to order lines, customers, and order types.

Underlying Base Objects

The documented referenced base object is SO_HEADERS_ALL, accessed through a synonym. The view definition selects directly from SO_HEADERS_ALL without any joins or UNION operations, so all columns are sourced from that single table. This establishes a one-to-one cardinality relationship between the view and the base table: every qualifying row in SO_HEADERS_ALL produces exactly one row in the view. The multi-org predicate is applied against ORG_ID, wrapped in an NVL expression that assigns a sentinel value of -99 when neither the ORG_ID column nor the CLIENT_INFO context resolves to a numeric organization. The CLIENT_INFO string is parsed by taking the first character and, if it is not a space, the first ten characters as the organization identifier. This is the classic multi-org access mechanism and means callers must initialize the session context (for example, through the FND_CLIENT_INFO initialization or the standard multi-org switching logic) before querying the view; otherwise the ORG_ID effectively defaults to -99 and no rows are returned.

Key Columns

Common Use Cases and Queries

Typical uses include order-header extracts, customer order summaries, and category-based segmentation reports. A representative query that filters by ORDER_CATEGORY and returns the most recent orders is:

  • SELECT HEADER_ID, ORG_ID, ORDER_NUMBER, ORDER_TYPE_ID, ORDER_CATEGORY, CUSTOMER_ID, CREATION_DATE FROM APPS.SO_HEADERS_IOP_115_V WHERE ORDER_CATEGORY = 'ORDER' AND CREATION_DATE >= TRUNC(SYSDATE) - 30;
  • Joining to SO_HEADERS_ALL or OE_ORDER_HEADERS_ALL through HEADER_ID when columns not exposed by the view are required.
  • Embedding the view in inbound or outbound interface programs that rely on implicit operating-unit scoping instead of explicit ORG_ID predicates.

Because the view resolves ORG_ID from the session context, any query executed outside a properly initialized multi-org environment may return no rows; reports should therefore set the operating unit context before invoking it, or fall back to SO_HEADERS_ALL with an explicit ORG_ID filter for administrative purposes.