Search Results as_todo_lists




Overview
Explore in AI Chat

Overview

AS_TODO_LISTS is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and classified under the AS – Sales Foundation product. It exposes multi-organization "to do" or task records that belong to the Oracle Sales and TeleSales foundation. In EBS 12.1.1 and 12.2.2, the object is documented as VALID and is implemented as an Oracle view rather than a physical table. The view functions as an OU (operating unit) filtered projection of an underlying base table, and it is most often consumed by concurrent programs, personalizations, and custom reports that need to enumerate open or closed activities assigned to sales resources.

The view does not store data; it selects from a single base object and applies an organization-security predicate. Because the filter is driven by the client-info session parameter, rows returned depend on the operating unit context that the caller has set. In Release 12.2.2, the documentation references only one base object, AS_TODO_LISTS_ALL, exposed through a synonym.

Underlying Base Objects

The documented base object referenced by this view is AS_TODO_LISTS_ALL (SYNONYM). The view text is a simple projection with a WHERE clause:

  • The SELECT list enumerates the columns of AS_TODO_LISTS_ALL, including descriptive, assignment, and relationship attributes.
  • The WHERE predicate compares the ORG_ID column to a numeric value decoded from USERENV('CLIENT_INFO'), using NVL to substitute NULL or -99 when the client-info value is absent.
  • This is the standard multi-org view pattern used throughout EBS, enforcing operating unit isolation at the SQL layer rather than in application code.

Because AS_TODO_LISTS_ALL is the multi-org table and the view applies the client-info filter, applications and reports should query AS_TODO_LISTS rather than the base table directly whenever operating unit security is required.

h4>Key Columns

The view exposes the following columns, all of which carry the same meaning as in the base table:

Common Use Cases and Queries

Typical uses include listing open tasks owned by a resource, counting personal versus organization tasks, and validating assignment integrity. Because the PERSONAL_FLAG is a frequent search term, a common query filters on it directly:

  • Open personal to-dos for a user: SELECT todo_id, description, todo_date FROM as_todo_lists WHERE personal_flag = 'Y' AND closed_flag = 'N' AND assign_to_person_id = :person_id.
  • Count by operating unit: SELECT org_id, COUNT(*) FROM as_todo_lists GROUP BY org_id.
  • Join to a sales lead: SELECT t.todo_id, t.description FROM as_todo_lists t WHERE t.lead_id IS NOT NULL.

Because the view enforces the client-info ORG_ID predicate, callers must initialize the operating unit context before querying, otherwise the filter resolves to -99 and no organization rows are returned. Reports and integrations built on AS_TODO_LISTS should therefore set the client-info session value, or use the base table with an explicit ORG_ID predicate when cross-organization reporting is required.