Search Results bill_to_location_code




Overview
Explore in AI Chat

Overview

PO_NOTIFICATION_DETAILS_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, notification-oriented projection of purchase order header data, joining the core PO_HEADERS_ALL record to descriptive lookups for document type, vendor, agent, approval status, currency, and ship-to/bill-to locations. The view is designed to support PO approval workflow notifications and related reporting, providing the recipient-facing attributes (PO number, type name, agent name, vendor name, status, currency, comments) in a single row per purchase order. Because AGENT_NAME is surfaced directly in the projection, users searching for "agent_name" will find it here as an alias for HRE.FULL_NAME derived from HR_EMPLOYEES_CURRENT_V.

Underlying Base Objects

The view text accesses seven sources: PO_HEADERS_ALL, PO_DOCUMENT_TYPES_VL, HR_EMPLOYEES_CURRENT_V, PO_LOOKUP_CODES, PO_VENDORS, FND_CURRENCIES_TL, and HR_LOCATIONS_ALL_TL (joined twice for ship-to and bill-to). Per the ETRM metadata, the documented referenced objects additionally include the synonyms FND_CURRENCIES_TL, HR_LOCATIONS_ALL_TL, and PO_HEADERS_ALL, the views HR_EMPLOYEES_CURRENT_V, PO_DOCUMENT_TYPES_VL, PO_LOOKUP_CODES, and PO_VENDORS, together with the packages FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. The package references are inherited through the underlying HR views, which apply security and profile logic internally.

All joins to descriptive objects are outer joins (denoted by +), except the join to PO_DOCUMENT_TYPES_VL, which is mandatory. The view filters PDTL.DOCUMENT_TYPE_CODE to 'PO' and 'PA', restricting output to standard and blanket purchase agreement document types. AUTHORIZATION_STATUS is resolved through PO_LOOKUP_CODES using LOOKUP_TYPE 'AUTHORIZATION STATUS', with NVL substitution to 'INCOMPLETE' when no lookup value is found. Language-dependent joins to FND_CURRENCIES_TL and HR_LOCATIONS_ALL_TL are constrained to USERENV('LANG').

Key Columns

Common Use Cases and Queries

Typical scenarios include PO approval notification rendering, agent workload reporting, and supplier-facing extracts. The following query lists approved orders with their buyer:

  • SELECT po_num, po_type_name, agent_name, vendor_name, status, currency FROM po_notification_details_v WHERE approved_flag = 'Y' ORDER BY agent_name;
  • SELECT agent_id, agent_name, COUNT(*) FROM po_notification_details_v WHERE org_id = :p_org_id GROUP BY agent_id, agent_name;
  • SELECT po_num, vendor_name, status FROM po_notification_details_v WHERE status = 'INCOMPLETE';

Because the view is not secured directly by operating unit at the header level in the same way as some PO entities, filtering by ORG_ID is recommended. The HR-based outer joins mean AGENT_NAME may be null for orders without a valid current employee record, and location or currency descriptions may be null when the language-constrained joins do not match.