Results for “approval_date”

50+ results




Overview
Explore in AI Chat

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

Overview

The view APPS.POBV_PLAN_PO_RELEASES is a Purchasing (PO) module reporting object in Oracle E-Business Suite, documented as "Retrofitted" in ETRM metadata. It exposes scheduled purchase order release information by joining release, header, and organization data into a single queryable structure. The view presents one row per scheduled release, combining release-level attributes such as release date, revision, and cancellation status with header-level attributes such as supplier ID, currency, and document state.

The view is intended primarily for inquiry, reporting, and integration purposes rather than transactional processing. Because it is a read-only view (the underlying definition includes a WITH READ ONLY clause and an organization security predicate), it is well suited to reporting tools, custom concurrent programs, and EBS integrated SOA or interface extracts where scheduled PO release detail is required without directly accessing the base tables.

The naming prefix "POBV" reflects a Purchasing Business View, and the columns carrying "_LA:" prefixes encode lookup display attributes. The view supports the user-entered search term "cancelled_by" through its CANCELLED_BY column, which records the user who cancelled a scheduled release.

Underlying Base Objects

According to the documented view text, POBV_PLAN_PO_RELEASES is defined over three base objects, referenced through synonyms in the APPS schema:

The security predicate _SEC:PR.ORG_ID enforces operating unit (multi-org) access, ensuring users see only releases for organizations they are authorized to access. The view remains valid for both the 12.1.1 and 12.2.2 reference environments covered by this documentation.

Key Columns

The view exposes a broad column set spanning release, header, and organization data:

  • PO_RELEASE_ID / RELEASE_NUM — unique release identifier and the human-readable release number.
  • PO_HEADER_ID / SEGMENT1 — the parent PO header identifier and its document number.
  • ORG_ID / NAME — operating unit identifier and name.
  • RELEASE_DATE, REVISION_NUM, REVISED_DATE, APPROVED_DATE — release dating and revision attributes.
  • CANCEL_FLAG, CANCELLED_BY — indicates whether the release was cancelled and identifies the user who cancelled it, directly matching the "cancelled_by" search term.
  • FROZEN_FLAG, HOLD_FLAG — status flags controlling release actions.
  • AUTHORIZATION_STATUS, CLOSED_CODE, FIRM_STATUS_LOOKUP_CODE — displayed-field lookups describing approval, document state, and firm status.
  • VENDOR_ID, VENDOR_SITE_ID, CURRENCY_CODE — supplier and currency reference data from the header.
  • NOTE_TO_VENDOR, USSGL_TRANSACTION_CODE, PAY_ON_CODE, ACCEPTANCE_DUE_DATE — supplementary release and accounting attributes.

Common Use Cases and Queries

Typical scenarios include auditing cancelled releases, reporting outstanding scheduled releases per buyer, and feeding external systems. The following query isolates releases cancelled by a specific user:

  • SELECT release_num, segment1, name, cancelled_by, cancel_flag FROM apps.pobv_plan_po_releases WHERE cancel_flag = 'Y' AND cancelled_by = :user_id;
  • SELECT segment1, release_num, release_date, authorization_status, currency_code FROM apps.pobv_plan_po_releases WHERE org_id = :org_id AND release_date >= :from_date;
  • SELECT vendor_id, COUNT(*) FROM apps.pobv_plan_po_releases WHERE frozen_flag = 'N' AND hold_flag = 'N' GROUP BY vendor_id;

Because the view is read-only and secured by ORG_ID, it should never be used for DML; instead, use it to satisfy reporting, verification, and data-extraction requirements against scheduled purchase order releases.