Results for “schedule_document_type”

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

Overview

APPS.CHV_ITEM_ORDERS_V is a consolidated reporting view within the Oracle E-Business Suite Procurement and Supply Chain modules. It presents item ordering and scheduling data originating from the CHV (Supplier Scheduling / Collaborative Planning) schema alongside associated purchasing document information. The view unifies ordering details with the release documents against which those orders were placed, giving visibility into supply commitments, quantities, and due dates at the schedule-item level.

The name of the view exposes its dual lineage: "ITEM_ORDERS" from the CHV scheduling data, filtered and enriched with PO release information. It is most relevant to purchasing, planning, and supplier scheduling flows where order quantity, unit of measure, promise dates, and the supporting purchase release must be reported together.

Underlying Base Objects

The view is defined over a UNION of two query branches, each joining CHV scheduling tables to Purchasing tables. The documented referenced objects are:

• CHV_ITEM_ORDERS (synonym) — the driving fact source for quantities, due dates, unit of measure, and descriptive flexfield attributes.
• CHV_SCHEDULE_ITEMS (synonym) — schedule header/item context, joined via SCHEDULE_ID and SCHEDULE_ITEM_ID.
• PO_RELEASES_ALL (synonym) — the purchasing release documents, linked by PO_RELEASE_ID.
• PO_HEADERS_ALL (synonym) — header for the release, joined via POR.PO_HEADER_ID.
• PO_LINES_ALL (synonym) — line-level data via DOCUMENT_LINE_ID.
• PO_LINE_LOCATIONS (synonym) — shipment-level detail, supplying ORG_ID and the shipment link.
• PO_DOCUMENT_TYPES (synonym) — restricts the query to RELEASE document types.
• PO_LOOKUP_CODES (view) — a lookup view filtered for the SCHEDULE_DOCUMENT_TYPE and AUTHORIZATION STATUS lookup types.
• PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES (synonyms) — used in the alternate UNION branch to surface requisition-based supply.
• FND_GLOBAL (package) — supplies session context (for example, ORG_ID) for organization-level filtering.

Each branch of the UNION applies filters restricting SUPPLY_DOCUMENT_TYPE to 'RELEASE' and joins the PO_LOOKUP_CODES view to resolve display values.

Key Columns

• SCHEDULE_ID / SCHEDULE_ITEM_ID / SCHEDULE_ORDER_ID — schedule and order identifiers that tie each row back to the CHV scheduling structure.
• SUPPLY_DOCUMENT_TYPE — the type of supply document; constrained to 'RELEASE' in the view definition.
• DISPLAYED_FIELD (PLC2) — the user-facing lookup description for the SCHEDULE_DOCUMENT_TYPE lookup type, derived from PO_LOOKUP_CODES.
• ORDER_QUANTITY, PURCHASING_UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE — ordered amount and associated UOMs.
• DUE_DATE — the scheduled or promised delivery date.
• PO_RELEASE_ID, DOCUMENT_LINE_ID, DOCUMENT_SHIPMENT_ID — keys linking the row to the release header, PO line, and shipment location.
• SEGMENT1||'-'||RELEASE_NUM, REVISION_NUM, LINE_NUM, SHIPMENT_NUM — human-readable release, revision, line, and shipment references.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns for extensible attributes.
• LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — audit and concurrent program columns.
• ORG_ID — operating unit identifier sourced from PO_LINE_LOCATIONS, enabling multi-org filtering.

Common Use Cases and Queries

The view is frequently used to report supplier scheduling orders alongside their purchase releases, reconcile scheduled quantities to release lines, and expose schedule document type descriptions. Because the "SCHEDULE_DOCUMENT_TYPE" lookup drives the DISPLAYED_FIELD column, it is commonly selected when a report must label the document type.

A representative query lists schedule orders and their release references:

• SELECT schedule_id, schedule_item_id, order_quantity, due_date, due_date, displayed_field, shipment_num FROM apps.chv_item_orders_v WHERE org_id = :org_id ORDER BY due_date;
• SELECT po_release_id, segmentation_release, line_num, order_quantity, due_date FROM apps.chv_item_orders_v WHERE schedule_id = :schedule_id;

Because ORG_ID is exposed, queries should apply operating unit predicates to enforce multi-org security. The view joins across CHV and PO schemas, so performance depends on indexes on SCHEDULE_ID, PO_RELEASE_ID, and LINE_LOCATION_ID in the underlying tables.