Results for “pay_on_code”

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

Overview

POS_SHIPMENTS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, classified under the POS – iSupplier Portal product family. Its documented purpose is simply to "display shipments," and in practice it serves as the shipment-level projection used by iSupplier Portal pages and related supplier-facing functionality. Rather than exposing the raw Purchasing tables directly, the view denormalizes header, line, shipment, vendor, item, and organization attributes into a single flattened row set that is convenient for both inquiry screens and ad-hoc reporting.

The view is marked VALID in the ETRM 12.2.2 metadata and is available in both 12.1.1 and 12.2.2. Because it is a view rather than a table, it stores no data of its own; every query against it resolves through the underlying Purchasing and HR/MTL base objects at runtime.

Underlying Base Objects

The documented view text joins the core Purchasing tables PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_RELEASES_ALL, together with vendor objects PO_VENDORS and PO_VENDOR_SITES_ALL, item and unit-of-measure objects MTL_SYSTEM_ITEMS_KFV and MTL_UNITS_OF_MEASURE, and organizational objects HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, and HZ_LOCATIONS. A supporting lookup view, PO_LOOKUP_CODES, contributes the TAB_DISPLAY column.

The ETRM "referenced base objects" list additionally records dependencies on FND_GLOBAL, POS_ASN_CREATE_PVT, and PO_DOC_STYLE_HEADERS. These are typically consumed through the view's WHERE clause and style/lookup logic rather than appearing as projected columns. From a query-planning perspective, the shipment row is anchored on PO_LINE_LOCATIONS_ALL (aliased PLL), with PO_DISTRIBUTIONS-style shipment detail resolved through the parallel Purchasing views.

Key Columns

The column list is broad and shipment-centric. Identifier columns include PO_NUMBER, RELEASE_NUM, DISPLAY_PO_NUMBER, PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_RELEASE_ID, SHIPMENT_NUM, and ORG_ID. Vendor and site data are exposed through VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID, VENDOR_NAME, VENDOR_SITE_CODE, PAY_SITE_FLAG, and PAY_ON_CODE.

Item and pricing attributes include ITEM_ID, ITEM_NUM (concatenated segments), ITEM_REVISION, ITEM_DESCRIPTION, SUPPLIER_ITEM_NUMBER, UNIT_PRICE, and currency fields CURRENCY_CODE, RATE_TYPE, RATE, and RATE_DATE. Quantities are represented by QUANTITY_ORDERED, QUANTITY_RECEIVED, and the placeholder SHIPMENT_QUANTITY and TOLERABLE_QUANTITY, which are defined as TO_NUMBER(NULL). Scheduling and receipt control columns include DUE_DATE (NVL of PROMISED_DATE/NEED_BY_DATE), RECEIPT_DAYS_EXCEPTION_CODE, DAYS_EARLY_RECEIPT_ALLOWED, DAYS_LATE_RECEIPT_ALLOWED, QTY_RCV_EXCEPTION_CODE, MATCH_OPTION, and CONSIGNED_FLAG.

The user's search term, ESTIMATED_TAX_AMOUNT, maps directly to the PLL.ESTIMATED_TAX_AMOUNT column carried through from PO_LINE_LOCATIONS_ALL. It is accompanied by the TAXABLE_FLAG column and a TAX_NAME column that is projected as an empty string (''). This juxtaposition is significant: tax is surfaced at shipment level as an estimated amount only, with no tax code or tax name resolution performed inside POS_SHIPMENTS_V.

Common Use Cases and Queries

Typical consumers use this view for supplier portal shipment listings, open-shipment reporting, and reconciliation of ordered versus received quantities. A representative query isolates shipment tax and schedule information for a purchase order:

• SELECT po_number, display_po_number, shipment_num, item_num, quantity_ordered, quantity_received, estimated_tax_amount, taxable_flag, due_date FROM apps.pos_shipments_v WHERE po_number = :po_number ORDER BY line_num, shipment_num;
• SELECT vendor_name, po_number, SUM(estimated_tax_amount) est_tax, SUM(quantity_ordered) ordered FROM apps.pos_shipments_v WHERE org_id = :org_id GROUP BY vendor_name, po_number;
• SELECT po_number, shipment_num, qty_rcv_exception_code, receipt_days_exception_code FROM apps.pos_shipments_v WHERE NVL(quantity_received,0) < quantity_ordered;

Because TAX_NAME is a literal empty string and SHIPMENT_QUANTITY/TOLERABLE_QUANTITY return NULL, report authors should not rely on this view for tax determination logic or consignment quantity display. For full tax detail, join the shipment row back to PO_DISTRIBUTIONS_ALL or the E-Business Tax tables on LINE_LOCATION_ID. Performance is generally acceptable for single-PO lookups; broad extracts should be filtered by ORG_ID and date range to avoid full scans across PO_LINE_LOCATIONS_ALL.