Results for “pos_bill_only_orders_v”

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

Overview

POS_BILL_ONLY_ORDERS_V is an APPS-owned database view in Oracle E-Business Suite, belonging to the iSupplier Portal (POS) product family. The ETRM metadata describes its purpose as selecting "consumption advices" — that is, it exposes purchase order headers that are eligible for consignment consumption advice processing. The view is VALID in both Oracle EBS 12.1.1 and 12.2.2 and is defined over PO purchasing tables, HR location tables, and HZ geography tables, layered with PL/SQL package calls for name resolution, currency formatting, and total computation.

The view specifically filters purchase orders where TYPE_LOOKUP_CODE is either BLANKET or STANDARD, the header is approved (APPROVED_FLAG = 'Y'), the authorization status is not IN PROCESS, INCOMPLETE, or REQUIRES REAPPROVAL, and critically, where CONSIGNED_CONSUMPTION_FLAG = 'Y'. This last predicate is what restricts the result set to consignment-relevant orders, aligning the view with consumption advice workflows. The requested user search term, bill_to_location, maps directly to a prominent column in this view, since bill-to location is used to identify the receiving/settlement point for consignment consumption.

Underlying Base Objects

The view joins several documented base objects. The central table is PO_HEADERS_ALL (PO_HEADERS_ALL is referenced via synonym), which supplies the PO header attributes such as APPROVED_DATE, CREATION_DATE, AGENT_ID, BILL_TO_LOCATION_ID, VENDOR_ID, VENDOR_SITE_ID, CURRENCY_CODE, TYPE_LOOKUP_CODE, SEGMENT1 (PO number), and the sixteen ATTRIBUTE columns.

Vendor information is sourced from PO_VENDORS (a view) and PO_VENDOR_SITES_ALL (a view), supplying VENDOR_NAME and VENDOR_SITE_CODE respectively. Status decoding uses PO_LOOKUP_CODES (view), and organization names come from HR_ALL_ORGANIZATION_UNITS_TL. Bill-to location resolution draws on HR_LOCATIONS_ALL_TL and HZ_LOCATIONS.

Package-based logic is embedded throughout: POS_GET.GET_PERSON_NAME_CACHE resolves the buyer name; POS_TOTALS_PO_SV.GET_PO_TOTAL computes the standard PO amount; and FND_CURRENCY_CACHE and FND_MESSAGE handle currency formatting and seed messages. The metadata also lists FND_GLOBAL and PO_RELEASES_ALL as referenced objects. Notably, PO_RELEASE_ID is returned as TO_NUMBER(NULL), so release-level detail is not surfaced by this view.

Key Columns

• BILL_TO_LOCATION_ID / BILL_TO_LOCATION — The bill-to location identifier and its display text, derived from HRL.LOCATION_CODE or a concatenation of address and city from HZ_LOCATIONS.
• PO_HEADER_ID, SEGMENT1 (PO_NUM) — Unique header identifier and the human-readable PO number.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE — Supplier identification and site linkage.
• AGENT_ID / AGENT_NAME — The buyer identity, resolved through the POS_GET package.
• APPROVED_DATE, CREATION_DATE, REVISION_NUM, COMMENTS — Standard header audit attributes.
• TYPE_LOOKUP_CODE / TYPE_NAME — Document type (BLANKET or STANDARD) with a translated display name.
• CURRENCY_CODE, AMOUNT — Currency and formatted total (blanket total or computed PO total).
• STATUS, CLOSED_CODE — Displayed status from PO_LOOKUP_CODES and the open/closed indicator.
• ORG_ID, ORG_NAME — Operating unit context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield values.

Common Use Cases and Queries

A typical use is selecting consignment orders and their bill-to locations for a given operating unit or supplier.

• Consumption advice candidate listing — Query approved blanket and standard consigned orders for processing.
• Bill-to location reporting — Group orders by BILL_TO_LOCATION to review distribution of consignment activity.
• Supplier-facing iSupplier views — Populate supplier screens showing eligible consumption orders.

Sample SQL:

SELECT po_num, vendor_name, type_name, status, bill_to_location, amount, currency_code, org_name FROM apps.pos_bill_only_orders_v WHERE org_id = :p_org_id AND vendor_id = :p_vendor_id ORDER BY approved_date DESC;

Because the view filters on CONSIGNED_CONSUMPTION_FLAG = 'Y' and authorization status, developers should not expect to see incomplete, rejected, or non-consigned orders. When the search term is bill_to_location, the relevant predicate is the outer join to location tables, so queries filtering on this column should account for possible nulls when neither the code nor address components are populated.