Results for “assign_to_person_id”

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

Overview

The AS_SALES_LEADS_LOG table resides in the OSM schema and belongs to the AS – Sales Foundation product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold the opportunity change history for sales leads. Whereas AS_SALES_LEADS stores the current state of each opportunity, AS_SALES_LEADS_LOG captures the transactional trail of changes made to those opportunities over time — reassignments, status transitions, rank modifications, qualification decisions, and rejections.

Heuristic Data Vault classification mined from the foreign key structure indicates a satellite-leaning pattern. In Data Vault modeling terms, this suggests AS_SALES_LEADS_LOG behaves as a satellite attached to a hub (AS_SALES_LEADS via SALES_LEAD_ID), recording descriptive, time-variant change attributes about the parent opportunity rather than acting as an independent hub or a many-to-many link.

Key Information Stored

The table is documented with 22 columns in the ETRM 12.2.2 physical schema. The most operationally significant columns include:

• LOG_ID — the surrogate primary key, enforced by AS_SALES_LEADS_LOG_PK and reinforced by the unique index AS_SALES_LEADS_LOG_U1. Because a separate unique index exists on the same column, the business-key candidate is also LOG_ID; the table does not expose a natural composite business key.
• SALES_LEAD_ID — foreign key to AS_SALES_LEADS, identifying the opportunity whose history row is being recorded.
• STATUS_CODE — the lifecycle status captured at the time of the change.
• ASSIGN_TO_PERSON_ID and ASSIGN_TO_SALESFORCE_ID — the resource to whom the opportunity was assigned.
• ASSIGN_SALES_GROUP_ID — the sales group receiving the assignment.
• LEAD_RANK_ID and MANUAL_RANK_FLAG — ranking outcome and whether the rank was applied manually.
• QUALIFIED_FLAG — indicates whether the opportunity was qualified as part of this change.
• REJECT_REASON_CODE — reason captured when an opportunity was rejected.
• CATEGORY — classification of the change record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting Multi-Org / security-group access control.
• OBJECT_VERSION_NUMBER — optimistic locking token used by the OAF/ADF framework.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus the concurrent program context: REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The most frequent scenario is reconstructing an opportunity's assignment and status timeline for audit or sales-performance reporting.

• Opportunity change history: SELECT l.log_id, l.sales_lead_id, l.status_code, l.assign_to_person_id, l.creation_date FROM as_sales_leads_log l WHERE l.sales_lead_id = :p_lead_id ORDER BY l.creation_date;
• Reassignment audit: joining to AS_SALES_LEADS to compare current owner against historical owners recorded in the log.
• Rejection analysis: grouping by REJECT_REASON_CODE to identify systemic disqualification trends.
• Concurrent-program lineage: filtering on REQUEST_ID or PROGRAM_ID to trace which batch process generated specific history rows.
• Security-scoped extracts: constraining results by SECURITY_GROUP_ID for multi-org reporting.

Related Objects

• AS_SALES_LEADS — joined via AS_SALES_LEADS_LOG.SALES_LEAD_ID = AS_SALES_LEADS.SALES_LEAD_ID; the primary parent of every history row.
• FND_SECURITY_GROUPS — joined via AS_SALES_LEADS_LOG.SECURITY_GROUP_ID, governing row-level access.
• PER_ALL_PEOPLE_F — resolves ASSIGN_TO_PERSON_ID to a named resource.
• AS_SALES_LEAD_RANKS / rank lookup — resolves LEAD_RANK_ID to a descriptive rank value.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_CONCURRENT_REQUESTS — correlates REQUEST_ID with the originating concurrent program.

Because AS_SALES_LEADS_LOG depends on AS_SALES_LEADS, integrity is maintained through the documented foreign key; no child tables reference AS_SALES_LEADS_LOG itself.