Search Results pos_horizontal_schedule_v




Overview
Explore in AI Chat

Overview

The APPS.POS_HORIZONTAL_SCHEDULE_V view is a reporting and inquiry object within the Oracle Purchasing (PO) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It is classified as a VALID view owned by the APPS schema and is used to present horizontal schedule data — that is, schedule lines and their associated bucket values arranged across a fixed set of columns rather than as a vertical list of rows. This horizontal orientation is characteristic of inquiry and reporting screens where quantities, dates, or bucket descriptors must be displayed side by side for a given schedule item.

The view's central purpose is to translate raw schedule data stored in a vertical or normalized form into a presentation-friendly layout. Each row returned by the view represents a schedule line, with up to ten individual column values (COLUMN1 through COLUMN10) exposed. Because different inquiry contexts require different representations of these values — bucket types, formatted dates, or plain character values — the view applies conditional DECODE logic driven by the ROW_SELECT_ORDER and ROW_TYPE columns to decide how each value is rendered.

Underlying Base Objects

The view is defined over four documented base objects:

  • CHV_HORIZONTAL_SCHEDULES (SYNONYM) — the primary data source. Columns such as SCHEDULE_ID, SCHEDULE_ITEM_ID, ROW_SELECT_ORDER, ROW_TYPE, and COLUMN1 through COLUMN10 are drawn from this object, which holds the horizontal schedule layout in its underlying structure.
  • CHV_INQ_SV (PACKAGE) — a server-side PL/SQL package invoked through the CHV_INQ_SV.GET_BUCKET_TYPE function. This function is called when ROW_SELECT_ORDER equals 1, converting a stored value into a bucket type description.
  • PO_LOOKUP_CODES (VIEW) — used to resolve the DISPLAYED_FIELD and its associated DESCRIPTION (aliased as POLC.DESCRIPTION). For bucket descriptor rows, the description is suppressed by returning NULL.
  • FND_GLOBAL (PACKAGE) — the standard Oracle Application Object Library package that provides session context, typically supplying the logged-in user for audit columns such as LAST_UPDATED_BY and CREATED_BY.

The relationship between the view and its base objects is direct: CHV_HORIZONTAL_SCHEDULES supplies the schedule data, PO_LOOKUP_CODES enriches it with display labels, and the CHV_INQ_SV package provides derived bucket type values at query time.

Key Columns

  • SCHEDULE_ID — identifier of the header schedule to which the row belongs.
  • SCHEDULE_ITEM_ID — identifier of the specific schedule item or line within the schedule.
  • ROW_SELECT_ORDER — controls the rendering logic applied to each COLUMN value. When set to 1, values are passed through CHV_INQ_SV.GET_BUCKET_TYPE; when set to 2, values are treated as dates in YYYY/MM/DD format; otherwise raw values are returned.
  • ROW_TYPE — distinguishes row categories such as 'BUCKET_DESCRIPTOR'. For descriptor rows the lookup description is set to NULL.
  • DISPLAYED_FIELD — the lookup field code resolved from PO_LOOKUP_CODES, giving the label associated with the row.
  • COLUMN1 through COLUMN10 — the ten horizontal value positions, conditionally decoded according to ROW_SELECT_ORDER.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns populated from the underlying schedule record.

Common Use Cases and Queries

This view is typically consumed by Purchasing inquiry forms and custom reports that must display schedule quantities or bucket information horizontally. A basic retrieval filters by schedule identifiers:

  • SELECT schedule_id, schedule_item_id, row_type, displayed_field, column1, column2, column3 FROM apps.pos_horizontal_schedule_v WHERE schedule_id = :p_schedule_id ORDER BY row_select_order, schedule_item_id;
  • SELECT schedule_item_id, column1, column2, column3, column4 FROM apps.pos_horizontal_schedule_v WHERE schedule_id = :p_schedule_id AND row_type = 'BUCKET_DESCRIPTOR';

Because the view relies on CHV_INQ_SV and FND_GLOBAL, it should be queried within an initialized EBS session where the APPS schema and package state are valid. Performance is generally acceptable for single-schedule lookups, but large-scale extraction should filter on SCHEDULE_ID or SCHEDULE_ITEM_ID to avoid full scans of the underlying synonym. The view is read-only and is not intended as a target for DML.