Results for “release_number”

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

Overview

POS_ACK_EDIT_V is a reporting view owned by the APPS schema within Oracle iProcurement (product code ICX), delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. Its functional purpose is to support the supplier acknowledgement and acceptance process, exposing the data set that buyers review when confirming, accepting, or rejecting supplier acknowledgements against purchase orders and releases. The view materializes a flattened, presentation-ready structure rather than raw transactional data, combining purchasing document attributes, supplier identifying information, and acknowledgement-specific workflow columns — such as ACCEPTANCE_FLAG, ACCEPT, REJECT, ACCEPTANCE_TYPE_CODE, COMMENTS, and APPROVAL_STATUS — in a single consumable record set.

Because the view terminates with ORDER BY PO_NUMBER, the result set is deterministic, which makes it dependable for the iProcurement acknowledgement pages and for downstream inquiry reports. In ETRM 12.2.2, the object is documented as VALID, confirming it is a supported component of the shipped application data model rather than a customer-specific customization.

Underlying Base Objects

The view is defined over a single documented referenced base object: the synonym POS_ACK_SELECT, which is the source of every column projected by the view. The view performs no joins, unions, or aggregation — its SELECT list enumerates thirty-one columns taken directly from POS_ACK_SELECT, so POS_ACK_EDIT_V is best understood as a security, filtering, or presentation layer over that underlying acknowledgement selection object. The synonym typically resolves to a purchasing acknowledgement query in the PO schema, but the documented ETRM relationship stops at POS_ACK_SELECT as the immediate dependency. Implementers tracing lineage further must inspect the synonym definition and the objects it resolves to, since no other base tables are documented for this view.

Key Columns

• DOCUMENT_TYPE_CODE / DOCUMENT_TYPE — Classifies the acknowledged document (for example, a standard purchase order versus a blanket agreement release). DOCUMENT_TYPE_CODE is the stored code value and DOCUMENT_TYPE the corresponding user-facing display value.
• PO_HEADER_ID / PO_RELEASE_ID — Primary and foreign key identifiers linking the acknowledgement to the PO header and, where applicable, the release.
• PO_NUMBER / RELEASE_NUMBER / REVISION_NUMBER — Human-readable document numbering, including release and revision context.
• ACCEPTANCE_FLAG / ACCEPT / REJECT — Action indicators that drive the acceptance decision in the acknowledgement UI.
• ACCEPTANCE_TYPE_CODE / ACCEPTANCE_TYPE / COMMENTS — Categorize the acceptance and capture buyer narrative.
• ACCEPTANCE_REQUIRED / ACCEPTANCE_STATUS / ACCEPTANCE_REQUIRED_BY / APPROVAL_STATUS — Track acknowledgement workflow state and due dates.
• SUPPLIER_ORG_ID / SUPPLIER_ID / SUPPLIER_SITE_ID / SUPPLIER_NAME / SUPPLIER_SITE — Resolve the responding supplier and its site.
• BUYER_ID / BUYER_NAME, SHIPTO_LOCATION_ID / SHIPTO_LOCATION, CARRIER_CODE / CARRIER, CURRENCY_CODE, TOTAL — Provide administrative, delivery, and financial context for each acknowledgement line.

Common Use Cases and Queries

Typical applications include buyer worklists showing acknowledgements pending acceptance, exception queries isolating rejected or overdue acknowledgements, and supplier-facing extracts grouped by supplier and document type.

Locate pending acknowledgements:

• SELECT po_number, release_number, document_type, supplier_name, acceptance_status FROM apps.pos_ack_edit_v WHERE acceptance_status = 'PENDING' ORDER BY po_number;

Isolate rejections by document type:

• SELECT po_number, document_type_code, document_type, comments FROM apps.pos_ack_edit_v WHERE acceptance_flag = 'N' AND document_type_code = 'PO';

Summarize by supplier and document type:

• SELECT supplier_name, document_type, COUNT(*) FROM apps.pos_ack_edit_v GROUP BY supplier_name, document_type;

Because no joins are performed by the view itself, queries against it remain efficient and safe for reporting users, provided the inherited ORDER BY PO_NUMBER is accounted for in outer queries.