Results for “original_line_salesrep_id”

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

Overview

RA_CUST_TRX_LINE_SALESREPS_ALL is the Oracle Receivables (AR) transaction table that stores sales credit assignments at the transaction line level. Each row represents the allocation of revenue or non-revenue sales credit to a specific salesperson for a particular transaction line, enabling organizations to track and compensate sales representatives based on their contribution to receivables transactions. The _ALL suffix indicates that the table is partitioned by operating unit via the ORG_ID column, supporting multi-org access control (MOAC) so that users in different operating units see only their relevant sales credit records.

In Data Vault modeling terms, the heuristic classification of this table is satellite-leaning. It behaves primarily as a satellite attached to the RA_CUSTOMER_TRX_LINES_ALL hub, capturing descriptive and measurable sales credit attributes (split amounts, split percentages, salesperson references) that change over time. It also carries link characteristics through foreign keys to RA_SALESREPS_ALL and JTF_RS_GROUPS_B, but the dominant pattern is a descriptive extension of the transaction line.

Key Information Stored

The surrogate primary key is CUST_TRX_LINE_SALESREP_ID, enforced by the RA_CUST_TRX_LINE_SALESREPS_PK constraint and reinforced by the unique index RA_CUST_TRX_LINE_SALESREPS_U1. The unique index RA_CUST_TRX_LINE_SALESREPS_UK1 on CUSTOMER_TRX_LINE_ID and SALESREP_ID serves as a business-key candidate, ensuring that a given salesperson is credited only once per transaction line.

• CUSTER_TRX_LINE_SALESREP_ID – Surrogate primary key for the sales credit record.
• CUSTOMER_TRX_ID – Foreign key to RA_CUSTOMER_TRX_ALL, identifying the parent transaction.
• CUSTOMER_TRX_LINE_ID – Foreign key to RA_CUSTOMER_TRX_LINES_ALL, identifying the specific line receiving the credit.
• SALESREP_ID – Foreign key to RA_SALESREPS_ALL, identifying the salesperson assigned to the credit.
• REVENUE_AMOUNT_SPLIT and REVENUE_PERCENT_SPLIT – The monetary amount and percentage of revenue sales credit allocated to the salesperson.
• NON_REVENUE_AMOUNT_SPLIT and NON_REVENUE_PERCENT_SPLIT – The monetary amount and percentage of non-revenue sales credit allocation.
• REVENUE_SALESGROUP_ID and NON_REVENUE_SALESGROUP_ID – Foreign keys to JTF_RS_GROUPS_B, linking credit to a sales group for revenue and non-revenue splits respectively.
• ORIGINAL_LINE_SALESREP_ID and PREV_CUST_TRX_LINE_SALESREP_ID – Self-referencing salesperson pointers used for credit reassignment and audit trails.
• REVENUE_ADJUSTMENT_ID – Foreign key to AR_REVENUE_ADJUSTMENTS_ALL, associating the credit with a revenue adjustment.
• ORG_ID – Operating unit identifier supporting multi-org partitioning.
• WH_UPDATE_DATE – Warehouse update date used by ETL processes for incremental extraction.
• Standard who columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield segments for customer-specific extensions.

Common Use Cases and Queries

Typical usage includes sales credit reporting, commission calculation feeds, revenue recognition analysis, and audit reconciliation. A common query joins transaction lines to their credit assignments to report revenue split by salesperson:

• Sales credit by transaction: SELECT customer_trx_id, salesrep_id, revenue_amount_split FROM ra_cust_trx_line_salesreps_all WHERE customer_trx_id = :trx_id;
• Credit attribution by salesperson: aggregate REVENUE_AMOUNT_SPLIT and NON_REVENUE_AMOUNT_SPLIT grouped by SALESREP_ID for a given period, joining to RA_SALESREPS_ALL for names.
• Commission extraction: filter by WH_UPDATE_DATE or LAST_UPDATE_DATE to pull incremental changes for downstream commission systems.
• Revenue adjustment tracing: join to AR_REVENUE_ADJUSTMENTS_ALL via REVENUE_ADJUSTMENT_ID to analyze how adjustments affect credit splits.
• Multi-org reporting: constrain by ORG_ID to comply with MOAC policies.

Because the table is partitioned by ORG_ID, queries should always include the operating unit predicate to avoid full partition scans and to respect data security.

Related Objects

• RA_CUSTOMER_TRX_ALL – Joined via CUSTOMER_TRX_ID; the parent transaction header.
• RA_CUSTOMER_TRX_LINES_ALL – Joined via CUSTOMER_TRX_LINE_ID; the transaction line receiving credit.
• RA_SALESREPS_ALL – Joined via SALESREP_ID, ORIGINAL_LINE_SALESREP_ID, and PREV_CUST_TRX_LINE_SALESREP_ID; the salesperson master.
• JTF_RS_GROUPS_B – Joined via REVENUE_SALESGROUP_ID and NON_REVENUE_SALESGROUP_ID; sales group definitions.
• AR_REVENUE_ADJUSTMENTS_ALL – Joined via REVENUE_ADJUSTMENT_ID; revenue adjustment records.
• RA_CUST_TRX_LINE_GL_DIST_ALL – References this table via CUST_TRX_LINE_SALESREP_ID; accounting distributions derived from sales credits.
• AR_XLA_LINES_EXTRACT – References CUST_TRX_LINE_SALESREP_ID; used by Subledger Accounting for line-level extraction.
• FII_AR_SALES_CREDITS and FII_AR_SALES_CREDITS_D_T – Financial Intelligence application tables that reference SALESCREDIT_PK to this table’s primary key for analytical reporting.