Search Results ra_salesreps




Overview
Explore in AI Chat

Overview

RA_SALESREPS is a backward-compatible, single-organization view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). Its primary function is to expose salesperson information from the multi-organization table RA_SALESREPS_ALL in a form that legacy code, reports, and integrations written against earlier releases can continue to use without modification. In a multi-org architecture, the underlying data store is RA_SALESREPS_ALL, which supports multiple operating units identified by ORG_ID. RA_SALESREPS presents a filtered, single-org perspective, and although the view text shown here does not explicitly include a WHERE clause on ORG_ID, it is intended to be queried within the context of the current operating unit so that only the appropriate salesperson rows are returned. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and remains a supported object for reporting and integration access to salesperson data.

Underlying Base Objects

The view is defined over two documented base objects referenced through the APPS schema:

The join condition links JRS.RESOURCE_ID to RES.RESOURCE_ID and filters on resource category, restricting rows to categories such as EMPLOYEE, OTHER, PARTY, PARTNER, and SUPPLIER_CONTACT. This ensures only valid salesperson resources associated with those categories are surfaced.

Key Columns

  • SALESREP_ID — primary identifier for the salesperson.
  • NAME — salesperson name sourced from the resource extension (RESOURCE_NAME aliased as NAME).
  • SALESREP_NUMBER — user-facing salesperson number.
  • STATUS and START_DATE_ACTIVE / END_DATE_ACTIVE — control whether the salesperson is active and the effective date range.
  • ORG_ID — the operating unit to which the salesperson belongs.
  • GL_ID_REV, GL_ID_FREIGHT, GL_ID_REC, SET_OF_BOOKS_ID — accounting and revenue/freight/receivable distribution references.
  • EMAIL_ADDRESS, ASSIGNED_TO_USER_ID, COST_CENTER, CHARGE_TO_COST_CENTER, COMPENSATION_CURRENCY_CODE — resource and compensation details.
  • SALES_TAX_GEOCODE, SALES_TAX_INSIDE_CITY_LIMITS — tax jurisdiction attributes used in tax determination.
  • COMMISSIONABLE_FLAG, TYPE, PERSON_ID, SOURCE_ID — categorization and commission eligibility indicators.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments.

Common Use Cases and Queries

Typical scenarios include validating salesperson assignments on sales orders and invoices, building commission and credit reports, and extracting salesperson data for data warehousing. A common query retrieves active salespersons for the current operating unit:

  • SELECT salesrep_id, name, salesrep_number, org_id, status
  • FROM ra_salesreps
  • WHERE status = 'A'
  • AND sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate);

Other queries join SALESREP_ID to transaction tables such as RA_CUSTOMER_TRX or OE_ORDER_HEADERS to summarize sales by salesperson, or select EMAIL_ADDRESS and ASSIGNED_TO_USER_ID for notification integrations. Because the view is a compatibility layer over RA_SALESREPS_ALL, Oracle recommends that new development query RA_SALESREPS_ALL directly when multi-org awareness is required, reserving RA_SALESREPS for backward-compatible access.