Results for “jtf_tty_align_pterr”

50+ results




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

Overview

JTF_TTY_ALIGN_PTERR is a CRM Foundation (JTF) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the resources used during a territory alignment run together with the proposed quotas assigned to those resources. It therefore acts as the intersection between an alignment execution (JTF_TTY_ALIGNMENTS) and the individual resources or resource groups that receive proposed territory assignments, preserving the pre-commit proposal state before alignment results are finalized.

Under the supplied relationship metadata, the object leans toward a satellite classification: its rows are keyed by a single surrogate identifier (ALIGN_PROPOSED_TERR_ID) and carry descriptive, non-hub attributes such as PROPOSED_QUOTA, RESOURCE_TYPE, and RSC_ROLE_CODE that change as alignment proposals are regenerated. This is a heuristic modeling suggestion rather than a documented Data Vault construct.

Key Information Stored

  • ALIGN_PROPOSED_TERR_ID — surrogate primary key (JTF_TTY_ALIGN_PTERR_PK) and the business-key candidate exposed by unique index JTF_TTY_ALIGN_PTERR_U1; it is the column that downstream tables join against.
  • ALIGNMENT_ID — foreign key to JTF_TTY_ALIGNMENTS, identifying the alignment run that produced this proposal.
  • RESOURCE_ID — foreign key to JTF_RS_RESOURCE_EXTNS, pointing to the individual resource included in the alignment.
  • RSC_GROUP_ID — foreign key to JTF_RS_GROUPS_B, used when the aligned entity is a resource group rather than a single resource.
  • PROPOSED_QUOTA — the quota value proposed for the resource or group within the alignment, forming the core business payload of the row.
  • RESOURCE_TYPE and RSC_ROLE_CODE — classify the aligned party and the role it plays in territory coverage.
  • OBJECT_VERSION_NUMBER — optimistic concurrency control, indicating the row follows the standard EBS multi-version pattern.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and WHO columns.

The documented schema contains 13 columns in total; the surrogate key is distinct from the alignment/resource combination, which is not enforced as a separate unique constraint.

Common Use Cases and Queries

Typical reporting scenarios include reviewing proposed quotas by alignment run, comparing proposals against finalized territory assignments, and auditing resource participation in a given alignment.

  • Proposed quota listing per alignment:
    SELECT p.ALIGN_PROPOSED_TERR_ID, p.RESOURCE_ID, p.PROPOSED_QUOTA FROM JTF.JTF_TTY_ALIGN_PTERR p WHERE p.ALIGNMENT_ID = :alignment_id;
  • Resource-level detail joined to resource extension data:
    SELECT p.RESOURCE_ID, r.RESOURCE_NUMBER, p.PROPOSED_QUOTA FROM JTF.JTF_TTY_ALIGN_PTERR p, JTF.JTF_RS_RESOURCE_EXTNS r WHERE p.RESOURCE_ID = r.RESOURCE_ID;
  • Group-level proposals:
    SELECT p.RSC_GROUP_ID, g.* FROM JTF.JTF_TTY_ALIGN_PTERR p, JTF.JTF_RS_GROUPS_B g WHERE p.RSC_GROUP_ID = g.GROUP_ID;
  • Discovery of related account and metric detail via the child tables:
    SELECT a.ALIGN_PROPOSED_TERR_ID, a.* FROM JTF.JTF_TTY_PTERR_ACCTS a WHERE a.ALIGN_PROPOSED_TERR_ID = :id;

Because alignment processing is bulk-oriented, queries should filter on ALIGNMENT_ID and use the unique index on ALIGN_PROPOSED_TERR_ID for single-row lookups. Historical reporting should also constrain by CREATION_DATE or LAST_UPDATE_DATE to scope results to a specific alignment cycle.

Related Objects

  • JTF_TTY_ALIGNMENTS — parent by ALIGNMENT_ID; defines the alignment run.
  • JTF_RS_RESOURCE_EXTNS — parent by RESOURCE_ID; the aligned resource.
  • JTF_RS_GROUPS_B — parent by RSC_GROUP_ID; the aligned resource group.
  • JTF_TTY_PTERR_ACCTS — child referencing ALIGN_PROPOSED_TERR_ID; account-level detail for the proposal.
  • JTF_TTY_PTERR_METRICS — child referencing ALIGN_PROPOSED_TERR_ID; metric values supporting the proposal.

These five relationships, documented in the ETRM metadata, define the primary access paths and join columns for this table.