Search Results compensation_currency_code

Overview

The AS_RA_SALESREPS view is a Sales Foundation (AS) reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in the E-Business Suite Technical Reference Manual (ETRM) as the "View definition for RA_SALESREPS_ALL," meaning it exposes the columns of the sales representative (salesrep) entity while applying an operating-unit security predicate. Salesreps are the individuals or, in some configurations, organizations credited with sales transactions, and this view is the primary dictionary-based access path used by reports, concurrent programs, and third-party integrations that need to read salesrep records without bypassing Multi-Org (MO) access control.

The view is not a physical table; it carries no independently maintained data. All values originate from RA_SALESREPS_ALL and its underlying organization hierarchy. In ETRM, the object is listed with no documented owner and no documented referenced base objects, indicating that its definition is captured primarily as view text rather than through an object dependency registry. The view text confirms that the sole source is RA_SALESREPS_ALL, aliased RAREPS.

Underlying Base Objects

AS_RA_SALESREPS is defined over a single base table, RA_SALESREPS_ALL (part of the AS - Sales Foundation schema, historically associated with the Oracle Receivables/Order Management salesrep model). Every column in the view is a direct projection of a RA_SALESREPS_ALL column with no joins, expressions, or transformations. The only logical processing applied is the operating-unit filter in the WHERE clause:

• NVL(RAREPS.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)

This is the standard EBS Multi-Org "CLIENT_INFO" predicate. It reads the current operating unit from the session client information, converting it to a number, and matches it to ORG_ID. Rows with a NULL ORG_ID (seed or global data) resolve to -99 through the outer NVL, so they remain visible across operating units. Because the view depends entirely on RA_SALESREPS_ALL, its performance, security, and data quality characteristics are those of the base table and any indexes defined on SALESREP_ID and ORG_ID.

Key Columns

The view exposes the complete salesrep attribute set. The most operationally significant columns include:

• SALESREP_ID — Primary key of the salesrep record, referenced widely as a foreign key from transaction and commission tables.
• SALESREP_NUMBER — User-facing unique identifier for the salesrep.
• NAME — Salesrep name displayed in forms, reports, and lookups.
• STATUS and START_DATE_ACTIVE / END_DATE_ACTIVE — Lifecycle and effective-dating controls. Queries typically filter active salesreps by comparing SYSDATE against the active date range.
• COMPENSATION_CURRENCY_CODE — The currency in which the salesrep is compensated. This column is the object of the search term and is the key field for commission, quota, and compensation reporting; it must be reconciled against SET_OF_BOOKS_ID and the transaction currency when computing credits.
• SET_OF_BOOKS_ID and GL_ID_REV / GL_ID_FREIGHT / GL_ID_REC — Accounting context: the ledger and the revenue, freight, and receivables account identifiers used for salescredit accounting.
• SALES_CREDIT_TYPE_ID — Links the salesrep to a sales credit type, determining how credit is allocated (for example, quota versus non-quota salescredit).
• ASSIGNED_TO_USER_ID and PERSON_ID — Integration keys linking the salesrep to an application user and, where applicable, to a Human Resources person record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns reserved for customer-specific extensions.
• EMAIL_ADDRESS, COST_CENTER, CHARGE_TO_COST_CENTER, COMMISSIONABLE_FLAG, SALESFORCE_ID — Supporting attributes for notification, cost allocation, compensation eligibility, and CRM synchronization.

Common Use Cases and Queries

Typical consumers include sales compensation reports, order and receivables interfaces, and reconciliation utilities. Because the view enforces operating-unit security, it is the preferred access point over RA_SALESREPS_ALL for reporting that must respect MO boundaries. A representative query retrieving active salesreps and their compensation currency is:

• SELECT salesrep_id, salesrep_number, name, compensation_currency_code, status FROM as_ra_salesreps WHERE status = 'A' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• SELECT salesrep_number, name, set_of_books_id, compensation_currency_code FROM as_ra_salesreps WHERE org_id IS NOT NULL ORDER BY name;

Practitioners should note that the view has no documented index of its own and relies on RA_SALESREPS_ALL indexes; large-volume extracts should therefore restrict on salesrep_id, salesrep_number, or status and avoid unbounded attribute-flexfield predicates. Where cross-operating-unit visibility is required, queries must run under the appropriate MO initialization or use the base table with explicit ORG_ID criteria.