Results for “ra_salesreps”

2 results




Overview
Explore in AI Chat

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

Overview

ASO_I_RA_SALESREPS_V is a public Oracle E-Business Suite view owned by the APPS schema and registered as a valid object under the ASO (Order Capture) product family. It exposes sales representative information sourced from the Receivables salesperson repository for use within the ASO order capture and order management flows. Architecturally, the view functions as a thin projection layer: rather than storing data, it inherits all rows from its single documented base object and projects a fixed column list consisting of ORG_ID, SALESREP_ID, SALES_CREDIT_TYPE_ID, NAME, START_DATE_ACTIVE, END_DATE_ACTIVE, SALESREP_NUMBER, PERSON_ID, and TYPE.

The "I" convention in the name and the ASO module prefix indicate the view was designed for internal consumption by ASO application logic, typically to resolve salesperson identifiers, names, and credit types when building order and quote data. Because it is delivered in the APPS schema, the view is governed by standard Oracle EBS security conventions: access is normally granted through application responsibilities rather than direct database privileges. The view remains valid in both Oracle EBS 12.1.1 and 12.2.2, making it a stable reference point across the two release lines for reporting and integration work that touches the "ra_salesreps" terminology.

Underlying Base Objects

Per the documented ETRM metadata, ASO_I_RA_SALESREPS_V is defined over exactly one referenced base object: RA_SALESREPS, which is itself a view rather than a physical table. This relationship is significant. RA_SALESREPS sits in the Receivables schema family and presents salesperson records drawn from the underlying human resources and receivables tables. Because ASO_I_RA_SALESREPS_V selects directly from RA_SALESREPS without joins, filters, or transformations beyond column projection, the two objects are row-for-row and value-for-value equivalent. Any DML or visibility restriction that applies to RA_SALESREPS propagates unchanged to ASO_I_RA_SALESREPS_V.

This single-source design means the ASO view carries no independent business logic. Its purpose is interface alignment: it provides ASO components with a salesperson view expressed in the column naming and ordering expected by order capture, while delegating all data sourcing to the Receivables layer. Consequently, an administrator auditing the view needs only to audit RA_SALESREPS and its downstream dependencies.

Key Columns

  • ORG_ID: Operating unit identifier, enabling multi-org filtering. Queries should generally restrict on this column to respect operating unit security.
  • SALESREP_ID: Primary identifier for the salesperson record, referenced by order, quote, and sales credit entities.
  • SALES_CREDIT_TYPE_ID: Identifier linking the salesperson to a sales credit type, used to categorize revenue credit allocation.
  • NAME: Display name of the salesperson as maintained in the Receivables salesperson definition.
  • START_DATE_ACTIVE / END_DATE_ACTIVE: Effective dating for the salesperson record. A NULL end date conventionally denotes an open-ended, currently active record; queries requiring only current salespeople should test both columns against the current date.
  • SALESREP_NUMBER: The user-visible salesperson number, frequently used in reporting and data load cross-referencing.
  • PERSON_ID: The underlying HR person identifier, allowing correlation with human resources and other person-centric data sets.
  • TYPE: Classifies the salesperson record type within the Receivables model.

Common Use Cases and Queries

Typical scenarios include validating salesperson references during order import, populating LOV-style lookups for order entry integrations, and reconciling sales credit assignments in reports. The effective date columns make the view suitable for point-in-time analysis of sales force composition.

A basic active-salesperson query for a given operating unit:

  • SELECT salesrep_id, salesrep_number, name, person_id
  • FROM apps.aso_i_ra_salesreps_v
  • WHERE org_id = :p_org_id
  • AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

To correlate salespersons with sales credit types:

  • SELECT salesrep_number, name, sales_credit_type_id, type
  • FROM apps.aso_i_ra_salesreps_v
  • WHERE org_id = :p_org_id
  • ORDER BY name;

Because the view is unfiltered and unrestricted at the database level, organizations should always apply ORG_ID and effective-date predicates in application queries to avoid cross-operating-unit leakage and stale records.