Search Results ra_salesreps




Overview
Explore in AI Chat

Overview

SO_SALESPERSONS_ACTIVE_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Order Entry (OE) product family and exposes a filtered list of salespersons that are currently eligible for assignment to sales orders, quotations, and related order-entry transactions. Because it presents only active, non-system salespersons, the view is commonly used in value-set–backed list of values (LOVs), order-entry flexfields, and downstream reporting where assigning an inactive or reserved salesperson would be inappropriate.

The view is registered in the E-Business Suite Tables and Views Repository (ETRM) with a status of VALID. Its publication is particularly relevant to users who search on the term ra_salesreps, since the view is a curated projection over that base object and provides a safer, business-filtered alternative to querying RA_SALESREPS directly.

Underlying Base Objects

According to the documented metadata, SO_SALESPERSONS_ACTIVE_V is defined solely over the base object RA_SALESREPS (itself documented as a VIEW in the ETRM repository). The view text is:

The relationship to RA_SALESREPS is therefore a one-to-one row projection with a WHERE predicate. RA_SALESREPS is the canonical receivables/order-entry salesperson repository; SO_SALESPERSONS_ACTIVE_V narrows it to records that are not the seeded system identifiers and that fall within their active date window.

Key Columns

  • SALESPERSON — the salesperson name, exposed from the NAME column of RA_SALESREPS. This is the descriptive value typically displayed in LOVs and reports.
  • SALESREP_ID — the unique numeric identifier of the salesperson. This is the primary key value used in foreign-key relationships on order headers, lines, and other OE/AR tables.
  • SALESREP_NUMBER — the user-facing salesperson number, useful for cross-referencing against external systems and printed documents.

Notably, the view deliberately omits date and status columns; it only surfaces the attributes required to identify and display an active salesperson.

Common Use Cases and Queries

The principal use of this view is populating salesperson LOVs on order-entry forms and validation against the underlying salesrep table. A typical lookup for a specific salesperson is:

  • SELECT salesperson, salesrep_number FROM so_salespersons_active_v WHERE salesrep_id = :p_salesrep_id;
  • SELECT salesrep_id, salesperson FROM so_salespersons_active_v WHERE UPPER(salesperson) LIKE UPPER(:search_text || '%') ORDER BY salesperson;

For reporting, the view is frequently joined to order headers to show selling parties on booked orders:

  • SELECT h.order_number, v.salesperson FROM oe_order_headers_all h, so_salespersons_active_v v WHERE h.salesrep_id = v.salesrep_id;

Because the view applies SYSDATE-based filtering, results vary with the effective start and end dates captured in RA_SALESREPS; consumers requiring historical salespersons should query RA_SALESREPS directly instead of this active-only view.