Results for “as_oth_salesreps_v”

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

Overview

The AS_OTH_SALESREPS_V view belongs to the AS (Sales Foundation) product family in Oracle E-Business Suite and is documented as the "Salesperson Definition View for Others type salesreps." Its purpose is to present salesperson records whose SALESFORCE_TYPE classification is 'OTHERS' — that is, salespersons defined outside the standard internal employee model, such as external representatives, agents, or non-employee resources participating in the sales credit structure.

The view consolidates salesperson attributes from the base salesforce repository with descriptive lookups, period status information, assigned user context, and sales credit type definitions. This consolidation makes it suitable for reporting, integration extracts, and validation queries where consumers require a denormalized, ready-to-read representation of "others" salespersons rather than joining the underlying tables themselves. Because the view embeds organization-based security through the USERENV('CLIENT_INFO') predicate, results are automatically restricted to the operating unit context established by the session.

Underlying Base Objects

ETRM's documented metadata does not enumerate base objects explicitly, but the view text identifies the following tables and views in its FROM clause:

• AS_SALESFORCE (aliased ASF) — holds the salesforce definition, including type, status code, and the descriptive flexfield attribute columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15).
• RA_SALESREPS_ALL (aliased RA) — the multi-org salesperson repository providing identity, dates, GL accounts, sales credit type, and processing period references.
• SO_SALES_CREDIT_TYPES_115 (aliased ST) — supplies the sales credit type name.
• AS_LOOKUPS (aliased ASL) — supplies the meaning for the SALESFORCE_TYPE lookup code.
• CN_PERIOD_STATUSES (aliased PS and PE) — resolves starting and ending processing period IDs to period names.
• FND_USER (aliased U) — resolves the assigned user ID to a user name.

All of these joins — except the mandatory RA_SALESFORCE_ID = ASF.SALESFORCE_ID relationship — are outer joins, meaning the view returns the complete population of OTHERS salespersons regardless of whether a lookup, user, or period match exists. The ASF.TYPE = 'OTHERS' predicate anchors the view's filtering, while ASF.TYPE = ASL.LOOKUP_CODE combined with ASL.LOOKUP_TYPE = 'SALESFORCE_TYPE' is what connects the salesforce_type search term to this object.

Key Columns

The view exposes a broad set of columns spanning salesperson identity, financial configuration, and administrative metadata:

• SALESREP_ID, SALESREP_NUMBER, NAME, PERSON_ID, EMAIL_ADDRESS — core salesperson identification.
• TYPE / lookup NAME (from ASL.MEANING) — the salesforce type, which for this view resolves to the "Others" meaning of the SALESFORCE_TYPE lookup.
• STATUS, STATUS_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE — activation and lifecycle state.
• SALES_CREDIT_TYPE_ID and ST.NAME — the credit type assigned to the salesperson.
• GL_ID_REV, GL_ID_FREIGHT, GL_ID_REC, SET_OF_BOOKS_ID, COST_CENTER, CHARGE_TO_COST_CENTER — accounting and costing configuration.
• START_PROCESSING_PERIOD_ID, END_PROCESSING_PERIOD_ID (with PS.PERIOD_NAME and PE.PERIOD_NAME) — processing period boundaries.
• ORG_ID — operating unit, filtered by the client-info security predicate.
• ASSIGNED_TO_USER_ID and U.USER_NAME — the user linked to the salesperson.
• SALESFORCE_ID, COMMISSIONABLE_FLAG, COMPENSATION_CURRENCY_CODE, SALES_TAX_GEOCODE, SALES_TAX_INSIDE_CITY_LIMITS — additional salesforce and tax attributes.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments.
• Standard audit columns: ROWID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, WH_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include validating externally defined salespersons before assignment to orders or compensation plans, producing extracts for downstream commission systems, and reporting on active "others" representatives by operating unit. A representative query:

• SELECT salesrep_id, salesrep_number, name, status, status_code FROM as_oth_salesreps_v WHERE org_id = :p_org_id AND status_code = 'A' ORDER BY name;
• SELECT name, email_address, sales_credit_type_id, ps.period_name AS start_period, pe.period_name AS end_period FROM as_oth_salesreps_v WHERE sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate+1);
• SELECT salesrep_number, name, attribute1, attribute2 FROM as_oth_salesreps_v WHERE attribute_category = 'XX_CUSTOM';

Because the view enforces client-info organization security, reports should always be executed within the correct operating unit responsibility context. Note that ETRM records this view as "Not implemented in this database," indicating it may be a legacy or non-deployed object in some environments; consumers should confirm availability before relying on it in custom code.