Results for “act_location_id”

2 results




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

Overview

AS_REF_ACT_LOCATIONS is a legacy table within the AS (Sales Foundation) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The Electronic Technical Reference Manual (ETRM) explicitly classifies this object with the description "No Longer Used" and confirms that it is "Not implemented in this database." Despite this deprecated status, the table's metadata remains useful for understanding historical data models, migration scripts, and reverse-engineering efforts where older Sales Foundation or Oracle Sales Online customizations persisted.

Functionally, the table served as a cross-reference linking sales activity records to physical location data. It associated an activity schedule (from AS_REF_ACT_SCHEDULES) with a specific contact point, party site, and location, thereby enabling location-aware activity tracking. From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is link. This suggests that AS_REF_ACT_LOCATIONS is best modeled as a link table resolving relationships between several business entities rather than acting as a hub of independent business keys or a satellite of descriptive attributes.

Key Information Stored

The documented metadata identifies the following columns as significant. The surrogate primary key is ACT_LOCATION_ID, defined by the constraint AS_REF_ACT_LOCATIONS_PK. This primary key uniquely identifies each cross-reference record. The remaining documented columns are foreign key columns that establish the table's relationships:

  • ACT_LOCATION_ID — Surrogate primary key; uniquely identifies the activity-location association. Not a business key.
  • ACT_SCHEDULE_ID — Foreign key to AS_REF_ACT_SCHEDULES; identifies the overarching sales activity schedule to which the location applies.
  • CONTACT_POINT_ID — Foreign key to HZ_CONTACT_POINTS; identifies the contact mechanism (phone, email, URL, etc.) associated with the activity location.
  • PARTY_SITE_ID — Foreign key to HZ_PARTY_SITES; identifies the party site linked to the activity.
  • LOCATION_ID — Foreign key to HZ_LOCATIONS; identifies the geographic or address location record.

The ETRM does not document additional unique or business-key indexes beyond the primary key. Consequently, no natural business key is formally recognized in the supplied metadata.

Common Use Cases and Queries

Because the table is not implemented in the current database, direct production queries are not viable. However, in legacy systems, migration exercises, or sandbox environments where this table may be recreated, the following patterns are typical. A join to HZ_CONTACT_POINTS is directly relevant to the user's search term "hz_contact_points," reflecting a need to trace contact information associated with sales activity locations:

  • Reconstructing activity-to-contact-point mappings for historical reporting.
  • Auditing which party sites and locations were referenced by sales schedules prior to deprecation.
  • Data migration validation: verifying orphaned CONTACT_POINT_ID or PARTY_SITE_ID values before archiving or converting records.

A representative SQL pattern for legacy data extraction would be:

SELECT a.act_location_id, a.act_schedule_id, cp.contact_point_type, cp.contact_point_value, ps.party_site_id, loc.location_id FROM as_ref_act_locations a JOIN hz_contact_points cp ON a.contact_point_id = cp.contact_point_id JOIN hz_party_sites ps ON a.party_site_id = ps.party_site_id JOIN hz_locations loc ON a.location_id = loc.location_id;

Reporting teams migrating off Sales Foundation should use such queries to map legacy activity locations into current CRM or TCA structures.

Related Objects

The documented foreign key relationships identify the most significant dependent and referenced objects:

  • AS_REF_ACT_SCHEDULES — Parent schedule table; joined via ACT_SCHEDULE_ID.
  • HZ_CONTACT_POINTS — Contact point registry; joined via CONTACT_POINT_ID. This is the object most directly implicated by the user's search term.
  • HZ_PARTY_SITES — Party site assignments; joined via PARTY_SITE_ID.
  • HZ_LOCATIONS — Address and location master; joined via LOCATION_ID.

Together, these four objects define the complete relational context of AS_REF_ACT_LOCATIONS. Any analysis of this deprecated table should begin with these joins, as no additional referencing objects are documented in the ETRM metadata.