Search Results ap_po_corrections_v




Overview
Explore in AI Chat

Overview

The APPS.AP_PO_CORRECTIONS_V view is a Payables (AP) reporting object that exposes purchase order line and line location data in the form and structure required for the Payables matching and correction process. Its primary purpose is to present procurement data — PO headers, lines, line locations, releases, and line types — alongside the descriptive flexfield and control-attribute columns that Payables uses when evaluating invoice-to-PO matching, price and quantity tolerance checks, and correction handling.

In Oracle EBS 12.1.1 and 12.2.2 this view functions as a read interface over the core Purchasing entities. It allows Payables forms, reports, and extensions to query PO line location attributes such as receipt tolerance, inspection requirements, and accrual flags without granting direct, uncontrolled access to PO_LINE_LOCATIONS_ALL. Because the view is defined with the owner schema APPS and is registered as VALID, it is a supported object for custom reports and integration queries that need a PO-line-location perspective from within the Payables module.

The user search term quantity_accepted reflects the common requirement to reconcile accepted quantities against invoiced quantities during matching and correction. While the excerpted view text is truncated before the quantity columns appear, the view's identity as a correction view over PO line locations strongly indicates that receiving and accepted-quantity data is surfaced through its joins to PO_LINE_LOCATIONS_ALL and the PO_LINE_LOCATIONS_AP_PKG package.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, AP_PO_CORRECTIONS_V references the following base objects:

The view therefore joins the PO document model to AP invoice data, enriching it with human-readable lookups and the PO_LINE_LOCATIONS_AP_PKG computations that Payables relies upon during the correction and matching workflows.

Key Columns

The excerpted view text reveals the column naming convention and coverage. Identifiers such as FROM_HEADER_ID, FROM_LINE_ID, and FROM_LINE_LOCATION_ID tie a row back to its PO header, line, and shipment, while ROW_ID exposes the underlying PO_LINE_LOCATIONS_ALL ROWID. Control and matching attributes include ACCRUE_ON_RECEIPT_FLAG, ALLOW_SUBSTITUTE_RECEIPTS_FLAG, INSPECTION_REQUIRED_FLAG, ENFORCE_SHIP_TO_LOCATION_CODE, DAYS_EARLY_RECEIPT_ALLOWED, DAYS_LATE_RECEIPT_ALLOWED, INVOICE_CLOSE_TOLERANCE, RECEIPT_REQUIRED_FLAG, and QTY_RCV_TOLERANCE.

Lifecycle and status columns include APPROVED_FLAG, APPROVED_DATE, CANCEL_FLAG, CANCEL_DATE, CANCEL_REASON, CLOSED_FLAG, CLOSED_CODE, CLOSED_DATE, FIRM_STATUS_LOOKUP_CODE, FIRM_DATE, ENCUMBERED_FLAG, ENCUMBERED_DATE, and ENCUMBER_NOW. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and the ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 descriptive flexfield columns are also exposed. Fields such as QUANTITY_ACCEPTED, QUANTITY_RECEIVED, and QUANTITY_INVOICED are derived through the PO_LINE_LOCATIONS_AP_PKG and receiving joins and are the columns typically targeted by quantity_accepted searches.

Common Use Cases and Queries

Typical uses include PO-to-invoice matching analysis, receipt and accepted-quantity reconciliation, tolerance threshold review, and open PO line correction reporting. Because accepted quantity is often supplied through a package function, queries should select from the view and optionally join PO_LINE_LOCATIONS_ALL or RCV_TRANSACTIONS for detail.

Example: retrieve PO line locations with their accepted and received quantities for a given PO number.

  • SELECT v.from_header_id, v.from_line_id, v.from_line_location_id, v.quantity_accepted, v.quantity_received, v.quantity_invoiced FROM apps.ap_po_corrections_v v WHERE v.from_header_id = :p_po_header_id;

Example: locate lines where the received quantity exceeds the invoiced quantity by more than the allowed tolerance.

  • SELECT v.from_line_location_id, v.quantity_received, v.quantity_invoiced, v.qty_rcv_tolerance FROM apps.ap_po_corrections_v v WHERE v.quantity_received IS NOT NULL AND v.quantity_invoiced IS NOT NULL AND (v.quantity_received - v.quantity_invoiced) > v.qty_rcv_tolerance;

Example: filter by document status for accrual and inspection control reporting.

  • SELECT header.segment1 po_number, v.from_line_id, v.inspection_required_flag, v.accrue_on_receipt_flag, v.closed_code FROM apps.ap_po_corrections_v v, apps.po_headers_all header WHERE v.from_header_id = header.po_header_id AND header.segment1 = :p_po_number;

These queries are supported by the view's documented base objects and are appropriate for custom Payables reports and reconciliation scripts.