Search Results fun_trx_type_ar_maps




Overview
Explore in AI Chat

Overview

FUN_TRX_TYPE_AR_MAPS is a Financials Common Modules (FUN) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that stores the mapping between an Intercompany transaction type and the corresponding Receivables transaction type and Receivables memo line. Its primary role is to drive the automatic creation of Receivables invoices and credit memos when Intercompany transactions are transferred into the Receivables subledger. Without this mapping, the Intercompany process cannot determine which AR transaction type or memo line to apply against the generated invoice lines, so the table acts as an essential configuration bridge between the Advanced Global Intercompany System (AGIS) and Oracle Receivables.

Its heuristic Data Vault classification, mined from the foreign key structure, is reported as standalone — that is, the table does not participate in an inferred hub/link/satellite chain via its documented foreign keys, but is more precisely modeled as a mapping or reference lookup. From a modeling perspective it behaves like a link table relating an Intercompany transaction type to an AR transaction type and an AR memo line.

Key Information Stored

The table is documented with 27 columns in the ETRM 12.2.2 schema, of which the following carry the substantive business meaning:

The surrogate key is TRX_TYPE_MAP_ID. The business identity of a row is effectively the combination of TRX_TYPE_ID with ORG_ID, since a transaction type is mapped per operating unit.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios include verifying that every Intercompany transaction type in use has a valid AR mapping, auditing the AR transaction types selected for invoice generation, and diagnosing failures when the Intercompany invoice process cannot resolve a Receivables transaction type.

  • Listing mappings for a given operating unit: query FUN_TRX_TYPE_AR_MAPS filtered by ORG_ID, projecting TRX_TYPE_ID, AR_TRX_TYPE_ID, AR_CM_TRX_TYPE_ID and MEMO_LINE_ID.
  • Joining to IGI_EXP_TRX_TYPE on TRX_TYPE_ID = TRX_TYPE_ID to obtain the intercompany transaction type name for readability.
  • Joining to AR_MEMO_LINES_ALL_B on MEMO_LINE_ID to validate that the memo line referenced is active and belongs to the expected AR setup.
  • Detecting unmapped intercompany transaction types by outer-joining the mapping table to IGI_EXP_TRX_TYPE and filtering for NULL TRX_TYPE_MAP_ID.
  • Auditing recent configuration changes using LAST_UPDATED_BY and LAST_UPDATE_DATE to identify who altered a mapping.

Related Objects

The most significant dependent and referenced objects are:

  • IGI_EXP_TRX_TYPE — referenced via TRX_TYPE_ID; supplies the Intercompany transaction type definition.
  • AR_MEMO_LINES_ALL_B — referenced via MEMO_LINE_ID; supplies the Receivables memo line applied to generated invoices.
  • AR_TRX_TYPE / Receivables transaction type setup — the target of AR_TRX_TYPE_ID and AR_CM_TRX_TYPE_ID, defining invoice and credit memo types.
  • IGI_ intercompany transaction tables — the AGIS transaction and batch tables that drive the transfer process invoking this mapping.
  • FUN_TRX_TYPE_AR_MAPS_ _S and associated concurrent programs within the FUN and IGI modules that read these mappings during intercompany invoice generation.