Results for “government_context”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.INL_ENTER_RECEIPTS_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the INL product family, Oracle Landed Cost Management, and is documented with a status of VALID. The view was cloned directly from RCV_ENTER_RECEIPTS_V, the Receiving module view that drives the Enter Receipts user interface, and is retained in the Landed Cost module to simplify UI coding against receipt data. Rather than re-deriving receipt attributes from the underlying purchasing, receiving, and inventory tables, the Landed Cost forms and related code can query a single flattened structure that already joins the relevant source tables.

The view is read-only with respect to the underlying base tables. It presents a denormalized projection of expected and in-transit receipt information — purchase orders, releases, requisitions, shipments, items, and vendor details — combined with the receiving controls that determine how a receipt must be processed. Consequently it functions both as a user-interface data source and as a reporting/integration surface for landed cost estimation, where receipt values and quantities drive cost allocation.

Underlying Base Objects

The ETRM 12.2.2 metadata records the following referenced base objects, resolved through APPS synonyms and views: GL_DAILY_CONVERSION_TYPES, HR_LOCATIONS_ALL_TL, MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, PO_HAZARD_CLASSES_TL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS, PO_LINE_TYPES_B, PO_RELEASES_ALL, PO_UN_NUMBERS_TL, PO_VENDORS (itself a view), and RCV_ROUTING_HEADERS (also a view).

These objects supply the view's principal data domains. PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS, PO_RELEASES_ALL, and PO_LINE_TYPES_B provide the purchasing document context — PO number, line, shipment, release, and order type. MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, MTL_ITEM_LOCATIONS, and related inventory objects contribute item-level attributes such as primary UOM, locator control, shelf-life, lot, and serial controls. PO_VENDORS and HR_LOCATIONS_ALL_TL supply vendor and ship-to location descriptions. GL_DAILY_CONVERSION_TYPES resolves the currency conversion type, while PO_HAZARD_CLASSES_TL and PO_UN_NUMBERS_TL deliver hazard class and UN number descriptions for regulated goods. RCV_ROUTING_HEADERS provides routing names for expected shipments. Because the view joins this many objects, queries against it should be tuned and filtered to avoid unnecessary full scans.

Key Columns

The view exposes a broad column list organized around the receipt lifecycle. Document identifiers include PO_HEADER_ID, PO_NUMBER, PO_LINE_ID, PO_LINE_NUMBER, PO_LINE_LOCATION_ID, PO_SHIPMENT_NUMBER, PO_RELEASE_ID, REQ_HEADER_ID, and RCV_SHIPMENT_HEADER_ID. Item and quantity data include ITEM_ID, ITEM_NUMBER, ITEM_DESCRIPTION, ORDERED_QTY, ORDERED_UOM, PRIMARY_UOM, and UNIT_PRICE. Receiving controls include INSPECTION_REQUIRED_FLAG, RECEIPT_REQUIRED_FLAG, ENFORCE_SHIP_TO_LOCATION_CODE, DESTINATION_TYPE_CODE, DESTINATION_SUBINVENTORY, and RECEIPT_SOURCE_CODE.

Of particular interest to users searching on "closed_code" is the CLOSED_CODE column. It indicates the closure status of the associated shipment or receipt line, distinguishing open, closed, and cancelled conditions so that forms and reports can exclude already-closed receipts from further processing. Related status and source fields include SOURCE_TYPE_CODE, ORDER_TYPE_CODE, and ORDER_TYPE. Scheduling and logistics attributes include NEED_BY_DATE, EXPECTED_RECEIPT_DATE, SHIPPED_DATE, FREIGHT_CARRIER_CODE, WAYBILL_AIRBILL_NUM, BILL_OF_LADING, and VENDOR_LOT_NUM. Currency and conversion details are carried in CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE, and CURRENCY_CONVERSION_RATE.

Common Use Cases and Queries

  • Identifying open receipt lines available for landed cost application, filtering out closed shipments.
  • Reconciling expected receipts against purchase order shipment schedules.
  • Populating Landed Cost receipt selection lists in custom forms or OAF pages.
  • Reporting on in-transit inventory by carrier, waybill, or expected date.

A typical query filters by closure status and ordering date:

  • SELECT po_number, po_line_number, item_number, ordered_qty, ordered_uom, closed_code, expected_receipt_date FROM apps.inl_enter_receipts_v WHERE closed_code = 'OPEN' AND expected_receipt_date >= SYSDATE ORDER BY expected_receipt_date;

Because the view is a clone of RCV_ENTER_RECEIPTS_V, existing Receiving queries can generally be redirected to it with minimal change. However, since it joins numerous base objects, restricting predicates on PO_NUMBER, ITEM_ID, CLOSED_CODE, or date columns is recommended to preserve performance in production environments.