Results for “get_release_status”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_RELEASES_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It is flagged in the ETRM metadata with the description "10SC ONLY - Retrofitted", indicating that the object was originally introduced for a specific 10SC context and subsequently retrofitted into the standard EBS 12.1.1 / 12.2.2 schema. Its status is VALID in the APPS schema.

The view presents a denormalized, reporting-friendly projection of purchase order release (blanket agreement release) information. A release represents the document used to order against a pre-negotiated blanket purchase agreement; it is a distinct purchasing document from a standard purchase order. PO_RELEASES_V consolidates header-level, release-level, vendor, site, person, and location information into a single queryable structure, giving reporting tools and integrations access to release data without requiring application logic to join the underlying base tables manually.

Because the view resolves descriptive values such as release status and release total through packaged functions, it is primarily intended for read-only reporting, extracts, and integration rather than for transactional processing.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_RELEASES_ALL (synonym) — the principal base table supplying release-level columns such as PO_RELEASE_ID, RELEASE_NUM, RELEASE_DATE, approval, hold, and cancellation attributes.
• PO_HEADERS_ALL (synonym) — supplies blanket agreement header attributes including SEGMENT1, TYPE_LOOKUP_CODE, currency, dates, ship-to, and note fields.
• PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS (views) — provide vendor name, vendor site code, and vendor contact identity.
• PER_ALL_PEOPLE_F (synonym) — resolves the full name of the release agent and secondary contacts.
• HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL (synonyms) — resolve inventory organization and ship-to location codes.
• PO_DOCUMENT_TYPES_ALL_B and PO_DOCUMENT_TYPES_ALL_TL (synonyms) — supply the document type name.
• AP_TERMS (synonym) — supplies payment terms.
• PO_RELEASES_SV2 (package) — whose GET_RELEASE_STATUS and GET_REL_TOTAL functions derive computed status and total values.
• FND_GLOBAL and HR_GENERAL (packages) — used for session- and attribute-related context.

The view relies on external synonyms rather than fully qualified names, so queries must resolve against the standard EBS schema naming conventions.

Key Columns

• PO_RELEASE_ID, RELEASE_NUM, RELEASE_TYPE, RELEASE_DATE — identify and describe the release.
• PO_HEADER_ID, SEGMENT1, TYPE_LOOKUP_CODE — link to and identify the parent blanket agreement.
• VENDOR_NAME, VENDOR_ID, VENDOR_SITE_CODE, VENDOR_SITE_ID — vendor and site details.
• FULL_NAME, AGENT_ID — the buyer/agent responsible for the release.
• GET_RELEASE_STATUS(...) and GET_REL_TOTAL(...) — derived release status and release total values.
• AUTHORIZATION_STATUS, APPROVED_FLAG, APPROVED_DATE, CANCEL_FLAG, HOLD_FLAG, CLOSED_CODE, FROZEN_FLAG — workflow and status control attributes.
• CURRENCY_CODE, BLANKET_TOTAL_AMOUNT, START_DATE, END_DATE, TERMS_NAME — commercial terms of the agreement.
• SHIP_TO_LOCATION_ID, LOCATION_CODE, INVENTORY_ORGANIZATION_ID — delivery and organization context.
• ATTRIBUTE1…ATTRIBUTE15 and GLOBAL_ATTRIBUTE1…GLOBAL_ATTRIBUTE6 — descriptive flexfield segments.

Common Use Cases and Queries

Typical scenarios include listing all releases against a blanket agreement, reporting open or approved releases by buyer or vendor, and extracting release data for spend analysis or integration.

SELECT release_num,
       segment1 AS blanket_number,
       release_date,
       vendor_name,
       full_name AS buyer,
       authorization_status
FROM   apps.po_releases_v
WHERE  po_header_id = :p_po_header_id
ORDER  BY release_date DESC;

SELECT release_num,
       segment1,
       vendor_name,
       vendor_site_code,
       authorization_status
FROM   apps.po_releases_v
WHERE  authorization_status = 'APPROVED'
AND    cancel_flag = 'N';

Because status and totals are computed through PO_RELEASES_SV2, the view should not be treated as a purely static projection; performance and results depend on the packaged functions. It is suited to reporting and integration, not to direct transactional updates.