Results for “batch_name”

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

Overview

AP_HISTORY_INVOICES_ALL is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the AP schema. Its documented purpose is to hold summary information about purged invoices. When the Payables Purge program eliminates fully paid, cancelled, or otherwise eligible invoice records from the live AP_INVOICES_ALL tables, this object retains a lightweight historical footprint so that prior activity can be traced without restoring the full transactional record set.

The table is recorded as VALID with a single-column primary key, AP_HISTORY_INVOICES_PK, defined on INVOICE_ID. From a heuristic Data Vault modeling perspective derived from its foreign key topology, the object is classified as satellite-leaning. This is consistent with its role as an historical, descriptive adjunct to a primary business entity rather than a hub of independent business keys or a pure link between entities. It carries descriptive attributes about invoices that no longer exist in the transactional tables.

Key Information Stored

The documented physical schema for 12.2.2 contains 11 columns. The most significant include:

• INVOICE_ID — the surrogate primary key (AP_HISTORY_INVOICES_PK). It preserves the original identifier of the purged invoice, allowing downstream historical references to remain resolvable.
• VENDOR_ID and VENDOR_SITE_CODE — the supplier and supplier site associated with the purged invoice.
• INVOICE_NUM — the human-readable supplier invoice number.
• INVOICE_DATE — the invoice date captured at purge time.
• INVOICE_AMOUNT — the monetary value of the purged invoice, supporting historical balances and reporting.
• BATCH_NAME — the invoice batch in which the purged invoice was originally entered.
• PURGE_NAME — a foreign key to FINANCIALS_PURGES, identifying the purge run that removed the record.
• DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE — the document sequence identifier and its assigned value, with DOC_SEQUENCE_ID referencing FND_DOCUMENT_SEQUENCES.
• ORG_ID — the operating unit identifier, supporting multi-org reporting.

A secondary unique index, AP_HISTORY_INVOICES_U2, is defined across VENDOR_ID, INVOICE_NUM, and ORG_ID, making these three columns the documented business-key candidate. This combination distinguishes the surrogate INVOICE_ID from the natural business identifier of a supplier invoice within an operating unit.

Common Use Cases and Queries

The principal use case is post-purge audit and reconciliation. Payables administrators use this table to confirm which invoices were removed during an archive or purge cycle and to verify purge parameters.

• Purge audit by run: joining PURGE_NAME to FINANCIALS_PURGES to confirm the scope of a specific purge program execution.
• Supplier invoice history: querying by VENDOR_ID, INVOICE_NUM, and ORG_ID to determine whether a specific invoice was purged, using the unique business-key index.
• Document sequence verification: joining DOC_SEQUENCE_ID to FND_DOCUMENT_SEQUENCES to validate that sequence values assigned prior to purge remain consistent.
• Payments reconstruction: linking INVOICE_ID to AP_HISTORY_INV_PAYMENTS_ALL to trace historical payment activity for purged invoices.

A representative pattern selects the surrogate key and descriptive attributes while constraining on the business key:

• SELECT invoice_id, invoice_num, invoice_date, invoice_amount FROM ap.ap_history_invoices_all WHERE vendor_id = :vendor_id AND invoice_num = :invoice_num AND org_id = :org_id;

Related Objects

The following relationships are documented for this object and represent its most significant dependencies:

• FINANCIALS_PURGES — referenced via AP_HISTORY_INVOICES_ALL.PURGE_NAME; identifies the purge run.
• FND_DOCUMENT_SEQUENCES — referenced via AP_HISTORY_INVOICES_ALL.DOC_SEQUENCE_ID; defines document sequence definitions.
• AP_HISTORY_INV_PAYMENTS_ALL — references AP_HISTORY_INVOICES_ALL.INVOICE_ID; stores historical payment-linkage detail for purged invoices.

Together these objects form the historical archive layer of Payables, complementing the live AP_INVOICES_ALL transactional tables and the concurrent purge and archive programs that populate this structure.