Search Results as_salesforce




Overview
Explore in AI Chat

Overview

The AS_SALESFORCE table is a core data object within the Oracle E-Business Suite (EBS) Sales Foundation (AS) module. It serves as the master definition table for a salesforce, which represents an individual salesperson or a sales team responsible for customer accounts and opportunities. Its primary role is to establish the central record for a sales resource, linking that resource to critical transactional and master data across the application, including customers, addresses, sales groups, and territories. Notably, the official ETRM documentation explicitly marks this table as "Obsolete," indicating it is a legacy structure that may have been superseded by other data models in later implementations or patches, though it remains present and referenced within the schemas of versions 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on a unique identifier for each salesforce record. The primary key is the SALESFORCE_ID column. Key relational columns define the salesforce's associations within the EBS ecosystem. The PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, and PARTNER_CONTACT_ID columns create foreign key relationships to the RA_CUSTOMERS and RA_ADDRESSES_ALL tables, linking the sales resource to a specific customer and location record, which is typical for partner or internal sales models. The SALES_GROUP_ID column links the salesforce to a defined team or hierarchy within the AS_SALES_GROUPS table. While the specific descriptive columns (like name, status, or effective dates) are not detailed in the provided metadata, they would typically be present to fully define the salesforce entity.

Common Use Cases and Queries

Despite its obsolete status, the table remains integral for historical reporting and understanding sales force assignments. A common use case is generating a list of all active salesforces with their associated customer and group information for territory analysis. Sample SQL to retrieve this core information would involve joining the related master tables:

  • SELECT sf.SALESFORCE_ID, c.CUSTOMER_NAME, a.ADDRESS1, sg.NAME GROUP_NAME FROM OSM.AS_SALESFORCE sf, RA_CUSTOMERS c, RA_ADDRESSES_ALL a, AS_SALES_GROUPS sg WHERE sf.PARTNER_CUSTOMER_ID = c.CUSTOMER_ID(+) AND sf.PARTNER_ADDRESS_ID = a.ADDRESS_ID(+) AND sf.SALES_GROUP_ID = sg.SALES_GROUP_ID(+);

Another critical reporting use case involves analyzing territory changes by querying the relationship between AS_SALESFORCE and the AS_CHANGED_TERRITORIES_ALL history table.

Related Objects

The AS_SALESFORCE table is a nexus for several key relationships, as evidenced by its foreign key constraints. It is a parent table to RA_SALESREPS_ALL, which ties Oracle Receivables sales representatives to this salesforce definition. It is also linked to AS_TERRITORIES_ALL, defining which territory the salesforce belongs to, and to AS_CHANGED_TERRITORIES_ALL for tracking reassignment history. As a child table, it references RA_CUSTOMERS, RA_ADDRESSES_ALL, and AS_SALES_GROUPS to pull in partner and organizational data. Developers and DBAs interacting with sales force data, territory management, or the sales representative setup in Receivables must account for these relationships, even when considering migration paths away from this obsolete table.