Results for “align_acct_id”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JTF_TTY_PTERR_ACCTS is a CRM Foundation (JTF) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the proposed territory assignments generated during a territory alignment exercise. Where the alignment engine evaluates accounts against territory definitions, this table persists the proposed account-to-territory pairing before the alignment is committed. It therefore acts as the working set of assignment proposals: the intersection of an account scheduled for realignment and the proposed territory that will receive it.
The object carries a heuristic Data Vault classification of link, mined from its foreign key structure. In modeling terms, this suggests treating JTF_TTY_PTERR_ACCTS as a relationship or association table resolving a many-to-many connection between accounts and proposed territories, rather than as a descriptive hub or satellite.
Key Information Stored
The table exposes nine documented columns. The most important are the following:
- ALIGN_PTERR_ACCT_ID — surrogate primary key, enforced by the JTF_TTY_PTERR_ACCTS_PK constraint and mirrored by the unique index JTF_TTY_PTERR_ACCTS_U1. This is the primary lookup key referenced when the object is searched by its PK name.
- ALIGN_PROPOSED_TERR_ID — foreign key to JTF_TTY_ALIGN_PTERR; identifies the proposed territory receiving the assignment.
- ALIGN_ACCT_ID — foreign key to JTF_TTY_ALIGN_ACCTS; identifies the alignment account being assigned.
- OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
- CREATED_BY, CREATION_DATE — standard who-columns capturing the creating user and timestamp.
- LAST_UPDATED_BY, LAST_UPDATE_DATE — standard who-columns capturing the last modifying user and timestamp.
- LAST_UPDATE_LOGIN — login context of the last update, supporting audit trails.
The unique index JTF_TTY_PTERR_ACCTS_U1 on ALIGN_PTERR_ACCT_ID identifies that surrogate key as the sole business-key candidate documented for this object; the fabricated account-to-territory pairing itself is expressed through the two foreign keys rather than through a separate natural key.
Common Use Cases and Queries
Typical reporting scenarios include reviewing which accounts are slated for a given proposed territory, auditing the volume of proposals per alignment run, and reconciling proposals before they are finalized. Because the table is a link, joins to both parent tables are almost always required.
A representative query listing proposals with account and territory context:
SELECT p.ALIGN_PTERR_ACCT_ID, a.ALIGN_ACCT_ID, t.ALIGN_PROPOSED_TERR_ID FROM JTF.JTF_TTY_PTERR_ACCTS p JOIN JTF.JTF_TTY_ALIGN_ACCTS a ON p.ALIGN_ACCT_ID = a.ALIGN_ACCT_ID JOIN JTF.JTF_TTY_ALIGN_PTERR t ON p.ALIGN_PROPOSED_TERR_ID = t.ALIGN_PROPOSED_TERR_ID;
Counting proposals per proposed territory groups the link by territory and supports workload estimates. Filtering on CREATION_DATE or LAST_UPDATE_DATE isolates activity within a specific alignment window, and comparing OBJECT_VERSION_NUMBER identifies records that have been re-run or corrected. Audit queries may join to FND_USER on CREATED_BY and LAST_UPDATED_BY.
Related Objects
The FK relationships documented for this object identify the most significant dependencies:
- JTF_TTY_ALIGN_PTERR — parent of ALIGN_PROPOSED_TERR_ID; holds the proposed territory definition.
- JTF_TTY_ALIGN_ACCTS — parent of ALIGN_ACCT_ID; holds the alignment account records.
- JTF_TTY_PTERR_ACCTS_PK and JTF_TTY_PTERR_ACCTS_U1 — the primary key constraint and unique index defined on ALIGN_PTERR_ACCT_ID.
- Standard audit references — FND_USER via CREATED_BY and LAST_UPDATED_BY, and FND_LOGINS via LAST_UPDATE_LOGIN.
Together these objects form the alignment proposal model: accounts and proposed territories supply the parties, and JTF_TTY_PTERR_ACCTS supplies the resolved assignment link between them.
-
Stores the Proposed Territory assignments in the Alignment
-
Stores the Proposed Territory assignments in the Alignment
-
Stores Accounts used in an Alignment
-
Stores Accounts used in an Alignment
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel