Results for “as_ref_act_sch_rel_to”

6 results




Overview
Explore in AI Chat

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

Overview

AS_REF_ACT_SCH_REL_TO is a legacy table registered within the Oracle E-Business Suite AS – Sales Foundation product family. According to the ETRM metadata, the table is explicitly marked "No Longer Used" and is documented as "Not implemented in this database." This status applies across Oracle EBS 12.1.1 and 12.2.2, where the object is retained exclusively as a residual dictionary artifact for backward compatibility with earlier releases. Functional responsibility for the scheduling and relationship logic that this table once supported has since been consolidated into successor objects within the AS Foundation schema.

From a Data Vault modeling perspective, the metadata's heuristic classification places this object as satellite-leaning. The presence of a single-column surrogate primary key (ACT_SCH_REL_TO_ID) and a foreign key reference into a parent schedule table is characteristic of a satellite construct attached to a parent hub/link. Any Data Vault re-implementation effort should treat this as a descriptive satellite rather than a hub or link, though the deprecated state means such modeling is likely academic rather than operational.

Key Information Stored

Because the table is not implemented in supported databases, the documented column set is minimal. The following artifacts are the only ones identified in the metadata:

  • ACT_SCH_REL_TO_ID — The surrogate primary key, enforced by constraint AS_REF_ACT_SCH_REL_TO_PK. This is the sole documented unique identifier for the row.
  • ACT_SCHEDULE_ID — A foreign key column referencing AS_REF_ACT_SCHEDULES. This establishes the parent schedule relationship and is the only documented business-relevant attribute.

No additional business-key unique indexes, descriptive attributes, or audit columns are documented. In legacy implementations, the column name suffix "REL_TO" suggests the object stored directional or relative-to relationship data between activity schedules, but no such columns survive in the ETRM record.

Common Use Cases and Queries

In practice, this table is not queried in supported Oracle EBS environments. DBAs and developers encountering it typically do so through metadata tooling rather than application logic. Representative query patterns include:

  • Existence verification during upgrade or patch analysis: SELECT table_name FROM all_tables WHERE table_name = 'AS_REF_ACT_SCH_REL_TO'; — expected to return no rows on 12.1.1/12.2.2.
  • Dependency discovery against the parent schedule table: SELECT * FROM as_ref_act_sch_rel_to WHERE act_schedule_id = :schedule_id; — will fail with ORA-00942 unless a legacy schema copy exists.
  • Foreign key archaeology via ALL_CONSTRAINTS and ALL_CONS_COLUMNS to confirm the AS_REF_ACT_SCHEDULES linkage before decommissioning related custom objects.

Reporting use cases are effectively null; no shipped concurrent program, view, or BI Publisher report sources this object in current releases.

Related Objects

  • AS_REF_ACT_SCHEDULES — The sole documented foreign-key target, joined on AS_REF_ACT_SCH_REL_TO.ACT_SCHEDULE_ID = AS_REF_ACT_SCHEDULES.ACT_SCHEDULE_ID. This is the authoritative parent for any residual relationship.
  • AS_REF_ACT_SCH_REL_TO_PK — The primary-key constraint on ACT_SCH_REL_TO_ID.

No other views, APIs, or dependent tables are documented. Consultants should treat AS_REF_ACT_SCH_REL_TO as a deprecated artifact, exclude it from new development, and reference AS_REF_ACT_SCHEDULES directly for any scheduling relationship requirements still present in the AS Foundation module.