Results for “as_ref_act_attendees”

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

Overview

AS_REF_ACT_ATTENDEES is a table historically associated with the AS (Sales Foundation) product family in Oracle E-Business Suite. According to the ETRM metadata for this object, the table is documented as No longer used and is Not implemented in this database in both Oracle EBS 12.1.1 and 12.2.2. This means that in a standard, fully patched EBS environment, the object will not be present in the application schema, and no concurrent program, form, or public API should reference it at runtime.

Where the table did exist, its purpose was to record the attendees associated with a sales or reference activity schedule. The single documented foreign key—ACT_SCHEDULE_ID referencing AS_REF_ACT_SCHEDULES—places it as a child of a scheduling parent, storing one row per attendee per activity. From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning: the table carries descriptive, context-dependent attributes about a parent business entity rather than acting as an independent hub or a pure relationship link.

Key Information Stored

The documented columns of interest are limited. The most significant are:

• ACT_ATTENDEE_ID — the surrogate primary key, defined by the constraint AS_REF_ACT_ATTENDEES_PK. This is a system-generated identifier with no business meaning.
• ACT_SCHEDULE_ID — the foreign key column pointing to AS_REF_ACT_SCHEDULES. This is the principal business-key candidate, since attendee records are inherently dependent on their parent schedule and would typically be uniquely identified in combination with a person or resource reference.

Because the table is documented only through its key structure, no additional descriptive columns (such as attendee name, role, response status, or contact identifiers) can be confirmed from the ETRM metadata. Any statement about such columns would be speculative. The metadata does not document a secondary unique index; only the primary-key constraint and the single outbound foreign key are confirmed.

Common Use Cases and Queries

In the current 12.1.1 and 12.2.2 releases, there is no supported use case, because the object is not implemented. Custom code or reports that still name AS_REF_ACT_ATTENDEES will fail with an ORA-00942 (table or view does not exist) error. The practical use cases are therefore diagnostic and remediation-oriented:

• Impact analysis — locating legacy customizations. Query the data dictionary to confirm absence: SELECT table_name FROM all_tables WHERE table_name = 'AS_REF_ACT_ATTENDEES';
• Dependency discovery — search stored PL/SQL and report definitions for the identifier: SELECT name, type FROM all_source WHERE UPPER(text) LIKE '%AS_REF_ACT_ATTENDEES%';
• Upgrade remediation — during an upgrade from an earlier release, identify any custom forms, OAF pages, or BI Publisher data templates that reference the table so they can be re-pointed to a supported successor object.

No supported SQL join pattern against live data can be published, since the parent and child rows are not maintained in the current schema.

Related Objects

The principal related object, confirmed by the documented foreign key, is:

• AS_REF_ACT_SCHEDULES — referenced via AS_REF_ACT_ATTENDEES.ACT_SCHEDULE_ID. This is the parent schedule entity on which attendee rows depended.

Additional Sales Foundation reference objects that share the AS_REF_ACT_ prefix (for example, schedule and activity reference tables in the same family) are the most likely peers in any legacy data model, but the ETRM metadata excerpt does not confirm specific names, columns, or join paths for them. Consultants performing impact analysis should verify each candidate object in the target database through ALL_TABLES and ALL_CONSTRAINTS before relying on it. The governing constraint name to search for remains AS_REF_ACT_ATTENDEES_PK, and the governing foreign-key column remains ACT_SCHEDULE_ID.