Results for “dont_pay_reason_code”

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

Overview

AP_UNSELECTED_INVOICES_ALL is a Payables module table owned by the AP schema. Its documented purpose is to hold invoices that could not be paid by a payment batch. During the payment batch process, Oracle Payables evaluates invoices against the selection criteria defined for a given payment batch. Invoices that pass validation are included in the batch, while those that fail — due to holds, missing bank information, invalid payment methods, or other disqualifying conditions — are written to this table together with a reason code explaining the exclusion. The table therefore acts as a diagnostic and audit record that administrators and payables staff can query to understand why specific invoices were skipped.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This is a sensible modeling suggestion: the table primarily records an association between a payment batch selection run (identified by CHECKRUN_ID) and an invoice (identified by INVOICE_ID), augmented by descriptive attributes such as the rejection reason. It does not stand alone as a business entity in its own right, which is characteristic of a link structure.

Key Information Stored

The table contains ten documented columns in the ETRM 12.2.2 schema. The most significant are:

• CHECKRUN_ID — Identifies the payment batch selection run (foreign key to AP_INV_SELECTION_CRITERIA_ALL) during which the invoice was evaluated and rejected.
• INVOICE_ID — Identifies the specific invoice that could not be paid (foreign key to AP_INVOICES_ALL).
• PAYMENT_NUM — The payment number associated with the batch attempt, useful for correlating with payment history.
• DONT_PAY_REASON_CODE — The code explaining why the invoice was not selected for payment; this is the key diagnostic attribute and typically maps to system-defined reasons such as holds, payment method mismatches, or insufficient funds.
• ORG_ID — The operating unit identifier, supporting multi-org partitioning and reporting.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns tracking who created and last modified each row.

No explicit surrogate primary key is documented in the supplied metadata. Rather, the combination of CHECKRUN_ID and INVOICE_ID functions as the business key, uniquely identifying the rejection of a given invoice within a specific selection run. Any query joining to source tables should use these two columns as the join basis.

Common Use Cases and Queries

The primary use case is troubleshooting payment batch shortfalls. A payables analyst running a payment batch and discovering fewer invoices paid than expected can query this table to identify the causes. A representative pattern:

• Join AP_UNSELECTED_INVOICES_ALL to AP_INVOICES_ALL on INVOICE_ID to retrieve invoice number, supplier, and amount.
• Join to AP_INV_SELECTION_CRITERIA_ALL on CHECKRUN_ID to retrieve batch identifier and selection parameters.
• Group by DONT_PAY_REASON_CODE to summarize the distribution of rejection reasons across a batch.

Reporting scenarios include daily exception reports listing unpaid invoices and their reasons, and audit reports reconciling batch expectations against actual payments.

Related Objects

• AP_INVOICES_ALL — joined on INVOICE_ID; the master invoice record.
• AP_INV_SELECTION_CRITERIA_ALL — joined on CHECKRUN_ID; defines the payment batch selection parameters.
• AP_PAYMENT_SCHEDULES_ALL — provides due dates and payment amounts for rejected invoices.
• AP_SUPPLIERS — supplier details for reporting rejected invoices by vendor.
• AP_LOOKUP_CODES — resolves DONT_PAY_REASON_CODE to descriptive meanings.
• AP_CHECKS_ALL — correlates payment numbers with issued payments.