Results for “po_quotation_approvals_all”

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

Overview

PO_QUOTATION_APPROVALS_ALL is a Purchasing (PO) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores approval records associated with supplier quotations and quotation line locations. The table resides in the PO schema and is documented as "Quotation approvals" within the Purchasing product. Its role is to capture the approval actions taken against a quotation line location, including the approval type, the reason, the approver identity, the active date range for the approval, and descriptive comments. Because it references quotation line locations, it operates as a child object beneath the quotation line structure, recording who approved what and under which approval category.

The ETRM metadata provides a heuristic Data Vault classification of "satellite-leaning." This is a modeling suggestion rather than a functional label: the table behaves primarily as a descriptive satellite attached to a parent quotation line location, carrying attributes that change over time, such as approval type, reason, approver, comments, and date-active ranges. The classification reflects the heavy descriptive and temporal nature of the columns rather than any hub or link semantics, since the primary key is a generated surrogate identifier.

Key Information Stored

The table contains 34 documented columns. The central identifier is QUOTATION_APPROVAL_ID, which serves as the primary key via PO_QUOTATION_APPROVALS_PK and is also documented as a unique index (PO_QUOTATION_APPROVALS_U1). Because this column is a system-generated surrogate, it is the surrogate primary key rather than a business key. The principal foreign key is LINE_LOCATION_ID, which ties each approval record to its parent quotation line location in PO_LINE_LOCATIONS_ALL.

• QUOTATION_APPROVAL_ID — surrogate primary key uniquely identifying each approval record.
• LINE_LOCATION_ID — foreign key linking the approval to its quotation line location.
• APPROVAL_TYPE — classification of the approval action.
• APPROVAL_REASON — rationale recorded for the approval.
• APPROVER_ID — identifier of the individual who approved the quotation.
• COMMENTS — free-text notes accompanying the approval.
• START_DATE_ACTIVE — start of the approval's effective period.
• END_DATE_ACTIVE — end of the approval's effective period.
• ORG_ID — operating unit discriminator, confirming multi-org data partitioning.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns recording how the record was created or updated.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — flexible descriptive fields for extensibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical reporting scenarios include identifying all approvals tied to a quotation line location, reviewing approvals within an active date window, and attributing approvals to specific approvers. A common join pattern retrieves approval detail alongside its parent line location:

• Query by parent: SELECT a.QUOTATION_APPROVAL_ID, a.APPROVER_ID, a.APPROVAL_TYPE, a.APPROVAL_REASON FROM PO.PO_QUOTATION_APPROVALS_ALL a WHERE a.LINE_LOCATION_ID = :line_location_id
• Filter for currently active approvals using START_DATE_ACTIVE and END_DATE_ACTIVE relative to SYSDATE.
• Join to PO_LINE_LOCATIONS_ALL on LINE_LOCATION_ID to correlate approvals with their quotation line locations.
• Restrict by ORG_ID to enforce operating unit security in multi-org reporting.
• Trace concurrent program execution using REQUEST_ID and PROGRAM_ID for audit purposes.

Because "ALL" tables typically have a corresponding non-_ALL counterpart and may be exposed through secured synonyms or views, reporting should consistently filter by ORG_ID where multi-org access applies.

Related Objects

• PO_LINE_LOCATIONS_ALL — the parent quotation line location table, joined on PO_QUOTATION_APPROVALS_ALL.LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID. This is the documented foreign key relationship.
• PO_QUOTATION_APPROVALS_PK / PO_QUOTATION_APPROVALS_U1 — the primary key constraint and unique index enforcing QUOTATION_APPROVAL_ID uniqueness.
• PO_HEADERS_ALL / PO_QUOTATIONS (quotation header objects) — reachable through the line location chain to reach quotation headers.
• PO_APPROVAL_HISTORY or related approval objects — conceptually related approval-tracking structures used elsewhere in Purchasing.
• FND_USER / PER_ALL_PEOPLE_F — commonly joined on APPROVER_ID to resolve the approver's identity in reports.

These relationships position PO_QUOTATION_APPROVALS_ALL as a satellite-like record that supports quotation approval auditing and reporting within the Purchasing module.