Results for “jtf_cal_addresses”

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

Overview

JTF_CAL_ADDRESSES is a CRM Foundation (JTF) table that stores address and contact information associated with private contacts. According to the ETRM documentation, the table was explicitly designed to facilitate Palm synchronization in future releases, which explains its denormalized structure containing embedded name, phone, and contact fields alongside structured address components. The table is owned by the JTF schema and is marked VALID in Oracle EBS 12.1.1 and 12.2.2.

The principal consumer of this data is the resource/contact management layer of CRM Foundation, since the table anchors to a resource via RESOURCE_ID. From a Data Vault modeling perspective, the mined relationships suggest a satellite-leaning classification: JTF_CAL_ADDRESSES hangs off JTF_RS_RESOURCE_EXTNS, behaves as a descriptive attribute store rather than an independent business entity hub, and is additionally governed by a SECURITY_GROUP_ID reference to FND_SECURITY_GROUPS. It contains 41 documented columns in the 12.2.2 physical schema, making it a moderately wide descriptive table rather than a transactional or intersection table.

Key Information Stored

Among the 41 columns, the most operationally significant are those defining identity, resource linkage, contact detail, and address geography:

• ADDRESS_ID — the surrogate primary key, enforced by the JTF_CAL_ADDRESSES_PK constraint and also the sole unique index (JTF_CAL_ADDRESSES_U1). It is the only documented business-key candidate.
• RESOURCE_ID — foreign key to JTF_RS_RESOURCE_EXTNS, establishing the owning resource or private contact.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant/multi-org data isolation.
• LAST_NAME, FIRST_NAME, JOB_TITLE, COMPANY — embedded person and organization descriptors.
• PRIMARY_CONTACT — flag indicating the designated primary contact record.
• CONTACT1_TYPE / CONTACT1 through CONTACT5_TYPE / CONTACT5 — five repeating type/value phone or contact pairs, a denormalization driven by Palm sync requirements.
• ADDRESS1 through ADDRESS4, CITY, COUNTY, STATE, ZIP, COUNTRY — the structured postal address components.
• PRIVATE_FLAG — visibility control for private versus shared records.
• DELETED_AS_OF — soft-delete marker; rows are logically removed rather than physically purged, a pattern typical of sync-enabled tables.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• NOTE — free-text annotation.

Common Use Cases and Queries

Typical usage centers on retrieving contacts for a resource and reporting address completeness:

SELECT a.address_id, a.first_name, a.last_name, a.company, a.city, a.state FROM jtf.jtf_cal_addresses a WHERE a.resource_id = :p_resource_id AND a.deleted_as_of IS NULL;

Joining to the parent resource to enrich reporting:

SELECT r.*, a.address1, a.city, a.zip FROM jtf.jtf_cal_addresses a JOIN jtf.jtf_rs_resource_extns r ON r.resource_id = a.resource_id WHERE a.private_flag = 'Y';

Practical scenarios include CRM contact lookups by resource, address deduplication and data-quality audits (detecting null CITY/STATE/ZIP), identifying primary contacts per resource, and extracting private contact lists for downstream sync or marketing processes. Because PRIVATE_FLAG and SECURITY_GROUP_ID gate visibility, most production queries must filter on both.

Related Objects

• JTF_RS_RESOURCE_EXTNS — the immediate parent resource table, joined on RESOURCE_ID; the primary inbound relationship.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security filtering.
• JTF_CAL_ADDRESSES_PK / JTF_CAL_ADDRESSES_U1 — the primary key constraint and unique index on ADDRESS_ID.
• FND_USER — implicit relationship through CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• CRM Foundation contact and interaction APIs that consume resource contact data for calendar and address book functionality.