Search Results ar_mfar_extract_s

Overview

ARP_XLA_EXTRACT_MAIN_PKG is the central extraction engine that connects Oracle Receivables transaction data to the Subledger Accounting (XLA) accounting engine in Oracle E-Business Suite 12.1.1 and 12.2.2. Its business purpose is to read Receivables source documents—invoices, credit memos, debit memos, adjustments, cash receipts, receivable applications, miscellaneous cash receipts, and cash basis distributions—assemble the correct accounting event and line data, and hand that data to XLA so that journal entries can be generated, accounted, and posted according to the applicable accounting method.

The user search term ar_mfar_extract_s corresponds to the AR_MFAR_EXTRACT_S table, a key staging/source table that the package references for multi-funding and multi-application Receivables (MFAR) extraction logic. The package is owned by APPS and reports a status of VALID. It depends on core AR packages (ARP_ACCT_MAIN, ARP_DET_DIST_PKG, ARP_GLOBAL), XLA views and rules, Oracle Workflow, FND utilities, and GL ledgers, confirming its role as the bridge between Operational Receivables and Subledger Accounting.

Key Procedures and Functions

The package exposes 27 documented procedures and functions. The principal ones include:

• EXTRACT — the main driver routine that reads AR source transactions and populates the XLA extract lines for accounting.
• PREACCOUNTING — prepares data ahead of the accounting call, validating eligible events and documents.
• POSTACCOUNTING — handles processing that follows the accounting engine invocation, including finalization of extracted data.
• POSTPROCESSING — post-extraction cleanup and follow-up logic.
• FLAG_THE_POSTING_ID — marks the posting identifier on extracted records for subsequent posting control.
• LOCK_DOCUMENTS_FOR_XLA, LOCKING_STATUS, EXTRACT_STATUS, POSTING_CTL_STATUS — concurrency control and status reporting helpers that lock source documents and report the current extraction/posting state.
• LOAD_HEADER_DATA_CTLGD, LOAD_HEADER_DATA_ADJ, LOAD_HEADER_DATA_CRH, LOAD_HEADER_DATA_TH — load header-level accounting data for customer transactions/GL distributions, adjustments, cash receipt history, and transaction history respectively.
• LOAD_LINE_DATA_CTLGD, LOAD_LINE_DATA_ADJ, LOAD_LINE_DATA_CRH, LOAD_LINE_DATA_TH, LOAD_LINE_DATA_CRH_MF — load line-level accounting data for the same source categories, with the CRH_MF variant addressing multi-funding cash receipt extraction.
• ED_UNED_TRX and THE_SEGMENT_VALUE — assist with earned/unearned transaction handling and segment value resolution.

Parameter lists are not reproduced here; only documented procedure names and their roles are described.

Tables Accessed

The package reads and writes AR operational and staging tables via APPS synonyms, notably AR_ADJUSTMENTS_ALL, AR_CASH_BASIS_DISTS_ALL, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_CRH_APP_GT, AR_CRH_GT, AR_DISTRIBUTIONS_ALL, AR_LINE_APP_DETAIL_GT, AR_MFAR_EXTRACT_S, AR_MISC_CASH_DISTRIBUTIONS_ALL, AR_PAYMENT_SCHEDULES_ALL, AR_POSTING_CONTROL_S, AR_RECEIVABLES_TRX_ALL, and AR_RECEIVABLE_APPLICATIONS. These supply the source transactions, distributions, receipt history, and application details required for XLA extraction. Supporting tables include RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, GL_LEDGERS, GL_SETS_OF_BOOKS, FND_SEGMENT_ATTRIBUTE_VALUES, and XLA views (XLA_ENTITY_EVENTS_V, XLA_EVENTS_GT, XLA_POST_ACCTG_EVENTS_V, XLA_ACCTG_METHOD_RULES, XLA_PRODUCT_RULES_TL) that define accounting rules and events.

Usage Notes

ARP_XLA_EXTRACT_MAIN_PKG is invoked indirectly by Receivables during accounting creation, typically through the Create Accounting process, AutoAccounting/XLA concurrent programs, and standard AR posting flows. It is not called directly from forms or user code in normal operation and is not referenced by any database object per the documentation, making it a terminal controller package within the extraction chain. The package is referenced by three other packages within APPS. Because it locks documents and manages posting control, extensions should invoke it only within the supported accounting workflow sequence to avoid locking conflicts and inconsistent extract data.