Results for “ar_receipt_classes”

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

Overview

AR_RECEIPT_CLASSES is a Receivables reference and setup table that stores the definition of receipt classes. In Oracle E-Business Suite 12.1.1 and 12.2.2, a receipt class groups a set of operational attributes that determine how receipts are created, confirmed, remitted, and cleared. Each receipt class is referenced by receipt methods, which in turn drive how customer payments are processed, accounted for, and posted. Because receipt classes act as a central look-up that many transaction-level tables point to, they function as a foundational setup entity rather than a transactional record.

Under the heuristic Data Vault classification derived from the documented foreign key structure, AR_RECEIPT_CLASSES is hub-leaning. In a dimensional or Data Vault model it would typically be modeled as a hub, with RECEIPT_CLASS_ID as the business key and descriptive attributes distributed to a satellite. The table resides in the AR schema and is documented with 53 physical columns at the 12.2.2 ETRM level.

Key Information Stored

The most significant columns in AR_RECEIPT_CLASSES include:

• RECEIPT_CLASS_ID — the surrogate primary key, defined through AR_RECEIPT_CLASSES_PK, and the value propagated to all dependent tables.
• NAME — the user-facing name of the receipt class.
• CONFIRM_FLAG — controls whether receipts of this class require confirmation before funds are considered available.
• CLEAR_FLAG — indicates whether receipts of this class require clearing.
• REMIT_FLAG — indicates whether receipts of this class require remittance.
• CREATION_STATUS — the status applied to receipts created under this class.
• CREATION_METHOD_CODE — determines how receipts are created for the class (for example, automatic, manual, or remittance-based).
• REMIT_METHOD_CODE — the remittance method applied when receipts are remitted.
• NOTES_RECEIVABLE — a flag indicating whether notes receivable processing applies.
• BILL_OF_EXCHANGE_FLAG — a flag indicating whether bill of exchange processing applies.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield columns.
• GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20 — the global descriptive flexfield columns.
• ZD_EDITION_NAME — the editioning column used in the 12.2 online patching architecture.

The documented unique index AR_RECEIPT_CLASSES_U1 spans RECEIPT_CLASS_ID and ZD_EDITION_NAME, reinforcing RECEIPT_CLASS_ID as the business-key candidate.

Common Use Cases and Queries

Typical reporting and validation scenarios include listing all active receipt classes, identifying classes that require confirmation, clearing, or remittance, and joining receipt classes to receipt methods and batches. A common join pattern links AR_RECEIPT_CLASSES to AR_RECEIPT_METHODS and FV_AR_BATCHES_ALL through RECEIPT_CLASS_ID. Note the spelling variant: the user search term "fv_ar_batches_all" corresponds to the documented ETRM object FV_AR_BATCHES_ALL.

Representative query patterns include:

• Selecting NAME, CONFIRM_FLAG, CLEAR_FLAG, and REMIT_FLAG from AR_RECEIPT_CLASSES to review class configuration.
• Joining AR_RECEIPT_CLASSES to AR_RECEIPT_METHODS on RECEIPT_CLASS_ID to report all methods belonging to each class.
• Joining AR_RECEIPT_CLASSES to FV_AR_BATCHES_ALL on RECEIPT_CLASS_ID to analyze batch volumes and activity by receipt class.
• Filtering on CREATION_METHOD_CODE or REMIT_METHOD_CODE to identify classes driven by automatic or remittance-based processing.

Because receipt classes are referenced by batches and transactions, queries should always include the ZD_EDITION_NAME predicate when operating against a 12.2.2 repository with editioning enabled.

Related Objects

The documented foreign key relationships identify the principal dependent objects:

• AR_RECEIPT_METHODS — references AR_RECEIPT_CLASSES via RECEIPT_CLASS_ID.
• FV_AR_BATCHES_ALL — references AR_RECEIPT_CLASSES via RECEIPT_CLASS_ID.
• AR_BATCHES_ALL — references AR_RECEIPT_CLASSES via RECEIPT_CLASS_ID.
• CE_AVAILABLE_TRANSACTIONS_TMP — references AR_RECEIPT_CLASSES via RECEIPT_CLASS_ID.
• ZX_REP_TRX_DETAIL_T — references AR_RECEIPT_CLASSES via RECEIPT_CLASS_ID.
• JG_ZZ_VAT_TRX_DETAILS — references AR_RECEIPT_CLASSES via RECEIPT_CLASS_ID.

These relationships confirm the hub-leaning classification, with receipt class definitions acting as the parent entity for receipt methods, batches, cash management transactions, and tax reporting detail structures.