Results for “jtf_xml_services_tl”

6 results




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

Overview

JTF_XML_SERVICES_TL is a translation (language-specific) table within the JTF — CRM Foundation product family of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the translatable attributes of XML service definitions, specifically the descriptive text associated with each registered service. In Oracle EBS, the JTF_XML_SERVICES entity underpins the CRM Foundation XML service registry, which maps incoming and outgoing XML service requests to their handler logic and presentation metadata. The "_TL" suffix is a standard EBS naming convention indicating that the table holds one row per language per parent entity, allowing the application to render service names, descriptions, and delivered messages in the session's current language.

The table is paired with the base table JTF_XML_SERVICES_B, which stores the language-independent columns. The documented implementation note states that JTF_XML_SERVICES_TL is "not implemented in this database," meaning that in the reference environment the table exists in the data dictionary but may contain no data or may not be physically populated. In environments where CRM Foundation XML services are actively configured, however, it functions as the descriptive companion to the base record.

Under the heuristic Data Vault classification mined from the foreign key structure, this table is described as satellite-leaning. This is a modeling suggestion: JTF_XML_SERVICES_TL behaves like a satellite because it hangs off the JTF_XML_SERVICES_B hub and carries descriptive, language-dependent attributes rather than defining new business relationships of its own.

Key Information Stored

The documented column set and key metadata for this table are compact. The columns explicitly identified in the ETRM metadata are:

  • LANGUAGE — the language code identifying the locale for the translated row. This is part of the composite primary key and is the discriminating column that makes this a translation table rather than a simple extension of the base table.
  • SERVICE_ID — the identifier of the XML service. This is the foreign key column joining back to JTF_XML_SERVICES_B.SERVICE_ID and the second component of the primary key.

The composite primary key, JTF_XML_SERVICES_TL_PK, is defined over (LANGUAGE, SERVICE_ID). In this structure, SERVICE_ID functions as the surrogate key inherited from the base table, while LANGUAGE operates as the business-key discriminator for the translation row. Because the key is composite, uniqueness is enforced at the language-and-service combination level, guaranteeing exactly one translated row per service per installed language. The metadata excerpt does not enumerate the descriptive text columns (such as SERVICE_NAME or DESCRIPTION) that would typically accompany a translation table; the two columns shown should be treated as the documented, guaranteed minimum. Queries should not assume any other column names beyond those confirmed in the data dictionary of the target instance.

Common Use Cases and Queries

Typical use cases center on retrieving human-readable service descriptions for a given language, validating translation completeness, and joining XML service configuration to runtime handler registrations.

Retrieving the translated record for a specific service and language follows a simple pattern:

  • SELECT * FROM jtf_xml_services_tl WHERE service_id = :p_service_id AND language = USERENV('LANG');
  • SELECT b.*, t.* FROM jtf_xml_services_b b, jtf_xml_services_tl t WHERE b.service_id = t.service_id AND t.language = 'US';

Translation coverage reporting is a common diagnostic, comparing the base table against available translations:

  • SELECT b.service_id, COUNT(t.language) AS trans_count FROM jtf_xml_services_b b LEFT OUTER JOIN jtf_xml_services_tl t ON b.service_id = t.service_id GROUP BY b.service_id;

Because the table is documented as not implemented in the reference database, administrators should confirm row counts before building dependent reports, and should treat empty results as a configuration observation rather than a query error. Note also that LANGUAGE is a reserved word in many Oracle contexts; qualifying it with the table alias is advisable in complex statements.

Related Objects

The following objects are most significant in relation to JTF_XML_SERVICES_TL:

  • JTF_XML_SERVICES_B — the base table holding language-independent service definitions. Joined on SERVICE_ID; it is the parent of the foreign key from this table.
  • JTF_XML_SERVICES_TL_PK — the composite primary key constraint over (LANGUAGE, SERVICE_ID) that enforces one row per language per service.
  • Foreign key constraint from JTF_XML_SERVICES_TL.SERVICE_ID to JTF_XML_SERVICES_B — the referential integrity link ensuring every translated row corresponds to a valid base service.
  • JTF_RS_* resource and CRM Foundation service registries — CRM Foundation components that consume XML service definitions at runtime and resolve descriptions through the translation table.
  • FND_LANGUAGES — the language definition table that supplies the valid LANGUAGE values used in the primary key.

Collectively, these relationships confirm that JTF_XML_SERVICES_TL is a dependent, satellite-style translation object whose principal join path is a single-column foreign key to JTF_XML_SERVICES_B on SERVICE_ID, qualified by LANGUAGE.