Results for “competitor_code”

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

Overview

The AS_LEAD_COMPETITORS table is a Sales Foundation (AS) object in Oracle E-Business Suite that records the competitors associated with sales opportunities (leads). Each row identifies a specific competitor engaged in a given sales opportunity, capturing comparative positioning data such as the competitor's rank and the win/loss outcome. The table is owned by the OSM schema and is classified as VALID in the ETRM reference for both 12.1.1 and 12.2.2 releases.

The documented physical schema comprises 37 columns, and the table participates in Sales Foundation's lead and opportunity management workflow by linking lead records to party records representing competing organizations. From a dimensional modeling perspective, the ETRM heuristic classification places this table as satellite-leaning. This suggests that AS_LEAD_COMPETITORS is best modeled as a satellite attached to a lead hub, because it describes attributes of a sales opportunity over time rather than serving as an independent business entity hub or as a pure many-to-many link between two hubs.

Key Information Stored

The primary identifier is LEAD_COMPETITOR_ID, which serves as the surrogate primary key (AS_LEAD_COMPETITORS_PK) and is also the sole documented business-key candidate via the unique index AS_LEAD_COMPETITORS_U1. The most significant columns include:

• LEAD_COMPETITOR_ID — Surrogate primary key uniquely identifying each competitor-to-lead association.
• LEAD_ID — Foreign key to AS_LEADS_ALL, identifying the sales opportunity with which the competitor is associated.
• COMPETITOR_ID — Foreign key to HZ_PARTIES, identifying the competing party as a registered Trading Community Architecture entity.
• COMPETITOR_CODE / COMPETITOR — Denormalized code and descriptive name used for display and reporting without forcing a join to HZ_PARTIES.
• COMPETITOR_RANK — Relative ranking or priority of the competitor within the opportunity.
• WIN_LOSS_STATUS — Outcome indicator reflecting whether the opportunity was won or lost against this competitor.
• RELATIONSHIP_PARTY_ID — Party relationship reference supporting relationship modeling for the competitor entry.
• PRODUCTS — Free-text or descriptive field noting products contested by the competitor.
• COMMENTS — Analyst notes on the competitive situation.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS supporting multi-org data security.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Standard Oracle descriptive flexfield (DFF) columns for customer-extensible data.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include competitive analysis for pipeline opportunities, win/loss reporting by competitor, and product-level competitive breakdowns. A common query joins competitors to leads and parties:

• List competitors for a lead: SELECT c.competitor, c.competitor_rank, c.win_loss_status FROM as_lead_competitors c WHERE c.lead_id = :lead_id ORDER BY c.competitor_rank;
• Win/loss by competitor: SELECT competitor, win_loss_status, COUNT(*) FROM as_lead_competitors GROUP BY competitor, win_loss_status;
• Resolve competitor parties: SELECT c.competitor_id, p.party_name FROM as_lead_competitors c, hz_parties p WHERE c.competitor_id = p.party_id;

Related Objects

• AS_LEADS_ALL — parent lead/opportunity header; joined on LEAD_ID.
• HZ_PARTIES — TCA party master; joined on COMPETITOR_ID.
• AS_LEAD_COMPETITOR_PRODS — child table holding competitor product lines; joined on LEAD_COMPETITOR_ID.
• FND_SECURITY_GROUPS — security grouping; joined on SECURITY_GROUP_ID.