Results for “ra_salesreps_all”

50+ results




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

Overview

RA_SALESREPS_ALL is the Oracle Receivables (AR) master table that stores information about salespeople. Within Oracle E-Business Suite 12.1.1 and 12.2.2, it functions as the central repository for every salesperson record used across the Order-to-Cash cycle, including Receivables, Order Management, and Projects. Salespeople defined here are assigned to customers, transactions, orders, agreements, and sales credits, and are linked to territories and salesforces for commission and revenue-accounting purposes.

ETRM metadata classifies RA_SALESREPS_ALL as hub-leaning under a heuristic Data Vault model. This should be read as a modeling suggestion: the table behaves like a hub, holding a stable, uniquely identified business entity (the salesperson) that numerous other tables reference through foreign keys, rather than a transactional link or a descriptive satellite. Its role is therefore foundational — the salesperson identity layer upon which credit, territory, and revenue relationships are built.

Note that the metadata records the object as "Not implemented in this database," indicating the documentation source did not have the physical table instantiated in the sampled environment; the structural metadata below is nonetheless authoritative for the EBS data model.

Key Information Stored

RA_SALESREPS_ALL is keyed by the surrogate primary key RA_SALESREPS_PK, defined on SALESREP_ID. This single-column numeric identifier is the value propagated to all dependent tables. The most significant columns documented in the metadata include:

Because the excerpts do not enumerate display columns such as name, number, or status, business-key candidates cannot be stated with certainty; the documented uniqueness is exclusively the SURROGATE key SALESREP_ID. The GL_ID_* columns effectively provide revenue-accounting defaults that flow into AutoAccounting for transactions attributed to the salesperson.

Common Use Cases and Queries

Typical scenarios include sales-credit reporting, commission reconciliation, territory-based revenue analysis, and diagnostic queries identifying orphaned or misconfigured salesperson references. A representative pattern joins the hub to its salesforce and ledger context:

  • Salesperson lookup with salesforce and ledger: SELECT s.salesrep_id, s.salesforce_id, s.set_of_books_id FROM ra_salesreps_all s WHERE s.salesrep_id = :id;
  • Credit reporting: join OE_SALES_CREDITS or RA_CUST_TRX_LINE_SALESREPS_ALL back to RA_SALESREPS_ALL on SALESREP_ID to summarize credited revenue by salesperson.
  • Transaction attribution: join RA_CUSTOMER_TRX_ALL to RA_SALESREPS_ALL on PRIMARY_SALESREP_ID to report invoices by primary salesperson.
  • Integrity checks: outer-join dependent tables to RA_SALESREPS_ALL to find sales credits or orders pointing to invalid or missing salespersons.
  • Validation across Order Management: query OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, SO_HEADERS_ALL, and their interface tables, all of which carry SALESREP_ID.

Related Objects

The following are the most significant dependents and references:

  • RA_CUSTOMERS — PRIMARY_SALESREP_ID references RA_SALESREPS_ALL.
  • RA_CUSTOMER_TRX_ALL — PRIMARY_SALESREP_ID references RA_SALESREPS_ALL.
  • RA_CUST_TRX_LINE_SALESREPS_ALL — SALESREP_ID, ORIGINAL_LINE_SALESREP_ID, and PREV_CUST_TRX_LINE_SALESREP_ID all reference this table.
  • RA_SALESREP_TERRITORIES — SALESREP_ID links salespeople to territories.
  • OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — SALESREP_ID references for order attribution.
  • OE_SALES_CREDITS — SALESREP_ID drives order-level sales credits.
  • SO_HEADERS_ALL, SO_AGREEMENTS_B, and SO_SALES_CREDITS — SALESREP_ID references across Order Management.
  • PA_CREDIT_RECEIVERS — SALESREP_ID links projects credit receivers.
  • AS_SALESFORCE and GL_SETS_OF_BOOKS — parent reference tables supplying salesforce and ledger context.