Search Results po_type_name

Overview

APPS.PO_NOTIFICATION_DETAILS_V is a denormalized reporting view in the Oracle E-Business Suite Procurement module, owned by the APPS schema and registered in FND Design Data as PO.PO_NOTIFICATION_DETAILS_V. Its purpose is to present a single, pre-joined row per purchase order header, combining approval state, buyer, supplier, currency, and location attributes so that notification and reporting programs can retrieve purchase order details without assembling the same joins repeatedly. The view is classified as internal, with the standard Oracle warning that it is intended for access by standard Oracle Applications programs rather than as a supported public interface, and its status is VALID in both 12.1.1 and 12.2.2.

For the search term po_type_name, the view is directly relevant: it exposes both TYPE_LOOKUP_CODE, the raw lookup code for the purchase order type, and PO_TYPE_NAME, an 80-character translated description of that type. This allows reporting and notification logic to display a human-readable document type without performing a separate lookup translation step.

Underlying Base Objects

The view is defined over a mixture of transactional tables, HR security and naming objects, and FND currency and profile utilities. Documented dependencies include PO_HEADERS_ALL (the purchase order header entity underlying PO_HEADER_ID, ORG_ID, PO_NUM, and approval attributes), PO_DOCUMENT_TYPES_VL and PO_LOOKUP_CODES (which supply document type and lookup translation, including PO_TYPE_NAME), and PO_VENDORS (the supplier source for VENDOR_ID and VENDOR_NAME).

Buyer information is derived through HR_EMPLOYEES_CURRENT_V, HR_PERSON_NAME, and HR_SECURITY, with HR_GENERAL supporting organizational and location context. Location values come from HR_LOCATIONS_ALL_TL. Currency columns rely on FND_CURRENCIES_TL and FND_PROFILE, while FND_GLOBAL supplies session context such as responsibility, user, and organization. The presence of HR_SECURITY indicates that buyer and organization visibility may be filtered by HR security rules, so results can vary by responsibility and user.

Key Columns

• PO_HEADER_ID, ORG_ID, PO_NUM — the purchase order identifier, operating unit organization, and document number forming the primary reporting key.
• TYPE_LOOKUP_CODE, PO_TYPE_NAME — the code and translated name of the PO type, the columns most directly answering a search for po_type_name.
• APPROVED_DATE, APPROVED_FLAG, STATUS — approval timestamp, an approval indicator, and a readable approval status used in notification logic.
• VENDOR_ID, VENDOR_NAME, AGENT_ID, AGENT_NAME — supplier and buyer identifiers and names.
• SHIP_TO_LOCATION_ID / SHIP_TO_LOCATION_CODE, BILL_TO_LOCATION_ID / BILL_TO_LOCATION_CODE — delivery and invoicing location identifiers and codes.
• CURRENCY_CODE, CURRENCY, COMMENTS — currency code and description, plus a 240-character comment field.

Common Use Cases and Queries

Typical uses include approval notification content, buyer and supplier reporting, and reconciliation of purchase orders by document type. Because PO_TYPE_NAME is pre-translated, the view is convenient for listings that must show the document type exactly as Oracle presents it.

List approved standard purchase orders with their translated type and supplier:

• SELECT po_num, po_type_name, vendor_name, agent_name, status, currency_code FROM apps.po_notification_details_v WHERE approved_flag = 'Y' ORDER BY approved_date DESC;

Report counts by document type for a specific organization:

• SELECT po_type_name, COUNT(*) FROM apps.po_notification_details_v WHERE org_id = :p_org_id GROUP BY po_type_name;

Locate purchase orders for a given buyer and show ship-to information:

• SELECT po_num, po_type_name, vendor_name, ship_to_location_code, status FROM apps.po_notification_details_v WHERE agent_id = :p_agent_id;

Consumers should treat the view as internal Oracle infrastructure and expect possible changes between releases.