Search Results acceptance_lookup_code

Overview

PO_ACCEPTANCES_V is an Oracle E-Business Suite Purchasing (PO) view owned by the APPS schema. It presents acceptance records for purchase orders and purchase order releases, exposing the accept/reject actions taken by employees against a document and its revision. The object is documented with the description "10SC ONLY," indicating that in the documented ETRM 12.1.1 and 12.2.2 configurations the view is scoped to specific operating unit or multi-organization contexts rather than being a general-purpose public interface. Functionally, it serves as a denormalized read layer over PO_ACCEPTANCES, joining acceptance data to lookup values, agent information, and HR person details so that reports and integrations can retrieve a single row containing both the acceptance action and the identity of the accepting party.

The view is relevant to the signature_flag search term because the SELECT list includes POA.SIGNATURE_FLAG, the column that indicates whether the acceptance record represents a signature or authorization event — a distinction important for procurement approvals, acceptance audit trails, and electronic signature reporting.

Underlying Base Objects

The documented base objects referenced by the view are PO_ACCEPTANCES (synonym over the base acceptance table), PO_AGENTS (synonym), PO_LOOKUP_CODES (view), and PER_PEOPLE_F (view). The documented view text also references the FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. The outer joins to PO_LOOKUP_CODES (lookup type ACCEPTANCE TYPE), PO_AGENTS, and PER_PEOPLE_F mean that acceptance rows are preserved even when no matching agent or effective HR person record exists. The join condition restricts PER_PEOPLE_F by the current effective date, so only currently effective person records are returned. Critically, the definition includes the predicate POA.PO_LINE_LOCATION_ID IS NULL, restricting output to header- or release-level acceptances rather than shipment-line-level acceptances.

Key Columns

• ACCEPTANCE_ID, PO_HEADER_ID, PO_RELEASE_ID — primary and foreign key identifiers linking the acceptance record to its purchasing document.
• ACTION, ACTION_DATE, ACCEPTED_FLAG, ACCEPTANCE_LOOKUP_CODE — the acceptance action, its date, and its result flag/code.
• ACCEPTANCE_TYPE — sourced from POC.DISPLAYED_FIELD via the ACCEPTANCE TYPE lookup, providing the readable acceptance definition.
• EMPLOYEE_ID, FULL_NAME, EMPLOYEE_NUMBER — the accepting employee's identifiers and name, including the documented EMPLOYEE_NUM column as exposed in ETRM 12.2.2 metadata.
• ACCEPTING_PARTY, ROLE — the party and role associated with the acceptance action.
• SIGNATURE_FLAG — indicates whether the acceptance record is signature-based, supporting audit and compliance reporting of authorized acceptances.
• ERECORD_ID — reference to the associated electronic record.
• REVISION_NUM, NOTE, and ATTRIBUTE1 through ATTRIBUTE15 — revision context, free-text notes, and descriptive flexfield segments.
• WHO/audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include acceptance audit reports, signature-tracking queries, and integration extracts where downstream systems require header-level acceptance detail with employee identity. A representative query retrieving signature-related acceptances follows:

SELECT acceptance_id, po_header_id, acceptance_type, action, action_date, full_name, accepting_party, role, signature_flag, erecord_id FROM apps.po_acceptances_v WHERE po_header_id = :p_po_header_id AND signature_flag = 'Y' ORDER BY action_date DESC;

A broader audit query lists all acceptances by accepting party:

SELECT po_header_id, employee_number, full_name, accepted_flag, acceptance_lookup_code, action_date FROM apps.po_acceptances_v WHERE accepting_party IS NOT NULL AND TRUNC(action_date) BETWEEN :p_from_date AND :p_to_date;

When querying this view, note the effective-dated PER_PEOPLE_F join and the PO_LINE_LOCATION_ID IS NULL restriction, as both materially narrow result sets. The "10SC ONLY" designation should be confirmed against your specific instance before using the view in a generally deployed report.