Results for “alignment_id”

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

Overview

JTF_TTY_ALIGN_ACCTS is a CRM Foundation (JTF) table in Oracle E-Business Suite that stores the accounts associated with a territory alignment. In the Oracle Territory Manager (also referred to as Territory Assignment or TTY) data model, an alignment defines the assignment of territories to resources or groups, and this table records which customer accounts participate in a given alignment. The table therefore acts as a bridge between territory alignment definitions and the account groupings used to populate them.

From a heuristic Data Vault modeling perspective, JTF_TTY_ALIGN_ACCTS leans toward a satellite classification. It carries descriptive and referential attributes (alignment identifier, territory group account identifier, and audit columns) attached to a parent alignment, rather than serving as a pure many-to-many link between two hubs. This classification should be treated as a modeling suggestion derived from the foreign key structure, not as a documented physical designation.

Key Information Stored

The table contains nine documented columns, of which the following are most significant:

• ALIGN_ACCT_ID — The surrogate primary key, enforced by the JTF_TTY_ALIGN_ACCTS_PK constraint and also covered by the unique index JTF_TTY_ALIGN_ACCTS_U1. It uniquely identifies each account-alignment record and is the value referenced by child tables.
• ALIGNMENT_ID — Foreign key to JTF_TTY_ALIGNMENTS. Identifies the parent alignment to which the account is attached.
• TERR_GROUP_ACCOUNT_ID — Foreign key to JTF_TTY_TERR_GRP_ACCTS. Links the record to the territory group account entry that defines the account set for the alignment.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard audit columns recording the user and timestamp of row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification user, timestamp, and login session.

The unique index JTF_TTY_ALIGN_ACCTS_U1 on ALIGN_ACCT_ID does not introduce an independent business key; the true business relationship is expressed through the ALIGNMENT_ID and TERR_GROUP_ACCOUNT_ID foreign keys.

Common Use Cases and Queries

Typical scenarios include auditing which accounts belong to a given alignment, reconciling alignment membership against territory group accounts, and reporting territory coverage by customer. A common join pattern resolves alignment membership for a specific parent alignment:

• SELECT aa.align_acct_id, aa.alignment_id, aa.terr_group_account_id FROM jtf.jtf_tty_align_accts aa WHERE aa.alignment_id = :p_alignment_id;
• Joining to JTF_TTY_ALIGNMENTS a ON aa.alignment_id = a.alignment_id to retrieve alignment descriptive attributes.
• Joining to JTF_TTY_TERR_GRP_ACCTS g ON aa.terr_group_account_id = g.terr_group_account_id to validate that each alignment account corresponds to a defined territory group account.
• Counting accounts per alignment for coverage reporting: SELECT alignment_id, COUNT(*) FROM jtf.jtf_tty_align_accts GROUP BY alignment_id.

Because OBJECT_VERSION_NUMBER is maintained by the framework, direct DML should be avoided; changes are normally applied through the Territory Manager application or its underlying APIs.

Related Objects

• JTF_TTY_ALIGNMENTS — Referenced by ALIGNMENT_ID; the parent alignment definition.
• JTF_TTY_TERR_GRP_ACCTS — Referenced by TERR_GROUP_ACCOUNT_ID; defines territory group account membership.
• JTF_TTY_PTERR_ACCTS — References JTF_TTY_ALIGN_ACCTS via its ALIGN_ACCT_ID column, forming a dependent child relationship.
• JTF_TTY_ALIGN_ACCTS_PK and JTF_TTY_ALIGN_ACCTS_U1 — The primary key constraint and unique index governing row identity.

These relationships position JTF_TTY_ALIGN_ACCTS as a central dependency for account-level territory alignment processing in the CRM Foundation schema.