Search Results closed_for_invoice_date




Overview
Explore in AI Chat

Overview

POBV_PLAN_PO_LINE_SHIPMENTS is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module, delivered for both 12.1.1 and 12.2.2. The "POBV" prefix identifies it as a Purchasing business view generated and maintained through the Oracle ETRM (E-Business Suite Tables and Views Reference Manual) framework, and its documented description carries the notation "- Retrofitted", indicating that the entity was reconstructed or re-pointed during the 12.2 architectural changes, notably the migration of the organization model to the Multi-Org Access Control (MOAC) security layer and the relocation of certain HR-related definitions.

The view presents planned purchase order line shipment information — a denormalized projection that joins shipment (line location) records with their parent line, header, and ship-to organization. It is consumed primarily by Oracle Purchasing forms, Oracle Daily Business Intelligence for Procurement, and by customer-developed reports and interfaces that need shipment-level detail without navigating the full base-table hierarchy. The user search term "closed_for_invoice_date" relates to this view's role in exposing the open/closed state of a shipment, which downstream drives invoicing eligibility. In the EBS data model, the shipment-level columns CLOSED_CODE, CLOSED_DATE, and CLOSED_REASON (all present in this view) determine whether a line location can still be matched to an invoice; the invoice-close tolerance column INVOICE_CLOSE_TOLERANCE likewise governs automatic closure for invoicing.

Underlying Base Objects

ETRM documents four referenced base objects, all exposed through APPS synonyms: HR_ALL_ORGANIZATION_UNITS, PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL. The view text confirms the join pattern: PO_LINE_LOCATIONS_ALL (aliased PS) supplies the shipment grain and most attributes; PO_LINES_ALL (PL) supplies the line number; PO_HEADERS_ALL (PH) supplies the header segment used as the PO number; and HR_ALL_ORGANIZATION_UNITS (OP) supplies the operating unit name, joined on ORG_ID. Because PO_HEADERS_ALL and PO_LINE_LOCATIONS_ALL are _ALL tables, MOAC predicates apply and each row is implicitly restricted to the operating units the session is authorized to access. The view exposes ORG_ID directly, allowing reporting tools and custom SQL to filter or group by operating unit.

Key Columns

Note the embedded `_LA:` descriptor strings in the view text. These are Oracle Lookup/Attribute markers used by the EBS "Your Page"/personalization and descriptive flexfield rendering layers; they are literal, non-functional text in the view definition and carry no queryable meaning.

Common Use Cases and Queries

The view is most often used to report on shipment status, outstanding quantities, and closure state without joining PO_LINE_LOCATIONS_ALL to its parents. A typical open-shipment query filters on approval and closure:

  • SELECT segment1, line_num, shipment_num, need_by_date, quantity, quantity_received, closed_code, closed_date FROM pobv_plan_po_line_shipments WHERE org_id = :p_org_id AND closed_code = 'OPEN';
  • SELECT segment1, shipment_num, quantity - quantity_billed open_qty FROM pobv_plan_po_line_shipments WHERE invoice_close_tolerance IS NOT NULL AND NVL(closed_code,'OPEN') <> 'CLOSED FOR INVOICE';
  • SELECT org_id, name, COUNT(*) FROM pobv_plan_po_line_shipments GROUP BY org_id, name;

Because the view is a non-materialized join, no refresh is required, but performance depends on the indexes on PO_LINE_LOCATIONS_ALL and PO_LINES_ALL; large extracts should always be constrained by ORG_ID and date ranges. The view is read-only and is not a supported update target for purchasing transactions.