Search Results item_rev_control_flag_to

Overview

POR_RECEIVE_ORDERS_V is an APPS-owned database view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that exposes the population of purchase order and requisition lines available for receiving. It belongs to the ICX product family — Oracle iProcurement — and is the data source that drives the iProcurement "Receive Items" flow, presenting a unified, query-ready list of expected receipts so that a receiving agent can search, select, and confirm inbound goods. Because it consolidates header, line, shipment, vendor, item, and receiving-control attributes into a single row per receivable shipment, the view also serves as a convenient reporting and integration surface for custom receipt worklists, dashboards, and third-party receiving interfaces that must not re-implement EBS receiving eligibility logic. Consistent with ETRM documentation, the object is recorded with status VALID under the APPS schema, and its description is simply "Items available for receiving."

Underlying Base Objects

The view is layered over core Oracle Purchasing and Inventory tables, joined through the APPS synonyms. Documented referenced base objects include PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_LINE_TYPES, PO_RELEASES, PO_DISTRIBUTIONS, PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS, PO_VENDORS, PO_VENDOR_SITES, PO_LOOKUP_CODES, PO_HAZARD_CLASSES, and PO_UN_NUMBERS. Item and unit-of-measure attributes are sourced from MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, and MTL_CATEGORIES_KFV. Receiving routing information is derived from RCV_ROUTING_HEADERS. Personnel and organization context depends on HR_EMPLOYEES_CURRENT_V, HR_LOCATIONS, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. Utility and session functions are supplied by FND_GLOBAL, FND_PROFILE, ICX_UTIL. The header-to-line-to-shipment hierarchy is preserved through PO_HEADER_ID, PO_LINE_ID, and PO_LINE_LOCATION_ID, with release information carried via PO_RELEASE_ID from PO_RELEASES.

Key Columns

The projection is deliberately aligned to the iProcurement receiving data model. Identification columns include PO_HEADER_ID, PO_NUMBER, PO_LINE_ID, PO_LINE_NUMBER, PO_LINE_LOCATION_ID, PO_SHIPMENT_NUMBER, PO_RELEASE_ID, and PO_RELEASE_NUMBER. Source and order classification are exposed through SOURCE_TYPE_CODE and RECEIPT_SOURCE_CODE (both hard-coded to 'VENDOR'), ORDER_TYPE_CODE ('PO'), and the decoded ORDER_TYPE from PO_LOOKUP_CODES via PLC.DISPLAYED_FIELD. Quantities central to receiving are QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_CANCELLED, and a computed open/outstanding quantity using NVL arithmetic — the basis for restricting the worklist to lines still requiring receipt. Destination context is provided by SHIP_TO_ORGANIZATION_ID, DELIVER_TO_PERSON_ID/REQUESTOR_ID, VENDOR_ID, SOURCE, VENDOR_SITE_ID, and SUPPLIER_SITE. Item control attributes — ITEM_ID, PRIMARY_UOM, ITEM_LOCATOR_CONTROL, RESTRICT_LOCATORS_CODE, RESTRICT_SUBINVENTORIES_CODE, SHELF_LIFE_CODE, SERIAL_NUMBER_CONTROL_CODE, and LOT_CONTROL_CODE — derive from MTL_SYSTEM_ITEMS and govern how receipt entry validates each line. The requested term, ITEM_REV_CONTROL_FLAG_TO, represents the revision control attribute used to determine whether a revision must be specified on receipt; it is populated from the MTL_SYSTEM_ITEMS revision quantity control logic and is typically surfaced alongside the item's revision control code so that the receiving UI can enforce or suppress revision entry accordingly.

Common Use Cases and Queries

Typical uses include building custom "items to receive" inquiries, populating iProcurement-style receipt pages in custom OAF or Forms extensions, and feeding downstream receiving integrations. The following example returns open, supplier-sourced shipments for a destination organization:

• SELECT po_number, po_line_number, po_shipment_number, supplier_site, item_id, primary_uom, quantity_ordered, quantity_delivered, order_type FROM apps.por_receive_orders_v WHERE to_organization_id = :org_id AND source_type_code = 'VENDOR' AND quantity_ordered > NVL(quantity_delivered,0) + NVL(quantity_cancelled,0);
• Filter by PO or release: WHERE po_number = :po_num OR po_release_number = :release_num.
• Inventory-controlled receipt planning: add predicates on item_locator_control, shelf_life_code, lot_control_code, or serial_number_control_code to drive validation grids.

Because the view embeds HR security and profile-dependent logic (HR_SECURITY, FND_PROFILE, FND_GLOBAL), queries should be executed in a session with a valid application context, and permissions should be granted to a custom APPS synonym or GRANT SELECT as appropriate for reporting users.