Search Results as_todo_lists_pk

Overview

AS_TODO_LISTS_ALL is a table owned by the OSM schema within the AS – Sales Foundation product family of Oracle E-Business Suite. The ETRM metadata describes the object as obsolete, designed historically to hold activities, tasks, and to-do items for sales representatives. The _ALL suffix indicates the table is partitioned by operating unit and is expected to be filtered by ORG_ID in any multi-org aware query or report.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is standalone. No parent-child hierarchy is enforced through the mined FK relationships, so the table functions as a self-contained hub of activity records rather than a link or satellite. This classification is a modeling suggestion only; the table predates formal Data Vault conventions and carries a wide, denormalized attribute set typical of its era.

Key Information Stored

AS_TODO_LISTS_ALL contains 57 documented columns. The surrogate primary key is TODO_ID, enforced by the AS_TODO_LISTS_PK constraint and reinforced by the unique index AS_TODO_LISTS_U1. The most operationally significant columns are:

• TODO_ID — surrogate primary key and unique business-key candidate.
• DESCRIPTION — free-text description of the activity.
• ASSIGN_TO_PERSON_ID and ASSIGNED_BY_PERSON_ID — the sales representative receiving the task and the person who assigned it.
• CUSTOMER_ID, ADDRESS_ID, CONTACT_ID, PHONE_ID — the customer context to which the activity relates.
• LEAD_ID and SALES_LEAD_ID — foreign keys to AS_LEADS_ALL and AS_SALES_LEADS respectively.
• TODO_DATE, TODO_START_TIME, TODO_END_TIME — scheduling attributes for the activity.
• STATUS_CODE, CLOSED_FLAG, PRIORITY, ACTIVITY_TYPE, ACTIVITY_CODE — classification and lifecycle state.
• ORG_ID — operating unit discriminator required for multi-org access.
• PERSONAL_FLAG, DOWNLOADABLE_FLAG, PALM_FLAG, WINCE_FLAG, DEVICE1_FLAG..DEVICE3_FLAG — legacy flags for personal and mobile-device synchronization.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1..ATTRIBUTE15 — the standard EBS DFF (descriptive flexfield) block.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns.

Common Use Cases and Queries

Because the table is documented as obsolete, primary use cases are historical reporting, data migration, and reconciliation during upgrades. Typical query patterns include:

• Retrieving open activities for a sales representative: SELECT TODO_ID, DESCRIPTION, TODO_DATE, PRIORITY FROM AS_TODO_LISTS_ALL WHERE ASSIGN_TO_PERSON_ID = :person_id AND CLOSED_FLAG = 'N' AND ORG_ID = :org_id.
• Joining to leads to reconstruct the sales pipeline: SELECT t.TODO_ID, l.LEAD_NAME FROM AS_TODO_LISTS_ALL t, AS_LEADS_ALL l WHERE t.LEAD_ID = l.LEAD_ID.
• Auditing activities created by a specific concurrent program using PROGRAM_ID and REQUEST_ID.
• Extracting DFF values via the ATTRIBUTE_CATEGORY/ATTRIBUTE columns for downstream analytics.

Reports should always include the ORG_ID predicate and treat the table as read-only.

Related Objects

The table participates in the following documented relationships:

• AS_LEADS_ALL — joined on AS_TODO_LISTS_ALL.LEAD_ID = AS_LEADS_ALL.LEAD_ID.
• AS_SALES_LEADS — joined on AS_TODO_LISTS_ALL.SALES_LEAD_ID = AS_SALES_LEADS.SALES_LEAD_ID.
• AS_TODO_LISTS_PK / AS_TODO_LISTS_U1 — primary key and unique index constraints.

Additional dependencies include the OSM schema ownership context, the standard EBS concurrent program framework referenced through PROGRAM_ID and REQUEST_ID, and the multi-org (ORG_ID) security model. Any view or API layered over this obsolete table should be reviewed for deprecation during 12.1.1 to 12.2.2 migration planning.