Results for “ax_it_ar_cmapptrx_v”

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

Overview

The view AX_IT_AR_CMAPPTRX_V is a component of the Oracle E-Business Suite Global Accounting Engine (AX) module, specifically designated for Italian localization rules creation. Its ETRM documentation title, "Use for Italian rules creation," identifies it as a supporting object used in the configuration and operation of Italian statutory accounting and document sequencing logic within the Global Accounting Engine. The view exposes receivables application data joined to customer transaction document sequencing attributes, allowing the Italian rule engine to associate applied transactions with their originating invoices and the associated document sequence identifiers.

The view is documented in the ETRM metadata for Oracle EBS 12.1.1 and 12.2.2. Notably, the implementation metadata states "Not implemented in this database," indicating that the view definition is shipped with the product but is not instantiated in every environment — it is created only where the relevant Italian localization and Global Accounting Engine functionality is deployed. For this reason, the view may not appear in a default instance, and its presence is contingent on the localization setup.

Underlying Base Objects

Although the ETRM "Referenced base objects" field documents no objects, the view text explicitly defines the query over two core Oracle Receivables tables:

• RA_CUSTOMER_TRX_ALL (aliased CT) — the transactions header table holding invoice, credit memo, and debit memo records.
• AR_RECEIVABLE_APPLICATIONS_ALL (aliased RA) — the receivables application table that links cash receipts and credit transactions to the invoices they settle.

The join condition CT.CUSTOMER_TRX_ID = RA.APPLIED_CUSTOMER_TRX_ID ties each application record to the applied transaction, while the filter RA.CUSTOMER_TRX_ID IS NOT NULL restricts the result to true application rows. The SELECT DISTINCT clause eliminates duplicate combinations arising from the join. The view therefore presents a denormalized projection combining document sequencing attributes from the transaction header with application linkage information.

Key Columns

The view exposes a focused set of columns relevant to Italian document sequencing and receivables application analysis:

• CM_CUSTOMER_TRX_ID — maps to RA.CUSTOMER_TRX_ID (aliased in the view text as CUSTOMER_TRX_ID), identifying the credit memo or applying transaction.
• DOC_SEQUENCE_ID — the document sequence identifier assigned to the applied customer transaction (CT.DOC_SEQUENCE_ID). This is the column most directly associated with the user search term, and it links the transaction to the sequence configuration used for legal numbering.
• DOC_SEQUENCE_VALUE — the sequential number assigned to the document within the sequence (CT.DOC_SEQUENCE_VALUE), i.e., the official document number.
• TRX_DATE — the transaction date of the applied invoice (CT.TRX_DATE).
• TRX_NUMBER — the transaction number of the applied invoice (CT.TRX_NUMBER).
• INVOICE_CUST_TRX_ID — corresponds to RA.APPLIED_CUSTOMER_TRX_ID, identifying the original invoice being settled.

Common Use Cases and Queries

The predominant use case is Italian statutory reporting and Global Accounting Engine rule evaluation, where document sequence identifiers and values must be reconciled against receivables applications. Typical scenarios include verifying that all applied transactions carry valid document sequence assignments and auditing sequence gaps or duplicates.

A representative query retrieves all applications tied to a specific document sequence:

• SELECT doc_sequence_id, doc_sequence_value, trx_number, trx_date, cm_customer_trx_id, invoice_cust_trx_id FROM ax_it_ar_cmapptrx_v WHERE doc_sequence_id = :p_seq_id ORDER BY doc_sequence_value;

Another common pattern joins the view to RA_CUSTOMER_TRX_ALL or FND_DOCUMENT_SEQUENCES to resolve the sequence name and legal entity context. Because the view is not implemented in every database, queries should first confirm object existence via ALL_VIEWS before execution. Where the view is absent, equivalent logic can be reproduced directly from RA_CUSTOMER_TRX_ALL and AR_RECEIVABLE_APPLICATIONS_ALL using the documented join and filter conditions.