Results for “ar_ta_split_merge_v”

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

Overview

AR_TA_SPLIT_MERGE_V is an Oracle Receivables (AR) reporting view that consolidates deduction assignment, split, and merge information tied to Receivables transactions. It belongs to the Oracle Trade Management / Advanced Collections family of objects, where "TA" denotes the Trade Accounting and deduction-management schema, and the "SPLIT_MERGE" suffix indicates its role in presenting transactions that have been split or reassigned between collectors and sales representatives.

The view is a read-only, query-oriented object. In the provided ETRM metadata it is explicitly documented as Not implemented in this database, meaning it exists as a shipped definition but carries no materialized rows until the underlying deduction-assignment and transaction data are populated. Its principal value is analytical: it exposes a denormalized, human-readable picture of a deduction transaction — the customer, the transaction number, the assigned and transferred sales representatives/collectors, amounts due, currency details, and the deduction narrative — in a single queryable layer. This makes it well suited to reporting, reconciliation, and downstream integration where the caller needs deduction status and ownership transfer context without joining a dozen AR base tables manually.

Underlying Base Objects

The view is defined over the following documented base objects:

• AR_PAYMENT_SCHEDULES (PS) — transaction and payment-schedule records, including TRX_NUMBER, AMOUNT_DUE_REMAINING, STATUS, GL_DATE, ORG_ID, and PAYMENT_SCHEDULE_ID.
• AR_TA_DEDN_ASSGNS (DED) — deduction assignment records holding ASSIGNED_TO_SALESREP_ID, ASSIGNED_TO_COLLECTOR_ID, TRANSFER_TO_SALESREP_ID, TRANSFER_TO_COLLECTOR_ID, DEDUCTN_TEXT, and DATE_ASSIGNED.
• RA_CUSTOMER_TRX (CTX) and RA_CUSTOMER_TRX_LINES (CTL) — the transaction header and line context, including comments, currency, exchange rate, attributes, and related transaction references.
• RA_CUST_TRX_TYPES (CTT) — transaction type metadata, filtered to TYPE IN ('DM','CM') with ATTRIBUTE10 IN ('DED','UCD').
• HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CUST_SITE_USES — customer account number, party name (truncated to 50 bytes via SUBSTRB), and site location.
• AR_COLLECTORS (COL, COL2) and RA_SALESREPS (SREP, SREP2) — resolved names for current and transferred collector/salesrep assignments.

The joins follow AR_PAYMENT_SCHEDULES through the customer transaction ID to the deduction assignment, and outward to the customer, transaction type, party, and site. The OUTER JOIN on RA_CUSTOMER_TRX allows schedules to persist even where a matching transaction header is not present in the expected join path.

Key Columns

• TRANSFER_TO_SALESREP_ID / TRANSFER_TO_COLLECTOR_ID — the assignment targets when a deduction is transferred; these underpin the "transfer_to_name" concept users search for.
• Assigned-to and transferred-to names — DECODE expressions resolve IDs to names from RA_SALESREPS and AR_COLLECTORS, returning NULL when both ID columns are null.
• AMOUNT_DUE_REMAINING — the outstanding balance on the payment schedule.
• STATUS — decoded into OPEN, CLOSED, PENDING, or VOID.
• PARTY_NAME (SUBSTRB 50), ACCOUNT_NUMBER, LOCATION — customer identification.
• TRX_DATE, GL_DATE, DATE_ASSIGNED — key dates for aging and assignment analysis.
• ATTRIBUTE1–15 and DEDUCTN_TEXT — descriptive and narrative context for the deduction.

Common Use Cases and Queries

Typical usage includes identifying open deductions by assigned collector, tracking deductions that have been transferred between representatives, and reconciling deduction balances to transaction types DM/CM.

Sample query returning current and transferred assignment names for open deductions:

• SELECT trx_number, party_name, amount_due_remaining, transfer_to_salesrep_id, transfer_to_collector_id
• FROM ar_ta_split_merge_v
• WHERE status = 'OPEN' AND org_id = :p_org_id
• ORDER BY trx_date DESC;

Because the view is not implemented in the database, queries should be validated against the source tables in the target environment, and any integration should treat the view as a reporting convenience rather than a transactional interface.