Search Results hazard_code_ext

Overview

The RLM_SCHEDULE_ITEMS_V view is a Release Management (RLM) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents schedule item information for customer release and scheduling transactions, consolidating both interface-staged records and schedule line entries into a single, query-friendly structure. The view is defined with a SELECT DISTINCT construct and exposes an ORIGIN_TABLE column whose literal value is set to 'INTERFACE' for the rows originating from the interface source. This design allows downstream consumers — reports, custom concurrent programs, and integration extracts — to distinguish the source of each schedule item row while presenting a consistent column list.

The view's primary role is to provide a denormalized, flattened read model of release management scheduling data, including shipping, packing, hazardous material, and customer pricing attributes. It is typically consumed rather than maintained, and is not itself an interface table for inbound data loading.

Underlying Base Objects

Per the documented metadata, RLM_SCHEDULE_ITEMS_V is defined over three referenced base objects:

• RLM_INTERFACE_LINES_ALL (SYNONYM) — the interface lines table holding staged, external customer schedule item data awaiting processing into Release Management.
• RLM_SCHEDULE_INTERFACE_HDR_V (VIEW) — a header-level interface view supplying schedule header context, joined to the line-level data.
• RLM_SCHEDULE_LINES_ALL (SYNONYM) — the core schedule lines table containing the persisted, processed schedule item records.

The view therefore bridges the interface and the persistent schedule layers, exposing columns prefixed with _EXT (external/interface-oriented attributes) alongside standard identifiers such as SCHEDULE_ITEM_NUM, HEADER_ID, INVENTORY_ITEM_ID, and CUSTOMER_ITEM_ID. The ORIGIN_TABLE literal confirms that the documented excerpt reflects the interface branch of the union-style definition.

Key Columns

• SCHEDULE_ITEM_NUM / HEADER_ID — the schedule item identifier and its parent schedule header.
• CUSTOMER_ITEM_ID / INVENTORY_ITEM_ID — links to the customer item definition and the internal inventory item master.
• CUST_SHIP_FROM_ORG_EXT / SHIP_FROM_ORG_ID — ship-from organization context, matching the shipping setup used in release management.
• CUST_SHIP_TO_EXT / CUST_BILL_TO_EXT / CUST_INTRMD_SHIP_TO_EXT — ship-to, bill-to, and intermediate ship-to party references.
• Address columns — SHIP_TO_* and SHIP_FROM_* components (name, address lines, city, county, postal code, province, state, country) for label and document printing.
• SHIP_LABEL_INFO_LINE_1 … _10 — pre-formatted shipping label information lines.
• Hazard and handling columns — HAZARD_CODE_EXT, HAZARD_DESCRIPTION_EXT, HANDLING_CODE_EXT, RETURN_CONTAINER_EXT.
• Commercial columns — CUST_PO_NUMBER, CUST_PO_DATE, CUST_PO_RELEASE_NUM, CUST_PO_LINE_NUM, CUST_CONTRACT_NUM_EXT, IMPORT_LICENSE_EXT, LETTER_CREDIT_EXT, CUST_ITEM_PRICE_EXT.

Note that the metadata does not explicitly list a CUSTOMER_DOCK_CODE column, although the search term customer_dock_code suggests a related docking attribute may be stored in the interface header (RLM_SCHEDULE_INTERFACE_HDR_V) or the underlying line tables rather than in this view's projection.

Common Use Cases and Queries

Typical usage includes release management reporting, integration extracts for EDI/ASN processing, and label or document printing. A standard query filters on a schedule header:

• Report all scheduled items for a customer shipment.
• Extract interface-staged items for a given customer PO.
• Print shipping labels using the pre-formatted label lines and address columns.

SELECT schedule_item_num,
       item_description_ext,
       customer_item_ext,
       cust_po_number,
       ship_to_name_ext,
       cust_item_price_ext,
       origin_table
  FROM apps.rlm_schedule_items_v
 WHERE header_id = :p_header_id
 ORDER BY schedule_item_num;

Because the view uses SELECT DISTINCT, results are deduplicated across the interface and schedule sources, making it suitable as a consolidated read source.