Results for “as_salesforce”

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

Overview

AS_SALESFORCE is a table owned by the OSM schema within the AS - Sales Foundation product family of Oracle E-Business Suite Release 12.1.1 and 12.2.2. The ETRM metadata classifies the object as table type TABLE with a VALID status, while its formal description states that it is obsolete and defines the salesforce. The obsolete designation reflects the historical role this table played in early Oracle Sales and Territory Management releases, where a "salesforce" represented the assignment of a selling party — either an internal employee (sales representative) or an external partner — to a sales group and geography. Although subsequent releases reorganized much of the salesforce model into territory and resource structures, AS_SALESFORCE remains present in the physical schema with 31 documented columns, and a large set of downstream tables still carry a SALESFORCE_ID foreign key column, indicating ongoing referential dependency.

A heuristic Data Vault classification derived from the foreign key structure suggests a satellite-leaning model. The table carries a single-attribute surrogate key (SALESFORCE_ID) while also holding descriptive and relationship attributes such as TYPE, STATUS_CODE, EMPLOYEE_PERSON_ID, SALES_GROUP_ID, and partner identifiers referencing RA_CUSTOMERS, RA_ADDRESSES_ALL, and AS_SALES_GROUPS. This pattern — a hub-like identifier surrounded by a compact set of descriptive and foreign-key attributes — is consistent with a satellite attached to the salesforce business key.

Key Information Stored

AS_SALESFORCE is defined by the primary key constraint AS_SALESFORCE_PK on SALESFORCE_ID, which is the surrogate identifier used by all dependent tables. Two additional unique indexes act as business-key candidates: AS_SALESFORCE_U2 on (EMPLOYEE_PERSON_ID, PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID) and AS_SALESFORCE_U3 on (PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, EMPLOYEE_PERSON_ID). These enforce the rule that a given employee or partner party, at a given address, resolves to one salesforce record.

• SALESFORCE_ID — surrogate primary key carried into nearly every downstream sales, forecast, and credit table.
• EMPLOYEE_PERSON_ID — identifies the internal employee (sales representative) associated with the salesforce entry.
• PARTNER_CUSTOMER_ID — external partner party, validated against RA_CUSTOMERS.
• PARTNER_ADDRESS_ID — partner address, validated against RA_ADDRESSES_ALL.
• PARTNER_CONTACT_ID — partner contact reference.
• SALES_GROUP_ID — the sales group to which the salesforce belongs, referencing AS_SALES_GROUPS.
• TYPE — classifies the salesforce record (for example employee versus partner channel).
• STATUS_CODE — lifecycle status controlling whether the salesforce is active for assignment.
• PALM_ID — legacy identifier retained for backward compatibility.
• CLIENT_NUMBER — client or organization identifier used in multi-organization scenarios.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns for extensible, customer-defined data.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track who created and modified each row.

Common Use Cases and Queries

Because SALESFORCE_ID is propagated widely, the most frequent access pattern is resolving a salesforce identifier to its owning employee, partner, or sales group. A typical reporting join retrieves the salesforce context for a forecast or opportunity record:

SELECT s.SALESFORCE_ID, s.TYPE, s.STATUS_CODE, s.EMPLOYEE_PERSON_ID, s.SALES_GROUP_ID
FROM AS_SALESFORCE s
WHERE s.STATUS_CODE = 'ACTIVE';

Analysts often traverse from transactional tables back to the salesforce to attribute revenue, forecast, or credit data to the responsible selling party:

SELECT f.SALESFORCE_ID, s.EMPLOYEE_PERSON_ID, f.FORECAST_AMOUNT
FROM AS_FORECASTS f, AS_SALESFORCE s
WHERE f.SALESFORCE_ID = s.SALESFORCE_ID;

Partner-channel reporting uses the partner columns to distinguish external selling parties from internal representatives, and the unique indexes support de-duplication and validation during data migration. Territory transfer analysis depends on the AS_CHANGED_TERRITORIES_ALL.TRANSFER_TO_SALESFORCE_ID reference to track reassignment of selling responsibility.

Related Objects

AS_SALESFORCE participates in a dense referential network. The most significant relationships include:

• AS_SALES_GROUPS — joined on AS_SALESFORCE.SALES_GROUP_ID; defines the grouping of salesforce members.
• RA_CUSTOMERS — joined on AS_SALESFORCE.PARTNER_CUSTOMER_ID; identifies external partner parties.
• RA_ADDRESSES_ALL — joined on AS_SALESFORCE.PARTNER_ADDRESS_ID; supplies partner address detail.
• AS_TERRITORIES_ALL — references AS_SALESFORCE via SALESFORCE_ID; links salesforces to territory definitions.
• RA_SALESREPS_ALL — references AS_SALESFORCE via SALESFORCE_ID; connects salesforce records to sales representatives.
• AS_CHANGED_TERRITORIES_ALL — references AS_SALESFORCE via TRANSFER_TO_SALESFORCE_ID; records territory reassignment targets.
• AS_FORECASTS and AS_FORECAST_WORKSHEETS — reference SALESFORCE_ID to attribute forecast data to a selling party.
• AS_SALES_CREDITS_LOG, AS_SALES_CREDIT_ADJS, and AS_PARTNER_ACCESSES — reference SALESFORCE_ID for credit allocation and partner access control.
• AS_OPP_WORKSHEET_LINES and AS_PROD_WORKSHEET_LINES — reference SALESFORCE_ID within opportunity and product worksheet processing.
• Materialized views such as ASF_WIN_LOSS_MV, ASF_OPP_PRD_MV, and ASF_SC_BIN_FRCST_MV — carry SALESFORCE_ID for pre-aggregated sales reporting.