Results for “jtf_tty_alignments”

50+ results




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

Overview

JTF_TTY_ALIGNMENTS is a CRM Foundation (JTF) table that stores the header-level definition of a territory alignment. Within Oracle EBS 12.1.1 and 12.2.2, an alignment represents the assignment of accounts and personalized territories to a specific owning resource, such as a sales representative, sales manager, or organizational unit. The table acts as the master record from which account-level and territory-level alignment detail lines are derived, making it a central object in the Territory Management and quota administration flow.

The table resides in the JTF schema and is documented as VALID. Its primary key, JTF_TTY_ALIGNMENTS_PK, is defined on ALIGNMENT_ID. A second unique index, JTF_TTY_ALIGNMENTS_U1, is also defined on ALIGNMENT_ID, reinforcing that column as the sole business-key candidate and surrogate identifier. Based on the foreign-key topology, the metadata classifies this object as hub-leaning: it is referenced by dependent tables but points outward to only one parent, which is consistent with a hub or header entity in a Data Vault model.

Key Information Stored

The table is documented with fifteen columns. The most significant identifiers and attributes are:

Common Use Cases and Queries

Typical reporting scenarios include identifying all alignments owned by a resource, reconciling proposed versus owner quota, and locating alignments by activation or import date. Each pattern joins on ALIGNMENT_ID or filters on OWNER_RESOURCE_ID.

  • Retrieve active alignments with quotas: SELECT alignment_id, alignment_name, owner_quota, total_proposed_quota FROM jtf_tty_alignments WHERE alignment_status = 'ACTIVE'.
  • List alignments for a resource: SELECT a.alignment_id, a.alignment_name FROM jtf_tty_alignments a, jtf_rs_resource_extns r WHERE a.owner_resource_id = r.resource_id.
  • Count aligned accounts per alignment: SELECT a.alignment_name, COUNT(c.account_id) FROM jtf_tty_alignments a, jtf_tty_align_accts c WHERE a.alignment_id = c.alignment_id GROUP BY a.alignment_name.
  • Audit recently imported alignments using IMPORTED_ON and the WHO columns.

Because the table carries audit and locking columns, reporting queries should generally filter on ALIGNMENT_STATUS rather than deleting rows, and should honor OBJECT_VERSION_NUMBER when writing back through the framework.

Related Objects

The following dependents and parents are documented through the foreign-key structure:

  • JTF_RS_RESOURCE_EXTNS — Parent resource table, joined via OWNER_RESOURCE_ID.
  • JTF_TTY_ALIGN_ACCTS — Account-level alignment detail, joined via ALIGNMENT_ID.
  • JTF_TTY_ALIGN_PTERR — Personalized territory alignment detail, joined via ALIGNMENT_ID.
  • JTF_TTY_WEBADI_INTERFACE — Interface table referencing ALIGNMENT_ID for inbound alignment data.

Together these objects form the alignment hierarchy, with JTF_TTY_ALIGNMENTS serving as the header that consolidates account and territory assignments under a single owning resource and its associated quota figures.