Search Results closed_code_dsp




Overview
Explore in AI Chat

Overview

POS_PO_SUPPLIER_AGREEMENTS_V is an APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2, defined within the POS (iSupplier Portal) product family. The view presents blanket purchase agreements — both global and local — in a supplier-facing format. Its documented purpose is to "display blankets," meaning it exposes purchasing document headers of blanket type that are relevant to the supplier self-service and iSupplier Portal flows. Because it is a view rather than a table, it stores no data itself; it consolidates information from purchasing, vendor, and lookup sources at query time, presenting a denormalized projection oriented toward external supplier visibility and reporting. The view is especially significant for the closed_code_dsp column it exposes: the documentation shows that CLOSED_CODE is transformed through NVL(POH.CLOSED_CODE, 'OPEN'), producing a display-friendly status value that renders a null closed code as the literal text 'OPEN'. This is the derivation behind the user-facing closed_code_dsp attribute commonly referenced in iSupplier Portal queries.

Underlying Base Objects

The documented base objects confirm the view is anchored principally on PO_HEADERS_ALL (accessed via a synonym), aliased POH in the view text. From this header table it draws agreement-level attributes such as dates, amounts, flags, terms, and descriptive fields. Supporting objects include PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS for supplier identification and contact detail; AP_TERMS for payment terms; GL_DAILY_CONVERSION_TYPES for rate types; HR_LOCATIONS_ALL_TL and HR_ALL_ORGANIZATION_UNITS_TL for location and organization translations; and PO_LOOKUP_CODES for lookup validation. Two packages are central: FND_CURRENCY.SAFE_GET_FORMAT_MASK formats monetary amounts according to the document currency mask, POS_GET.GET_PERSON_NAME resolves agent names, and POS_TOTALS_PO_SV is referenced for agreement totals. FND_GLOBAL provides session context such as user and responsibility, ensuring the view respects the caller's environment where applicable.

Key Columns

The view exposes a wide projection. Notable columns include:

Common Use Cases and Queries

The view is typically used to present open or closed blankets to suppliers, to build iSupplier Portal agreement listings, and to report on agreement status and value. A sample query filtering on the derived closed-code display value:

SELECT po_header_id, segment1, vendor_name, closed_code_dsp, blanket_total_amount
FROM apps.pos_po_supplier_agreements_v
WHERE closed_code_dsp = 'OPEN';

Because the closed-code column renders 'OPEN', 'CLOSED', or 'CANCELLED', consumers can filter agreement lifecycle state without interpreting raw codes. Other common patterns aggregate formatted amounts per supplier or join PO_HEADER_ID back to PO_HEADERS_ALL for extended attributes not projected by the view.