Results for “sales_group”

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

Overview

AS_PARTNER_ACCESSES is a Sales Foundation (AS) table that resides in the OSM schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores sales representative information associated with a lead in a partner's OSO (Oracle Sales Online) database. In practice, this table acts as the intersection between leads captured from partner channels and the internal sales force records that support telemarketing, campaign follow-up, and lead qualification workflows. The table is classified as VALID and is part of the documented physical schema in ETRM 12.2.2, comprising sixteen columns.

From a modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests that, contrary to a strictly normalized hub-link-satellite pattern, AS_PARTNER_ACCESSES is best treated as a denormalized entity carrying both identifying keys and descriptive attributes in a single structure, rather than being decomposed into separate hub and satellite objects.

Key Information Stored

The table is anchored by its surrogate primary key, PARTNER_ACCESS_ID, which uniquely identifies each partner access record. Several business-key candidates and foreign-key references provide context and linkage:

• PARTNER_ACCESS_ID — Surrogate primary key for the table; also appears as a foreign key to PV_PARTNER_ACCESSES, indicating a relationship between the partner access definitions in AS and the corresponding entries in the PV (Partner) schema.
• LEAD_ID — Foreign key to AS_LEADS_ALL; identifies the specific lead to which the sales rep information pertains.
• SALESFORCE_ID — Foreign key to AS_SALESFORCE; identifies the sales representative or sales force member assigned to the lead.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; controls row-level security and visibility of the record across operating units or responsibility boundaries.
• LAST_NAME, FIRST_NAME, NAME — Descriptive identity attributes of the sales representative associated with the lead.
• TITLE — Job title or role of the sales representative.
• EMAIL, PHONE_NUMBER — Contact details for the associated sales representative.
• SALES_GROUP — The sales group or team to which the representative belongs.
• STATUS — Lifecycle or activity state of the partner access record.
• CREATION_DATE, CREATED_BY_USER_NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY_USER_NAME — Standard audit columns capturing who created or last modified the record and when, using user-name rather than numeric user-id references.

Common Use Cases and Queries

Typical usage centers on lead-to-sales-rep assignment reporting, partner lead dashboards, and contact enrichment for telemarketing campaigns. A common reporting pattern joins AS_PARTNER_ACCESSES to AS_LEADS_ALL and AS_SALESFORCE to resolve lead context and sales rep identity:

• Assigned reps per lead: SELECT l.LEAD_ID, p.LAST_NAME, p.FIRST_NAME, p.EMAIL FROM AS_PARTNER_ACCESSES p, AS_LEADS_ALL l WHERE p.LEAD_ID = l.LEAD_ID AND p.STATUS = 'ACTIVE';
• Partner access parity check: Join to PV_PARTNER_ACCESSES on PARTNER_ACCESS_ID to validate that each AS record has a corresponding PV record.
• Security-filtered extraction: Include SECURITY_GROUP_ID predicates (via FND_SECURITY_GROUPS) so reports respect the responsibility-level access rules.

Related Objects

The following objects are most significant based on the documented foreign-key relationships:

• AS_LEADS_ALL — Parent of LEAD_ID; provides lead master data.
• AS_SALESFORCE — Parent of SALESFORCE_ID; supplies sales force/representative definitions.
• PV_PARTNER_ACCESSES — Referenced through PARTNER_ACCESS_ID, binding AS partner access records to the PV-level partner access definitions.
• FND_SECURITY_GROUPS — Parent of SECURITY_GROUP_ID; governs row-level security.