Results for “acceptance_id”

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

Overview

PO_ACCEPTANCES is a Purchasing (PO) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores purchase order and release acceptance records. It captures the formal acknowledgement by a supplier, internal accepting party, or authorized employee that goods, services, or contractual terms associated with a purchase document have been accepted. In public sector and regulated procurement environments, this table frequently backs acceptance functionality tied to e-signature or approval workflows, as indicated by the SIGNATURE_FLAG, ACCEPTING_PARTY, and ERECORD_ID columns present in the documented schema.

The table is owned by the PO schema and contains 45 documented columns in the 12.2.2 physical schema, with 12.1.1 implementations following the same core structure. The primary key is PO_ACCEPTANCES_PK, defined on ACCEPTANCE_ID, and a unique index PO_ACCEPTANCES_U1 also exists on ACCEPTANCE_ID. Based on the foreign key topology — multiple parent references to PO_HEADERS_ALL, PO_RELEASES_ALL, and PO_LINE_LOCATIONS_ALL — the heuristic Data Vault classification is a link table, suggesting it models relationships and events between purchasing entities rather than a pure hub or satellite. This classification is a modeling suggestion derived from FK structure and should be validated against the specific business requirement.

Key Information Stored

The most significant columns in PO_ACCEPTANCES fall into identity, document linkage, and acceptance detail categories.

• ACCEPTANCE_ID — surrogate primary key (PO_ACCEPTANCES_PK); uniquely identifies each acceptance record and is also the business-key candidate via PO_ACCEPTANCES_U1.
• PO_HEADER_ID — foreign key to PO_HEADERS_ALL; identifies the purchase order header to which the acceptance pertains.
• PO_RELEASE_ID — foreign key to PO_RELEASES_ALL; identifies the associated release when the acceptance relates to a blanket agreement release.
• PO_LINE_LOCATION_ID — foreign key to PO_LINE_LOCATIONS_ALL; links the acceptance to the specific shipment or line location.
• ACTION and ACTION_DATE — capture the nature of the acceptance action and its timestamp.
• ACCEPTED_FLAG — indicates whether the acceptance was granted or denied.
• ACCEPTANCE_LOOKUP_CODE — lookup value categorizing the acceptance.
• EMPLOYEE_ID — foreign key to PSB_EMPLOYEES; the internal employee performing or recording the acceptance.
• ACCEPTING_PARTY and ROLE — describe who accepted the terms and in what capacity.
• SIGNATURE_FLAG — flags whether an electronic signature was applied.
• DRAFT_ID — foreign key to PO_DRAFTS; supports draft-based acceptance processing.
• VENDOR_CONTACT_ID, VENDOR_CONTACT_NAME, VENDOR_CONTACT_TITLE, and VENDOR_SIGNED_DATE — capture supplier-side signatory details and the date the vendor signed.
• NOTE — free-text remarks attached to the acceptance.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and 15 ATTRIBUTE flex columns provide audit and extensibility support.

Common Use Cases and Queries

Typical reporting scenarios include tracing which purchase orders and releases have been formally accepted, monitoring pending acceptance actions, and auditing electronic signatures for compliance. A common query joins PO_ACCEPTANCES to PO_HEADERS_ALL to list acceptances by PO:

• SELECT pa.ACCEPTANCE_ID, pa.ACTION, pa.ACTION_DATE, ph.SEGMENT1 FROM PO_ACCEPTANCES pa JOIN PO_HEADERS_ALL ph ON pa.PO_HEADER_ID = ph.PO_HEADER_ID WHERE pa.ACCEPTED_FLAG = 'Y';
• Drill-down queries joining PO_ACCEPTANCES to PO_LINE_LOCATIONS_ALL reveal acceptance status at shipment level.
• Vendor signatory audits query VENDOR_CONTACT_NAME, VENDOR_SIGNED_DATE, and SIGNATURE_FLAG.
• Draft-based acceptance reporting joins DRAFT_ID to PO_DRAFTS.

Related Objects

The following documented objects reference or are referenced by PO_ACCEPTANCES through foreign key relationships:

• PO_HEADERS_ALL — joined on PO_ACCEPTANCES.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID.
• PO_RELEASES_ALL — joined on PO_ACCEPTANCES.PO_RELEASE_ID = PO_RELEASES_ALL.PO_RELEASE_ID.
• PO_LINE_LOCATIONS_ALL — joined on PO_ACCEPTANCES.PO_LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.PO_LINE_LOCATION_ID.
• PSB_EMPLOYEES — joined on PO_ACCEPTANCES.EMPLOYEE_ID = PSB_EMPLOYEES.EMPLOYEE_ID.
• PO_DRAFTS — joined on PO_ACCEPTANCES.DRAFT_ID = PO_DRAFTS.DRAFT_ID.