Search Results rct_class_confirm_flag




Overview
Explore in AI Chat

Overview

AR_RCT_METHOD_H_V is an APPS-owned database view in the Oracle E-Business Suite Receivables (AR) module. It is documented as an "AR XLA Extract" view, meaning it exists to expose subledger accounting (XLA) extract data for receipt method and receipt class combinations at the header level. In Oracle EBS 12.1.1 and 12.2.2, the view serves as a reporting and integration access point into the Receivables extract tables used by the Subledger Accounting engine, allowing receipt method attributes, receipt class attributes, and their associated event and ledger context to be queried through a single denormalized interface.

Because the underlying XLA extract table (AR_XLA_LINES_EXTRACT) is populated during subledger accounting processing, this view is primarily useful to parties that need to inspect how receipt methods and receipt classes are captured for accounting events. It is not a transactional entry view; it is read-oriented and intended for extraction, reconciliation, and audit purposes.

Underlying Base Objects

The view is defined over three referenced base objects, all exposed through APPS synonyms:

  • AR_RECEIPT_METHODS — the receipt method master, aliased RM1 in the view text, providing method name, payment channel, printed name, and the foreign keys to receipt class and receipt method ID.
  • AR_RECEIPT_CLASSES — the receipt class master, aliased RC1, providing class-level flags and control attributes.
  • AR_XLA_LINES_EXTRACT — the subledger accounting extract table, aliased L, providing the event and ledger context and acting as the driving table for the extract.

The view joins AR_RECEIPT_METHODS to AR_XLA_LINES_EXTRACT on RECEIPT_METHOD_ID, and joins AR_RECEIPT_METHODS to AR_RECEIPT_CLASSES on RECEIPT_CLASS_ID. A level restriction of L.LEVEL_FLAG = 'H' confines the extract rows to the header level. The view text also carries an INDEX hint referencing AR_XLA_LINES_EXTRACT_N1, indicating the intended access path against the extract table.

Key Columns

The columns fall into three groups corresponding to the source objects. Receipt class attributes include RCT_CLASS_CLEAR_FLAG, RCT_CLASS_CONFIRM_FLAG, RCT_CLASS_CREATE_METHOD_CD, RCT_CLASS_CREATION_STATUS, RCT_CLASS_NAME, RCT_CLASS_NOTES_RECEIVABLE, RCT_CLASS_RECEIPT_CLASS_ID, RCT_CLASS_REMIT_FLAG, RCT_CLASS_REMIT_METHOD_CD, and the global attribute columns RCT_CLASS_GLOBAL_ATTR1 through 3 plus RCT_CLASS_GLOBAL_ATTR_CAT.

Receipt method attributes include RCT_MTHD_NAME, RCT_MTHD_PAYMENT_TYPE_CODE, RCT_MTHD_PRINTED_NAME, RCT_MTHD_RECEIPT_CLASS_ID, and RCT_MTHD_RECEIPT_METHOD_ID. Extract context columns include EVENT_ID and LEDGER_ID.

The RCT_CLASS_REMIT_FLAG column, derived from RC1.REMIT_FLAG, is directly relevant to the user search term "remit_flag." It indicates the remittance behavior configured on the receipt class, and it appears here because remittance handling directly influences subledger accounting and bank remittance processing for receipts.

Common Use Cases and Queries

Typical uses include auditing which receipt methods map to which classes for a given event or ledger, validating remittance configuration across receipt classes, and feeding downstream reconciliation or reporting extracts.

  • Filtering by remit flag to identify receipt classes whose remittance behavior supports or suppresses remittance processing.
  • Joining EVENT_ID and LEDGER_ID to subledger accounting event and ledger views to trace receipt method accounting context.
  • Reporting receipt method and receipt class combinations for a specific ledger.

Sample query:

SELECT rct_class_name, rct_class_remit_flag, rct_class_remit_method_cd, rct_mthd_name, rct_mthd_payment_type_code, event_id, ledger_id FROM apps.ar_rct_method_h_v WHERE rct_class_remit_flag = 'Y' AND ledger_id = :p_ledger_id;

Because the view depends on AR_XLA_LINES_EXTRACT, results reflect the extract data available at the time of query. Organizations should confirm that subledger accounting extraction has run for the periods under review before relying on the output.