Results for “maturity_date_rule_code”

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

Overview

AR_RECEIPT_METHODS is the Oracle Receivables reference table that defines the payment methods available to an operating unit for recording customer receipts. Each row represents a distinct receipt method — for example Check, Cash, Wire, Credit Card, or Lockbox — and carries the processing rules that Oracle Receivables applies when a receipt is created, printed, matured, or cleared. The table resides in the AR schema and is owned by the Receivables product. Because approximately forty downstream tables carry a RECEIPT_METHOD_ID foreign key — including AR_CASH_RECEIPTS_ALL, RA_CUSTOMER_TRX_ALL, AR_LOCKBOXES_ALL, and AR_PAYMENTS_INTERFACE_ALL — AR_RECEIPT_METHODS functions as a shared reference (dimension) object across Receivables, Cash Management, Order Management, and Payments. Its heuristic Data Vault classification is hub: a stable, business-keyed entity that anchors the RECEIPT_METHOD_ID identifier and absorbs descriptive attributes through the surrounding transaction and interface tables. This object is present and valid in both Oracle EBS 12.1.1 and 12.2.2; the 12.2.2 physical schema documents 64 columns, including edition-tracking columns introduced by the multi-tenancy (ZD_EDITION_NAME) model.

Key Information Stored

RECEIPT_METHOD_ID is the surrogate primary key (AR_RECEIPT_METHODS_PK) and the column referenced by every foreign key relationship. Two unique constraints serve as business-key candidates: AR_RECEIPT_METHODS_U1 on (RECEIPT_METHOD_ID, ZD_EDITION_NAME) and AR_RECEIPT_METHODS_U2 on (NAME, ZD_EDITION_NAME), confirming that the method name is the functional business key and that the 12.2 schema is edition-aware. RECEIPT_CLASS_ID links the method to its class defined in AR_RECEIPT_CLASSES. START_DATE and END_DATE govern the effective period during which the method may be selected. LEAD_DAYS, MATURITY_DATE_RULE_CODE, and RECEIPT_CREATION_RULE_CODE drive the automatic maturity and receipt-creation behavior associated with the method. AUTO_PRINT_PROGRAM_ID references the concurrent program used to print receipts, while AUTO_TRANS_PROGRAM_ID supports the automatic transaction program. PRINTED_NAME supplies the name shown on printed output, and PAYMENT_TYPE_CODE and PAYMENT_CHANNEL_CODE (the latter referencing IBY_FNDCPT_PMT_CHNNLS_B) classify the method for the Oracle Payments funds-capture framework. BR_CUST_TRX_TYPE_ID and BR_MIN_ACCTD_AMOUNT / BR_MAX_ACCTD_AMOUNT carry the Brazil localization rules for the receivables document type and accounting amount thresholds. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) provide audit information, with ATTRIBUTE and GLOBAL_ATTRIBUTE column sets reserved for extensibility.

Common Use Cases and Queries

Typical queries resolve a receipt method ID to its descriptive name across reporting tables, or enumerate the active methods available to a user. Reporting on receipts by method, validating payment-method setup before loading interface data, and joining to Payments channel configuration are the most frequent patterns.

• Resolve method names on receipts: SELECT r.receipt_number, m.name FROM ar_cash_receipts_all r, ar_receipt_methods m WHERE r.receipt_method_id = m.receipt_method_id;
• List currently active methods: SELECT receipt_method_id, name, receipt_class_id FROM ar_receipt_methods WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• Validate interface loads: SELECT i.receipt_number, m.name FROM ar_payments_interface_all i, ar_receipt_methods m WHERE i.receipt_method_id = m.receipt_method_id;
• Methods used on transactions: SELECT t.trx_number, m.name FROM ra_customer_trx_all t, ar_receipt_methods m WHERE t.receipt_method_id = m.receipt_method_id;

Because the table is a hub, most operational reporting joins outward from the transaction tables to this reference to obtain the method label.

Related Objects

The most significant dependencies are the tables that both reference and constrain this object.

• AR_RECEIPT_CLASSES — referenced via AR_RECEIPT_METHODS.RECEIPT_CLASS_ID; defines the parent class of each method.
• IBY_FNDCPT_PMT_CHNNLS_B — referenced via PAYMENT_CHANNEL_CODE; aligns the method with the Payments channel.
• AP_PAYMENT_PROGRAMS — referenced via AUTO_PRINT_PROGRAM_ID; supplies the printing concurrent program.
• RA_CUST_TRX_TYPES_ALL — referenced via BR_CUST_TRX_TYPE_ID for the Brazil localization document type.
• AR_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RECEIPTS_ALL — carry RECEIPT_METHOD_ID for actual and unconfirmed receipts.
• AR_PAYMENTS_INTERFACE_ALL — stores RECEIPT_METHOD_ID during receipt import.
• AR_LOCKBOXES_ALL — links lockbox definitions to a receipt method.
• RA_CUSTOMER_TRX_ALL and RA_CUST_RECEIPT_METHODS — store the default receipt method on transactions and customer assignments.