Search Results blanket_total_amount




Overview
Explore in AI Chat

Overview

POS_SUPP_AGREEMENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered with the iSupplier Portal (POS) product family. It exposes a denormalized, presentation-ready projection of blanket purchase agreements, joining purchasing header data to supplier and supplier site information, operating unit names, and document state lookup descriptions. The view is a supporting object for iSupplier Portal supplier-facing pages, where a supplier views the agreements negotiated with the buying organization.

Because the view filters on PO_HEADERS_ARCHIVE_ALL with LATEST_EXTERNAL_FLAG = 'Y' and TYPE_LOOKUP_CODE = 'BLANKET', it returns only the current externally published version of blanket agreements. This makes it suitable for external-facing reports and portal integrations rather than for internal audit of all historical revisions. The view is not maintained as a base table; it carries no DML capability and should be treated strictly as a read-only reporting source.

Underlying Base Objects

The documented base objects referenced by the view are:

  • PO_HEADERS_ARCHIVE_ALL (synonym) — the archived purchasing document header, supplying agreement attributes and the BLANKET type filter and LATEST_EXTERNAL_FLAG restriction.
  • PO_VENDORS (view) — supplier master, supplying VENDOR_NAME and VENDOR_NUMBER (mapped from SEGMENT1).
  • PO_VENDOR_SITES_ALL (view) — supplier site master, supplying VENDOR_SITE_CODE.
  • PO_LOOKUP_CODES (view) — resolves the document state lookup into a display value via DISPLAYED_FIELD, restricted to lookup type 'DOCUMENT STATE'.
  • HR_ALL_ORGANIZATION_UNITS_TL (synonym) — the operating unit name, joined with an outer join on ORGANIZATION_ID and LANGUAGE = USERENV('LANG').
  • FND_GLOBAL (package) — referenced indirectly through the language environment used in the operating unit join.

Joins are keyed on VENDOR_ID, VENDOR_SITE_ID, the derived document state code, and ORG_ID. The HR organization join is outer, so agreements lacking a matching organization translation still return rows.

Key Columns

Columns of operational importance include:

Several positional columns are defined as TO_CHAR(NULL) placeholders, meaning they exist in the projection but return no data. Consumers porting reports from earlier releases should verify column positions rather than relying on names alone.

Common Use Cases and Queries

Typical uses include supplier portal agreement listings, spend-versus-limit analysis on blankets, and reconciliation of agreement totals to releases. A representative query retrieving agreement number, supplier, total amount, and state is:

  • SELECT segment1, vendor_name, blanket_total_amount, amount_limit, authorization_status, displayed_field FROM apps.pos_supp_agreements_v WHERE org_id = :p_org_id ORDER BY segment1;

To identify blankets approaching their ceiling:

  • SELECT segment1, vendor_name, blanket_total_amount, amount_limit FROM apps.pos_supp_agreements_v WHERE amount_limit IS NOT NULL AND blanket_total_amount > amount_limit * 0.9;

Because the view reads from the archive header and applies the latest external flag, results reflect currently published agreement versions only. Queries requiring in-process or historical revisions, or requiring the amount released to date, must join to the purchasing base tables or to PO_RELEASES_ALL rather than relying on this view alone.