Results for “ar_ta_recv_trxset_all”

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

Overview

AR_TA_RECV_TRXSET_ALL is an Oracle Receivables (AR) configuration table that stores the association between Transaction Sets and Receivable accounts. It functions as a cross-reference or mapping object that links a receivables transaction set to the accounting flexfield combination (CCID) that defines the receivable account used when that transaction set is processed. In Oracle EBS 12.1.1 and 12.2.2, this object supports the Transaction Set ("TA") feature family, which allows multiple transactions to be grouped and processed together with consistent accounting treatment.

From a Data Vault modeling perspective, the heuristic classification supplied with the metadata is standalone, meaning the object is not decomposed into a parent hub with dependent satellites in the mined FK structure. In practice, however, the combination of PROFILE_ID and RECEIVABLES_ACCOUNT_CCID behaves like a link between a profile context and an accounting flexfield combination, which suggests it could be modeled as a link table in a Data Vault design. Its role in EBS is purely configuration/reference data rather than transactional activity.

Key Information Stored

The metadata identifies the following significant columns and key structures:

• RECEIVABLES_TRX_SET_ID — the surrogate primary key, enforced by the AR_TA_RECV_TRXSET_PK constraint. It uniquely identifies each association row.
• PROFILE_ID — identifies the profile or context to which the transaction set association applies. It participates in both unique keys.
• RECEIVABLES_ACCOUNT_CCID — the accounting flexfield combination (code combination ID) for the receivable account tied to the transaction set. It is part of the AR_TA_RECV_TRXSET_UK business-key candidate.
• TRX_SET_ID — the transaction set identifier. It is part of the AR_TA_RECV_TRXSET_UK1 business-key candidate.

Two unique business-key candidates are documented: AR_TA_RECV_TRXSET_UK on (PROFILE_ID, RECEIVABLES_ACCOUNT_CCID) and AR_TA_RECV_TRXSET_UK1 on (PROFILE_ID, TRX_SET_ID). These enforce the rule that a given profile may not be duplicated for the same receivable account or for the same transaction set. The surrogate key RECEIVABLES_TRX_SET_ID should be treated as the technical identifier, while the composite pairs above are the business keys. Additional descriptive or audit columns beyond those named were not documented in the supplied metadata.

Common Use Cases and Queries

Because the object is not implemented in the referenced database instance (per the metadata), queries should be validated against the target environment. Typical use cases include resolving the receivable account assigned to a transaction set for a given profile, auditing configuration completeness, and driving subledger accounting (SLA) lookups. A representative query joining the association to transaction-set and account definitions follows:

• Identify receivable accounts per transaction set: SELECT PROFILE_ID, TRX_SET_ID, RECEIVABLES_ACCOUNT_CCID FROM AR_TA_RECV_TRXSET_ALL WHERE TRX_SET_ID = :trx_set_id
• Resolve the CCID to a flexfield combination via FND_FLEX_VALUES / GL_CODE_COMBINATIONS to obtain the account string.
• Detect duplicate or missing profile mappings using the unique-key columns, supporting configuration QA and reconciliation reports.

Related Objects

The documented FK/PK structure classifies the object as standalone, so no enforced foreign keys to parent tables are listed. Nevertheless, the following objects are functionally significant:

• GL_CODE_COMBINATIONS — joined via RECEIVABLES_ACCOUNT_CCID to resolve the receivable account.
• FND_FLEX_VALUES / FND_ID_FLEX_SEGMENTS — used to expand the CCID into individual segment values.
• AR_TA_TRX_SETS / transaction-set definition objects — related through TRX_SET_ID.
• AR_TA_RECV_TRXSET_ALL itself, plus its constraints AR_TA_RECV_TRXSET_PK, AR_TA_RECV_TRXSET_UK, and AR_TA_RECV_TRXSET_UK1.
• Profile-related configuration, referenced through PROFILE_ID.

Because the table is not implemented in the sampled database, the related objects above should be confirmed against the actual AR data model in the target release.