Results for “exception_code”

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

Overview

AR_AUTOREC_EXCEPTIONS is a Receivables (AR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM metadata, it is described as a "temporary table used to store exceptions found by Automatic Receipts and its related programs." Automatic Receipts is the concurrent process that generates receipts against a customer's open debit items based on receipt batch and payment program rules. During execution, the program validates each payment schedule and customer against a series of eligibility rules — minimum receipt amounts, bank account assignments, customer bank accounts, and remit-to bank accounts. When a candidate transaction fails one of these validations, the exception is written to AR_AUTOREC_EXCEPTIONS so that it can be reported to the user rather than silently discarded or allowed to fail the entire batch.

From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a link: it records an association between a receipt batch, a concurrent request, a payment schedule, a paying customer, and the relevant bank account entities, keyed by an exception event rather than by a persistent customer or transaction descriptor.

Key Information Stored

The table is documented with 22 columns in the 12.2.2 physical schema. The most significant include:

• BATCH_ID — the receipt batch being processed when the exception was raised; part of the composite primary key AR_AUTOREC_EXCEPTIONS_PK.
• REQUEST_ID — the concurrent request that produced the exception; also part of the primary key and a business-key candidate linking back to FND_CONCURRENT_REQUESTS.
• EXCEPTION_CODE — the third primary key component, identifying the specific validation failure (for example, an amount below the minimum or a missing bank account).
• PAYMENT_SCHEDULE_ID — the open debit item or installment that failed validation.
• PAYING_CUSTOMER_ID and PAYING_SITE_USE_ID — the customer and site use associated with the failing transaction.
• DUE_DATE — the due date of the affected payment schedule at the time of processing.
• CUST_MIN_REC_AMOUNT and BANK_MIN_REC_AMOUNT — the minimum receipt amount thresholds evaluated for the customer and bank, useful for diagnosing amount-related exceptions.
• CUST_BANK_ACCT_ID, REMIT_BANK_ACCT_ID, and REMIT_BANK_ACCT_USE_ID — the customer and remit bank account identifiers involved in the exception.
• CASH_RECEIPT_ID — populated where a receipt exists but the exception relates to downstream processing.
• ADDITIONAL_MESSAGE — supplementary diagnostic text for the exception.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

The primary use case is exception reporting after an Automatic Receipts run. Receivables users query this table to determine which payment schedules were excluded and why, then correct the underlying setup and rerun the batch. A typical query joins to the batch and request to isolate the latest run:

• Identify all exceptions for a batch: SELECT e.payment_schedule_id, e.exception_code, e.additional_message FROM ar_autorec_exceptions e WHERE e.batch_id = :batch_id;
• Trace exceptions to the concurrent request: join REQUEST_ID to FND_CONCURRENT_REQUESTS to obtain request dates and statuses.
• Resolve the affected transaction: join PAYMENT_SCHEDULE_ID to AR_PAYMENT_SCHEDULES_ALL and then to AR_CASH_RECEIPTS_ALL or RA_CUSTOMER_TRX_ALL for reporting.
• Aggregate recurring failure causes by EXCEPTION_CODE to identify systemic setup problems such as unresolved remit bank accounts or misconfigured minimum amounts.

Because the table is temporary in nature, its contents should be treated as an operational diagnostic rather than a permanent audit record.

Related Objects

The documented foreign keys connect AR_AUTOREC_EXCEPTIONS to the following objects, and these are the most useful joins in practice:

• AR_BATCHES_ALL via BATCH_ID — the receipt batch context.
• FND_CONCURRENT_REQUESTS via REQUEST_ID — the concurrent program execution that generated the exception.
• AR_PAYMENT_SCHEDULES_ALL via PAYMENT_SCHEDULE_ID — the affected transaction or installment.
• HZ_CUST_ACCOUNTS via PAYING_CUSTOMER_ID and HZ_CUST_SITE_USES_ALL via PAYING_SITE_USE_ID — the customer and site.
• AP_BANK_ACCOUNTS_ALL via CUST_BANK_ACCT_ID and REMIT_BANK_ACCT_ID — the bank account definitions referenced in the validation.
• CE_BANK_ACCT_USES_ALL via REMIT_BANK_ACCT_USE_ID — the remit-to bank account use assignment.

These relationships make AR_AUTOREC_EXCEPTIONS an effective diagnostic hub for troubleshooting Automatic Receipts failures across the customer, transaction, and bank account domains.