Results for “as_ref_act_schedules”

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

Overview

AS_REF_ACT_SCHEDULES is a reference table in the Oracle E-Business Suite Sales Foundation (AS) product family. Per the ETRM documentation, the table carries the description "No Longer Used," and its implementation/DBA data states "Not implemented in this database." This indicates that AS_REF_ACT_SCHEDULES is a legacy or obsolete object retained in the data model for historical or schema-versioning purposes, and should not be treated as an active transactional or reference entity in current Oracle EBS 12.1.1 or 12.2.2 environments. The table's presence in the metadata primarily serves to document legacy relationships and to support any historical data migration or upgrade scripts.

From a Data Vault modeling perspective, the heuristic classification provided is hub-leaning. This suggests that AS_REF_ACT_SCHEDULES functions primarily as a hub, with the surrogate primary key ACT_SCHEDULE_ID acting as the business key candidate, while the foreign key to AS_REF_DELIVERABLES would represent a link to another hub. This is a modeling suggestion only; given the table's deprecated status, actual data vault implementation is unlikely to be relevant.

Key Information Stored

The documented metadata identifies a limited set of columns. The most important are:

• ACT_SCHEDULE_ID — the surrogate primary key, defined by the constraint AS_REF_ACT_SCHEDULES_PK. This is the only column explicitly named in the documentation and serves as the unique identifier for each row.
• DELIVERABLE_ID — a foreign key column referencing AS_REF_DELIVERABLES. This establishes a relationship between an activity schedule and a deliverable, representing a business-key candidate for the hub.

No other columns are documented in the ETRM excerpt. Because the table is marked "No Longer Used" and "Not implemented in this database," the full column list is either unavailable or not maintained. Any columns beyond these two would be inherited from legacy schema definitions that are no longer active in supported releases.

Common Use Cases and Queries

Since AS_REF_ACT_SCHEDULES is not implemented in the current database, direct querying is generally not possible. However, its legacy structure may still appear in upgrade scripts, archived schemas, or documentation reviews. Common scenarios include:

• Upgrade impact analysis — verifying whether legacy customizations or interfaces reference AS_REF_ACT_SCHEDULES before migrating from 12.1.1 to 12.2.2.
• Data lineage investigation — tracing historical activity schedule data through the foreign key relationships to understand how deliverables, attendees, and locations were previously modeled.
• Schema comparison — confirming that this table is absent from active database instances and that no dependent objects remain.

A representative query pattern, if the table were present, would resemble:

SELECT s.ACT_SCHEDULE_ID, s.DELIVERABLE_ID FROM AS_REF_ACT_SCHEDULES s WHERE s.DELIVERABLE_ID = :deliverable_id;

Reporting use cases would likely involve joining to AS_REF_DELIVERABLES to associate schedules with their parent deliverables, but again, this is only relevant for legacy data retrieval.

Related Objects

The documented foreign key relationships identify the following significant related objects:

• AS_REF_DELIVERABLES — referenced by AS_REF_ACT_SCHEDULES.DELIVERABLE_ID; the parent entity for deliverables.
• AS_REF_ACT_ATTENDEES — references AS_REF_ACT_SCHEDULES via ACT_SCHEDULE_ID; legacy attendee records per schedule.
• AS_REF_ACT_LOCATIONS — references AS_REF_ACT_SCHEDULES via ACT_SCHEDULE_ID; legacy location records per schedule.
• AS_REF_ACT_SCH_REL_TO — references AS_REF_ACT_SCHEDULES via ACT_SCHEDULE_ID; legacy schedule-to-schedule relationships.

These dependents further confirm that AS_REF_ACT_SCHEDULES was once a central hub for activity schedule data within the Sales Foundation module. Because the table is no longer used or implemented, these relationships are of historical interest only and should not be relied upon for current application logic, reporting, or integration design in Oracle EBS 12.1.1 or 12.2.2.