Results for “ar_receipt_classes_u1”

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

Overview

AR.AR_RECEIPT_CLASSES is a core Oracle Receivables (AR) setup table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores user-defined receipt classes, which are configuration templates that classify how receipts are created and processed. A receipt class determines whether receipts assigned to it are created manually or automatically, and which downstream processing steps are required — confirmation, remittance, and clearance. Because these flags drive application behavior directly, the table functions as a control point for the entire receipt lifecycle, from entry through bank clearance.

The object is registered as VALID in the ETRM repository under schema AR, with FND Design Data mapped to AR.AR_RECEIPT_CLASSES and storage in the APPS_TS_TX_DATA tablespace (PCT Free 10). The heuristic Data Vault classification is hub-leaning, derived from its position at the center of a set of foreign-key relationships. As a modeling suggestion, AR_RECEIPT_CLASSES is best treated as a hub: it holds a stable, uniquely identified business entity (the receipt class) that multiple dependent tables reference through RECEIPT_CLASS_ID.

Key Information Stored

The surrogate primary key is RECEIPT_CLASS_ID (NUMBER(15)), enforced by the AR_RECEIPT_CLASSES_PK constraint. The documented unique index is AR_RECEIPT_CLASSES_U1, defined over (RECEIPT_CLASS_ID, ZD_EDITION_NAME); note that in the documented 12.2.2 physical schema this index includes the ZD_EDITION_NAME column, so its uniqueness is scoped by edition in online-patching (AD Online Patching) editions.

• NAME — the descriptive name of the receipt class presented to users.
• CREATION_METHOD_CODE — AUTOMATIC for system-generated receipts, MANUAL for manually entered receipts.
• CONFIRM_FLAG — Y or N; whether confirmation is required for receipts in this class.
• REMIT_FLAG — Y or N; whether remittance processing is required.
• REMIT_METHOD_CODE — FACTORING, STANDARD, or STANDARD_AND_FACTORING, indicating the remittance options available.
• CLEAR_FLAG — N for no clearance required (receipt treated as cleared at creation), S for automatic clearing, Y for clearance by matching.
• CREATION_STATUS — status value associated with receipt creation.
• NOTES_RECEIVABLE and BILL_OF_EXCHANGE_FLAG — flags supporting notes receivable and bill-of-exchange receipt handling.
• Attribute / Global Attribute flexfields — ATTRIBUTE_CATEGORY with ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE_CATEGORY with GLOBAL_ATTRIBUTE1–20, providing extensibility without schema change.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for audit and concurrency tracking.

The documented column list totals 53 columns; the flexfield and WHO columns above account for the majority beyond the functional receipt-class attributes.

Common Use Cases and Queries

Receipt classes are configured during implementation and reference data migrations, then queried for validation, reporting, and troubleshooting. Typical scenarios include reconciling active receipt classes against receipt methods, verifying which classes require automatic clearing, and auditing configuration changes through the WHO columns.

A simple lookup joins the class to its dependent receipt methods:

• SELECT arc.receipt_class_id, arc.name, arc.creation_method_code, arc.confirm_flag, arc.remit_flag, arc.clear_flag FROM ar.ar_receipt_classes arc WHERE arc.creation_method_code = 'AUTOMATIC';
• SELECT arc.name receipt_class, arm.name receipt_method FROM ar.ar_receipt_classes arc, ar.ar_receipt_methods arm WHERE arc.receipt_class_id = arm.receipt_class_id ORDER BY arc.name, arm.name;

Reporting uses include an inventory of classes with their processing requirements, an audit extract filtered on LAST_UPDATE_DATE, and a batch-to-class analysis joining AR_BATCHES_ALL or FV_AR_BATCHES_ALL on RECEIPT_CLASS_ID. Flexfield attributes are commonly surfaced where clients extend the class with site-specific data; filter on ATTRIBUTE_CATEGORY to isolate those rows.

Related Objects

AR_RECEIPT_CLASSES is referenced by several dependent objects through the RECEIPT_CLASS_ID foreign key, confirming its hub-like role.

• AR.AR_RECEIPT_METHODS — AR_RECEIPT_METHODS.RECEIPT_CLASS_ID references this table; each receipt method belongs to a receipt class.
• AR.AR_BATCHES_ALL — AR_BATCHES_ALL.RECEIPT_CLASS_ID references the class used for each receipt batch.
• FV. FV_AR_BATCHES_ALL — FV_AR_BATCHES_ALL.RECEIPT_CLASS_ID links federal/treasury batches to the class.
• CE.CE_AVAILABLE_TRANSACTIONS_TMP — CE_AVAILABLE_TRANSACTIONS_TMP.RECEIPT_CLASS_ID; cash management obtains receipt-class context for available transactions.
• ZX.ZX_REP_TRX_DETAIL_T — ZX_REP_TRX_DETAIL_T.RECEIPT_CLASS_ID; tax reporting detail references the receipt class.
• JG.JG_ZZ_VAT_TRX_DETAILS — JG_ZZ_VAT_TRX_DETAILS.RECEIPT_CLASS_ID; Latin American tax detail uses the same key.

APIs that create or process receipts, such as AR_RECEIPT_API_PUB, accept a receipt class as an input and resolve its flags through this table. Any query joining dependent tables should use RECEIPT_CLASS_ID as the common column.