Search Results compensation_currency_code

Overview

The ICX_SALESREP_PERS_INFO_V view is a sales representative information view registered under the ICX product family (Oracle iProcurement) in Oracle E-Business Suite. Its documented description is "Sales Representative View," indicating that it exposes personal and organizational attributes of sales representatives defined in the Oracle Receivables and Order Management schemas. The view is intended to present a denormalized, report-friendly projection of the sales representative record, combining the representative's identity, credit type, status, organization, contact information, cost center, and compensation currency into a single queryable object. Users typically discover this view when searching on the SALES_REP_ID column, which is the primary identifier for a sales representative and the principal join key to related transaction and assignment tables.

The view is not implemented in every database. The supplied ETRM metadata explicitly records "Not implemented in this database," which means the object may exist only when the relevant ICX and Receivables functionality has been enabled or patched. This is an important caveat for any report or integration that references the view: existence and population depend on the installation's configuration.

Underlying Base Objects

The view is defined over two documented base objects, joined on the sales credit type identifier:

• RA_SALESREPS (aliased SP) — the master sales representative table in Oracle Receivables, supplying representative identity, status, organization, contact, and compensation attributes.
• SO_SALES_CREDIT_TYPES (aliased SCT) — the sales credit type reference table in Oracle Order Management, supplying the credit type name.

The join condition is SCT.SALES_CREDIT_TYPE_ID = SP.SALES_CREDIT_TYPE_ID. One column, SALESREP_STATUS, is not taken directly from a base table but is derived through the function ICX_CUSTOMER_PANEL.GET_AR_CODE('CODE_STATUS', SP.STATUS), which translates the stored status code into a display value using the iProcurement customer panel lookup logic. No additional referenced base objects are documented in the ETRM metadata.

Key Columns

• SALES_REP_ID — primary identifier of the sales representative; the join key most commonly searched for. Maps to RA_SALESREPS.SALESREP_ID.
• REP_NAME — the representative's name (RA_SALESREPS.NAME).
• SALES_CREDIT_TYPE — descriptive name of the credit type, sourced from SO_SALES_CREDIT_TYPES.NAME.
• SALES_CREDIT_TYPE_ID — foreign key to the sales credit type; the join column between the two base objects.
• SALESREP_STATUS — decoded status value produced by ICX_CUSTOMER_PANEL.GET_AR_CODE for the 'CODE_STATUS' lookup.
• ORG_ID — operating unit identifier, supporting multi-org filtering.
• EMAIL_ADDRESS — the representative's electronic mail address.
• ASSIGNED_TO_USER_ID — the application user account linked to the representative, useful for responsibility or self-service routing.
• COST_CENTER — the cost center attributed to the representative.
• COMPENSATION_CURRENCY_CODE — the currency in which the representative is compensated.

Common Use Cases and Queries

Typical uses include listing active representatives by operating unit, resolving a SALES_REP_ID to a name and email for notifications or reporting, and joining to sales order or receivables data to attribute transactions to representatives. A representative lookup might be written as:

• SELECT sales_rep_id, rep_name, email_address FROM icx_salesrep_pers_info_v WHERE org_id = :p_org_id;
• SELECT sales_rep_id, rep_name, sales_credit_type FROM icx_salesrep_pers_info_v WHERE sales_rep_id = :p_sales_rep_id;

Because the view is documented as not implemented in the reference database, deployments should verify object existence before relying on it in concurrent programs, OAF pages, or BI Publisher data models, and provide a fallback query against RA_SALESREPS where the view is unavailable.