Search Results max_order_quantity

Overview

APPS.CHV_SCHEDULE_ITEMS_V is a Supplier Scheduling (CHV) view that consolidates schedule line data with item master, planning, purchasing, and supplier authorization attributes. In Oracle EBS 12.1.1 and 12.2.2, it serves as a denormalized read model over the CHV_SCHEDULE_ITEMS and CHV_SCHEDULE_HEADERS tables, enriched with descriptive and planning columns sourced from Oracle Inventory, Oracle Purchasing, and Oracle HR. Because the status is VALID and the object is a view rather than a table, no physical storage or DML is associated with it; all access is read-only.

The view is particularly relevant to suppliers and planners who need to review item-level scheduling attributes such as minimum and maximum order quantities, fixed lot multipliers, cumulative and authorized quantities, and purchasing unit of measure. The MAXIMUM_ORDER_QUANTITY column of interest is sourced from MTL_SYSTEM_ITEMS, making this view a convenient single source for order quantity constraints alongside schedule context.

Underlying Base Objects

The view is defined with inner joins across several base objects and outer joins for buyer and planner name resolution:

• CHV_SCHEDULE_ITEMS and CHV_SCHEDULE_HEADERS — core scheduling data, joined on SCHEDULE_ID.
• MTL_PARAMETERS and MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV — joined on ORGANIZATION_ID and ITEM_ID, supplying item description, lead time, order quantity limits, lot multipliers, and concatenated segments.
• PO_ASL_ATTRIBUTES — supplies the approval/authorization flag and scheduler.
• PO_HEADERS and PO_LINES_ALL — supply the blanket/planned order context (segment, end date, line number).
• PER_PEOPLE_F (twice) — resolves buyer and planner full names, with SYSDATE BETWEEN effective date ranges and outer-join syntax.
• PO_LOOKUP_CODES — displayed field lookup.
• Runtime packages FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and CHV_INQ_SV support security and inquiry behavior.

Key Columns

• SCHEDULE_ID, SCHEDULE_ITEM_ID — primary identifiers linking back to schedule headers and lines.
• ORGANIZATION_ID, ORGANIZATION_CODE — inventory organization context.
• ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION — item identification.
• MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER, FULL_LEAD_TIME — item planning constraints used by supplier scheduling.
• ITEM_PLANNING_METHOD, ITEM_CONFIRM_STATUS, ITEM_PURGE_STATUS — scheduling state flags.
• ENABLE_AUTHORIZATIONS_FLAG, SCHEDULER_ID, FULL_NAME (buyer and planner) — approval and ownership.
• PO_HEADER_ID, SEGMENT1, END_DATE, PO_LINE_ID, LINE_NUM — purchasing document linkage.
• STARTING_CUM_QUANTITY, STARTING_AUTH_QUANTITY, STARTING_CUM_QTY_PRIMARY, STARTING_AUTH_QTY_PRIMARY — cumulative receipt and authorization baselines.
• PURCHASING_UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE — units of measure.
• Standard ATTRIBUTE1..15 and audit columns (CREATION_DATE, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID).

Common Use Cases and Queries

Typical scenarios include reviewing order quantity limits per supplier schedule, reconciling cumulative authorizations, and exporting schedule lines for supplier portals or EDI releases.

• Identify items with a maximum order quantity set: SELECT SCHEDULE_ID, ITEM_ID, CONCATENATED_SEGMENTS, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER FROM APPS.CHV_SCHEDULE_ITEMS_V WHERE MAXIMUM_ORDER_QUANTITY IS NOT NULL;
• List scheduled items for a specific organization with buyer names: SELECT ORGANIZATION_CODE, CONCATENATED_SEGMENTS, DESCRIPTION, FULL_NAME FROM APPS.CHV_SCHEDULE_ITEMS_V WHERE ORGANIZATION_ID = :org_id;
• Join to headers for schedule detail: SELECT v.* FROM APPS.CHV_SCHEDULE_ITEMS_V v, APPS.CHV_SCHEDULE_HEADERS h WHERE v.SCHEDULE_ID = h.SCHEDULE_ID AND h.SCHEDULE_ID = :schedule_id;

Because buyer and planner name columns are resolved through effective-dated PER_PEOPLE_F outer joins, results reflect the person effective as of the query execution date.