Results for “jtf_tty_geo_webadi_interface”

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

Overview

JTF.JTF_TTY_GEO_WEBADI_INTERFACE is a staging and interface table within the CRM Foundation (JTF) product family of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to serve as the Geography WEB ADI interface table, meaning it acts as the transient landing area for records uploaded through Oracle Web Applications Desktop Integrator (Web ADI) spreadsheets when users perform bulk maintenance of territory geography definitions. Rather than writing directly to the production territory geography tables, Web ADI uploads populate this interface table first, where rows can be validated, transformed, and subsequently processed into the base geography territory value structures.

From a Data Vault modeling perspective, the documented metadata classifies this table as standalone, with only one foreign key relationship. A heuristic classification therefore suggests a satellite-like role: the table carries descriptive geographic attributes (country, state, city, postal code) plus audit and sequence columns associated with a single parent reference to JTF_TTY_GEO_TERR_VALUES via GEO_TERR_VALUE_ID. Because it holds no downstream dependents of its own, it is best treated as a leaf-level interface satellite rather than a hub or link.

Key Information Stored

The table is documented with 17 columns in the 12.2.2 physical schema. The surrogate primary key is JTF_TTY_WEBADI_INT_ID, which uniquely identifies each interface row and is the column most commonly used for row-level retrieval and cleanup. A second identifier, GEO_TERR_VALUE_ID, functions as the foreign key to JTF_TTY_GEO_TERR_VALUES and is the principal business-key candidate linking the staged row to its parent geography territory value.

The geographic business content is carried by COUNTRY, STATE_PROVINCE, CITY, and POSTAL_CODE, which together describe the address hierarchy being uploaded. GEO_TERR_NAME holds the human-readable geography territory name, while TERRITORY_GROUP and MANAGER_TERR_NAME provide grouping and managerial territory context. Batch and session tracking are supported by USER_ID and USER_SEQUENCE, which identify the uploading user and the ordering of rows within that user's upload. Standard EBS concurrency and audit columns are present: OBJECT_VERSION_NUMBER supports optimistic locking, while CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture the creation and modification history of each staged record.

Common Use Cases and Queries

The primary use case is validating and monitoring Web ADI territory geography uploads before and after import. Administrators typically query rows for a specific user or recent time window to confirm that the spreadsheet content was staged correctly. A representative pattern is a filter by the uploading user and their sequence:

• SELECT JTF_TTY_WEBADI_INT_ID, TERRITORY_GROUP, GEO_TERR_NAME, COUNTRY, STATE_PROVINCE, CITY, POSTAL_CODE FROM JTF.JTF_TTY_GEO_WEBADI_INTERFACE WHERE USER_ID = :p_user_id ORDER BY USER_SEQUENCE;
• Reconciliation against the parent value, joining on GEO_TERR_VALUE_ID = JTF_TTY_GEO_TERR_VALUES.GEO_TERR_VALUE_ID to verify that staged rows resolve to valid territory values.
• Error triage: listing rows whose geographic attributes fall outside expected reference sets, or identifying rows where GEO_TERR_NAME was not matched.
• Audit reporting on LAST_UPDATE_DATE and LAST_UPDATED_BY to track which administrators last staged or cleansed geography data.

Because these rows are transient, housekeeping queries that purge processed or stale interface records are also common operational tasks.

Related Objects

The documented foreign key relationship anchors this table to the territory geography value master. The most significant related objects are:

• JTF_TTY_GEO_TERR_VALUES — the parent table referenced by GEO_TERR_VALUE_ID; the authoritative source of geography territory values into which staged rows are processed.
• JTF_TTY_GEO_WEBADI_INTERFACE itself, accessed through Web ADI concurrent programs and geography administration flows that read, validate, and purge its rows.
• CRM Foundation territory administration forms and concurrent managers that consume this interface during bulk geography maintenance.
• Adjacent JTF territory value and territory group tables that supply reference data for TERRITORY_GROUP and MANAGER_TERR_NAME validation.
• Standard audit and user reference objects (FND_USER) implied by USER_ID and the CREATED_BY / LAST_UPDATED_BY columns.