Results for “jtf_tty_webadi_interface”

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

Overview

The JTF.JTF_TTY_WEBADI_INTERFACE table is a CRM Foundation (JTF) interface table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store data that needs to be displayed in Excel through Oracle WebADI (Web Applications Desktop Integrator). It functions as a staging and presentation buffer: records are populated by territory management or account assignment processes, enriched with descriptive attributes, and then surfaced to end users in a spreadsheet layout where they can be reviewed, edited, and uploaded back into EBS.

The table is classified as VALID in the JTF schema and contains 442 documented columns, making it one of the widest interface structures in the CRM Foundation data model. The heuristic Data Vault classification mined from the foreign key structure is standalone, which suggests that in a Data Vault model this object would best be treated as an independent structure rather than a hub, link, or satellite; its single documented foreign key to JTF_TTY_ALIGNMENTS is not part of a broader hub-and-link network.

Key Information Stored

The table's surrogate primary key is JTF_TTY_WEBADI_INT_ID. The business relationship is anchored by ALIGNMENT_ID, which references JTF_TTY_ALIGNMENTS and identifies the territory alignment context for each row. The remaining columns fall into several functional groups:

• Account and site identification: NAMED_ACCOUNT, SITE_TYPE, DUNS, GU_DUNS, GU_NAME, DU_DUNS, DU_NAME, PARTY_NUMBER, PARTY_SITE_NUMBER, IDENTIFYING_ADDRESS.
• Address and firmographic data: CITY, STATE, PROVINCE, POSTAL_CODE, DNB_ANNUAL_REV, DNB_NUM_OF_EM, PRIOR_WON.
• Territory assignment columns: TERRITORY_GROUP, TO_TERRITORY_GROUP, TERR_GRP_ACCT_ID, ALIGNMENT_ID.
• Sales team detail: SALES_MANAGER, SALES_GROUP, SALES_ROLE, plus repeating RESOURCE<n>_NAME, RESOURCE<n>_ID, GROUP<n>_NAME, GROUP<n>_ID, ROLE<n>_NAME and ROLE<n>_ID columns for resources 1 through 30.
• Effectivity and audit: START_DATE, END_DATE, RESOURCE<n>_START_DATE, RESOURCE<n>_END_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• WebADI control columns: USER_ID, USER_SEQUENCE, DELETE_FLAG, and 15 generic ATTRIBUTE1–ATTRIBUTE15 columns used for client-specific extensions.

USER_SEQUENCE and USER_ID identify the session and ordering in which rows were staged for a specific user's WebADI workbook, while DELETE_FLAG marks rows the user has chosen to remove during the upload cycle.

Common Use Cases and Queries

Typical usage involves extracting the staged rows for a given user and alignment, verifying the data before rendering it into the WebADI Excel template, and cleaning up rows after upload. A representative query is:

SELECT JTF_TTY_WEBADI_INT_ID, ALIGNMENT_ID, NAMED_ACCOUNT, TERRITORY_GROUP, SALES_MANAGER, DELETE_FLAG FROM JTF.JTF_TTY_WEBADI_INTERFACE WHERE USER_ID = :p_user_id ORDER BY USER_SEQUENCE;

Reporting scenarios include auditing territory coverage by comparing TO_TERRITORY_GROUP against TERRITORY_GROUP, reviewing resource assignments for resources 1 through 30, and reconciling WebADI uploads by inspecting DELETE_FLAG and LAST_UPDATE_DATE. A cleanup or purge query by alignment is also common after a WebADI session completes:

DELETE FROM JTF.JTF_TTY_WEBADI_INTERFACE WHERE ALIGNMENT_ID = :p_alignment_id AND USER_ID = :p_user_id;

Related Objects

Join paths and dependent objects of significance include:

• JTF_TTY_ALIGNMENTS — referenced via ALIGNMENT_ID; the primary documented foreign key relationship.
• JTF_TTY_TERRITORIES and JTF_TTY_TERRITORY_GROUPS — supply the TERRITORY_GROUP and TO_TERRITORY_GROUP context used in WebADI territory reassignment.
• JTF_TTY_RESOURCES — source for RESOURCE<n>_ID and RESOURCE<n>_NAME values.
• HZ_PARTIES and HZ_CUST_ACCOUNTS — supply NAMED_ACCOUNT, PARTY_NUMBER and party site information referenced in the staging rows.
• FND_USER — links USER_ID and CREATED_BY/LAST_UPDATED_BY to an application user.
• JTF_TTY_WEBADI_PKG and related WebADI integrator APIs — perform population, validation, and posting of rows into the interface table.