Search Results as_todo_lists_n4

Overview

OSM.AS_TODO_LISTS_ALL is a transactional table in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment that stores to-do list entries, commonly referred to as activities or tasks, associated with the Oracle Sales and Marketing (OSM) application family. The table resides in the OSM schema, is registered under FND Design Data as AS.AS_TODO_LISTS_ALL, and carries a status of VALID. Physical storage is allocated in the APPS_TS_ARCHIVE tablespace with a PCT Free of 10, reflecting a design optimized for archival and low-update workloads. The table is defined in the ETRM documentation with 57 columns.

Functionally, AS_TODO_LISTS_ALL represents the central fact for sales activities, follow-ups, and scheduled tasks tied to customers, contacts, addresses, leads, and promotions. It plays a pivotal role in driving activity management, calendar integration, and pipeline follow-up reporting in Oracle Sales. From a heuristic Data Vault modeling perspective, this object is classified as standalone, though its structure suggests it functions as a hub for to-do identifiers surrounded by descriptive satellite attributes and foreign-key links to lead and sales-lead entities.

Key Information Stored

The primary key is TODO_ID, enforced by the unique index AS_TODO_LISTS_U1. This surrogate key uniquely identifies each to-do record and is the documented business-key candidate. The most significant descriptive columns include:

• DESCRIPTION (VARCHAR2 4000) — free-format text describing the to-do.
• PERSONAL_FLAG and CLOSED_FLAG — status qualifiers, both indexed for frequent filtering.
• ASSIGN_TO_PERSON_ID and ASSIGNED_BY_PERSON_ID — the resource assigned the task and the originator.
• CUSTOMER_ID, ADDRESS_ID, CONTACT_ID, PHONE_ID — the party context for the activity.
• LEAD_ID and SALES_LEAD_ID — foreign keys to lead entities, supporting sales pipeline tracking.
• TODO_DATE, TODO_START_TIME, TODO_END_TIME — scheduling information.
• ACTIVITY_TYPE, ACTIVITY_CODE, PROMOTION_ID, CATEGORY — classification and campaign linkage.
• STATUS_CODE, PRIORITY, NOTIFICATION_DAYS — workflow and escalation controls.

Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and concurrent program audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present, along with 15 ATTRIBUTE columns for flexfield-style extension.

Common Use Cases and Queries

Typical reporting scenarios include generating open activity lists per salesperson, measuring follow-up compliance against TODO_DATE, and analyzing pipeline coverage by activity type. For example, to retrieve open personal tasks for a resource:

• SELECT TODO_ID, DESCRIPTION, TODO_DATE, PRIORITY FROM OSM.AS_TODO_LISTS_ALL WHERE ASSIGN_TO_PERSON_ID = :person_id AND CLOSED_FLAG = 'N' AND PERSONAL_FLAG = 'Y' ORDER BY TODO_DATE;

Activity counts by customer and activity type can be produced by joining AS_TODO_LISTS_ALL to customer and lead tables using CUSTOMER_ID and ACTIVITY_TYPE, leveraging index AS_TODO_LISTS_N8. Overdue activity reports filter on TODO_DATE (< SYSDATE) with CLOSED_FLAG = 'N', supported by AS_TODO_LISTS_N4 and AS_TODO_LISTS_N6.

Related Objects

The table maintains documented foreign-key relationships and is commonly referenced by related OSM entities:

• AS_LEADS_ALL via LEAD_ID — the parent lead associated with the activity.
• AS_SALES_LEADS via SALES_LEAD_ID — the sales-lead record tied to the task.
• AS_TODO_LISTS_U1 — the unique index on TODO_ID that enforces primary-key uniqueness.
• AS_TODO_LISTS_N1 through N10 — non-unique indexes supporting common query paths on CUSTOMER_ID, ADDRESS_ID, CONTACT_ID, LEAD_ID, ACTIVITY_TYPE, and other business attributes.

Because the table is flagged in the ETRM documentation as Oracle Internal Use Only, direct SQL access should be restricted to standard Oracle Applications programs; custom development should rely on supported OSM APIs and views rather than direct DML against AS_TODO_LISTS_ALL.