Results for “authorization_status”

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

Overview

APPS.ICX_EDM_PO_BLANKET_REL_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product family. As its ETRM description states, it is the Project Related PO Releases View. It presents a denormalized, reporting-oriented projection of blanket purchase agreement releases in which a project and task context exists on the release distribution.

The view's purpose is to support project-aware inquiry and reporting of release documents without requiring callers to reconstruct the multi-table join between purchasing headers, releases, distributions, document types, lookups, vendor master data, terms, and HR locations. It exposes both identifiers and human-readable display values, including the concatenated PO number (SEGMENT1||'-'||RELEASE_NUM), the release total formatted via PO_TOTALS_PO_SV.GET_RELEASE_TOTAL combined with FND_CURRENCY.SAFE_GET_FORMAT_MASK, and the buyer name resolved through PO_INQ_SV.GET_PERSON_NAME. This design makes the view suitable for EDM/self-service procurement integrations and for project-driven purchasing inquiries in Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The documented base objects show a join across purchasing, project, HR, and lookup structures. The central join is between PO_HEADERS_ALL (header header/detail) and PO_RELEASES_ALL on PO_HEADER_ID, with PO_DISTRIBUTIONS_ALL supplying project and task context. Reference joins include PO_DOCUMENT_TYPES_ALL restricted to DOCUMENT_TYPE_CODE = 'RELEASE' matched to RELEASE_TYPE; PO_LOOKUP_CODES used four times for authorization status, FOB, freight terms, and closure status; PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS for supplier data; AP_TERMS for payment terms; and HR_LOCATIONS twice for ship-to and bill-to locations. Packages referenced are MRP_GET_PROJECT, PO_TOTALS_PO_SV, FND_CURRENCY, PO_INQ_SV, FND_GLOBAL, and HR_GENERAL. The vendor contact join uses an outer join (VC.VENDOR_CONTACT_ID(+)), and DISTINCT suppresses duplication across the distribution-to-release fan-out.

Key Columns

• PO_HEADER_ID, PO_RELEASE_ID, BUYER_ID, VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID, TERMS_ID, SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID — surrogate keys for drill-down and integration joins.
• PROJECT_ID, TASK_ID — project and task identifiers from the release distribution, with corresponding name columns resolved through MRP_GET_PROJECT.PROJECT and MRP_GET_PROJECT.TASK.
• PO_NUM and PO_RELEASE_NUMBER — the reported purchase order number and the release number.
• DOC_TYPE_NAME, AUTHORIZATION_STATUS_DSP, FOB_DSP, FREIGHT_TERMS_DSP, CLOSURE_STATUS — display fields sourced from document types and lookup codes.
• ORDER_DATE (release date), PRINTED_DATE, REVISION_NUM, REVISED_DATE — release lifecycle attributes.
• AMOUNT, CURRENCY_CODE — the release total rendered using the currency format mask.
• BUYER_NAME, VENDOR_NAME, SUPPLIER_CONTACT_NAME, SUPPLIER_URL (PO_VENDORS.ATTRIBUTE14), VENDOR_SITE_CODE — supplier and agent identity data.
• TERMS_NAME, SHIP_TO_LOCATION, BILL_TO_LOCATION, SHIP_VIA_LOOKUP_CODE — commercial and logistics attributes.

Common Use Cases and Queries

Typical scenarios include project-cost reporting on blanket releases, supplier performance analysis by buyer or vendor site, and iProcurement/EDM integration extracts requiring documented release attributes. Because project and task columns are exposed directly, the view is convenient for Oracle Projects cross-reference reporting and for auditing authorization statuses.

• List releases for a given project: SELECT PO_NUM, PO_RELEASE_NUMBER, AMOUNT, CURRENCY_CODE FROM APPS.ICX_EDM_PO_BLANKET_REL_V WHERE PROJECT_ID = :p_project_id ORDER BY ORDER_DATE DESC;
• Aggregate release spend by supplier: SELECT VENDOR_NAME, SUM(AMOUNT) FROM APPS.ICX_EDM_PO_BLANKET_REL_V GROUP BY VENDOR_NAME;
• Filter by buyer and authorization status: SELECT PO_NUM, RELEASE_NUM, BUYER_NAME, AUTHORIZATION_STATUS_DSP FROM APPS.ICX_EDM_PO_BLANKET_REL_V WHERE BUYER_ID = :buyer_id AND CLOSURE_STATUS = 'OPEN';
• Drill to document details using PO_HEADER_ID, PO_RELEASE_ID, and PROJECT_ID. Note that AMOUNT and display columns are formatted strings returned by PL/SQL service functions, so numeric comparisons should be avoided unless converted explicitly.