Search Results salesperson_name




Overview
Explore in AI Chat

Overview

ARFV_SALES_CREDITS is an APPS-owned view in the Oracle E-Business Suite Receivables (AR) module that presents sales credit information associated with transaction lines. In both Oracle EBS 12.1.1 and 12.2.2, the view is documented in ETRM as VALID and is defined with a WITH READ ONLY clause, meaning it is intended strictly for querying and reporting rather than for DML operations. Its primary purpose is to expose the relationship between a Receivables transaction line and the salesperson credited against it, resolving foreign-key references so that consumers receive human-readable values instead of internal identifiers.

The view carries a marker column ("_DF:") and a derived column ("_DF:AR:RA_CUST_TRX_LINE_SALESREPS:RCT") that reference the underlying base table RA_CUST_TRX_LINE_SALESREPS. These markers are typical of Oracle's descriptive-flexfield style resolution columns and indicate the lineage of the record. For users searching on "salesperson_name," this view is a convenient starting point because it surfaces SALESPERSON_NAME directly, along with SALESPERSON_NUMBER, without requiring the caller to join RA_SALESREPS manually.

Underlying Base Objects

The view is defined over five base objects referenced in the ETRM metadata: RA_CUST_TRX_LINE_SALESREPS, HR_ALL_ORGANIZATION_UNITS, RA_CUSTOMER_TRX_LINES, RA_SALESREPS (itself a view), and RA_CUSTOMER_TRX. The central driving table is RA_CUST_TRX_LINE_SALESREPS (aliased RCT), which holds one row per sales credit assignment per transaction line.

The joins are largely outer joins. RA_CUST_TRX_LINE_SALESREPS.ORG_ID is joined to HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID with the (+) operator, so the operating unit name (AOU.NAME) is returned where an organization unit match exists. The transaction header join to RA_CUSTOMER_TRX (CT) is a mandatory equi-join on CUSTOMER_TRX_ID, while the line join to RA_CUSTOMER_TRX_LINES (CTL) uses an outer join on CUSTOMER_TRX_LINE_ID, allowing sales credits at the header level to still appear. The salesperson join to RA_SALESREPS (RS) enforces matching by SALESREP_ID and, where both ORG_IDs are populated, by ORG_ID as well; a NULL SALESPERSON_NAME falls out only when SALESREP_ID is null. The RA_SALESREPS object is itself a view, so the salesperson attributes are resolved one level deeper.

Key Columns

  • SALES_CREDIT_ID — Unique identifier for the sales credit line, mapped from CUST_TRX_LINE_SALESREP_ID.
  • SALESPERSON_NAME — The name of the credited salesperson, sourced from RA_SALESREPS.NAME; this is the column most commonly searched.
  • SALESPERSON_NUMBER — The salesperson's reference number from RA_SALESREPS.SALESREP_NUMBER.
  • SALESREP_ID — Internal identifier linking back to RA_SALESREPS.
  • OPERATING_UNIT — Organization unit name resolved via HR_ALL_ORGANIZATION_UNITS.NAME.
  • TRANSACTION_NUMBER / TRANSACTION_LINE_NUMBER — The customer transaction number and its line number.
  • SALES_ORDER_NUMBER — Sales order reference from the transaction line.
  • CUSTOMER_TRX_ID / CUSTOMER_TRX_LINE_ID — Foreign keys to the transaction header and line.
  • ORG_ID — Operating unit identifier for multi-org filtering.
  • WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, inherited from the base table.

Common Use Cases and Queries

Typical usage includes sales-credit reporting, commission reconciliation, and multi-org analysis. The following query lists credits for a given salesperson:

SELECT salesperson_name, salesperson_number, transaction_number,
       transaction_line_number, operating_unit, sales_credit_id
FROM   apps.arfv_sales_credits
WHERE  salesperson_name = 'SMITH, JOHN';

To aggregate credits by salesperson and operating unit:

SELECT salesperson_name, operating_unit, COUNT(*) credit_count
FROM   apps.arfv_sales_credits
GROUP  BY salesperson_name, operating_unit
ORDER  BY salesperson_name;

Because ORG_ID is exposed, the view supports multi-org reporting when combined with MO_GLOBAL or ORG_ID predicates. Given the WITH READ ONLY definition, all access should be limited to SELECT statements.