Results for “jty_changed_terrs”

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

Overview

JTY_CHANGED_TERRS is a table owned by the JTF (CRM Foundation) schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is narrow and explicit: it stores changed territories. In the ETRM (Territory Manager) architecture, territory definitions are fluid — assignment rules, matching SQL, hierarchy relationships, and ranking logic are periodically recalculated or re-published. When a territory undergoes such a change, a marker row can be written into this table so downstream concurrent programs and assignment engines can identify which territories require reprocessing without scanning the full territory definition set.

The table carries eleven documented columns and one documented foreign key, TERR_ID → JTF_TERR_ALL. Based on the FK structure, the heuristic Data Vault classification is standalone; the metadata does not identify satelles or link tables beyond this single reference. A reasonable modeling suggestion is therefore to treat JTY_CHANGED_TERRS as an event or queue-style satellite: its rows are change signals keyed to a territory rather than master reference data.

Key Information Stored

The most significant columns fall into three groups:

• Identity: CHANGED_TERRITORY_ID is the documented surrogate primary key for the row. OBJECT_VERSION_NUMBER provides optimistic locking, incremented on each update — standard OAF/ADF concurrency behavior.
• Territory reference: TERR_ID is the foreign key pointing to JTF_TERR_ALL, identifying which territory changed and serving as the primary business-key candidate for uniqueness.
• Change classification: CHANGE_TYPE describes the nature of the change; SOURCE_ID identifies the originating record or process.
• Reprocessing flags: RANK_CALC_FLAG, PROCESS_ATTR_VALUES_FLAG, MATCHING_SQL_FLAG, and HIER_PROCESSING_FLAG indicate which territory sub-processing activities (rank recalculation, attribute value processing, matching SQL regeneration, hierarchy processing) must be re-executed for the changed territory.
• Request tracking: STAR_REQUEST_ID and TAP_REQUEST_ID tie the change to the Star and TAP concurrent request identifiers that generated or consumed it.

Common Use Cases and Queries

Typical uses center on territory refresh and debugging. A simple query lists all pending changed territories:

• SELECT CHANGED_TERRITORY_ID, TERR_ID, CHANGE_TYPE, RANK_CALC_FLAG, MATCHING_SQL_FLAG FROM JTY_CHANGED_TERRS;
• Joining to the territory master for names: SELECT c.TERR_ID, t.TERR_NAME, c.CHANGE_TYPE FROM JTY_CHANGED_TERRS c, JTF_TERR_ALL t WHERE c.TERR_ID = t.TERR_ID;
• Tracking by concurrent request: filter on STAR_REQUEST_ID or TAP_REQUEST_ID to correlate a batch run with the territories it touched.
• Flag-based triage: group by RANK_CALC_FLAG, MATCHING_SQL_FLAG, and HIER_PROCESSING_FLAG to estimate the scope of a required territory re-evaluation.

Reporting usually enumerates outstanding changes before running assignment or ranking concurrent programs, or audits which territories changed during a given period by joining request IDs to concurrent request history.

Related Objects

The documented FK anchors this table to the territory master. The most significant related objects are:

• JTF_TERR_ALL — the territory master; joined via JTY_CHANGED_TERRS.TERR_ID = JTF_TERR_ALL.TERR_ID.
• JTF_TERR_ACCESS — territory access rows affecting who sees changed territories.
• JTF_TERR_RESOURCES — resource-to-territory assignments recalculated after changes.
• JTF_TERR_DENORM — denormalized territory data refreshed by change processing.
• JTY_TERR_PROCESS_LOG — logging of territory processing runs.
• Concurrent programs in the JTF/ETRM module that read this table to drive recalculation.

Because the ETRM metadata is limited to a single FK, additional relationships should be confirmed against the live dictionary before relying on them.