Results for “zx_reporting_codes_tl_u1”

12 results




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

Overview

ZX.ZX_REPORTING_CODES_TL is a translation table within the Oracle E-Business Tax (ZX) schema of Oracle EBS 12.1.1 and 12.2.2. It stores the language-specific descriptions associated with tax reporting codes used by Oracle E-Business Tax and the underlying transaction tax engine. Reporting codes classify tax and transaction data for regulatory reporting (for example, on tax returns, fiscal reports, and country-specific statutory layouts), and the _TL suffix indicates that this table holds translatable text — the human-readable name of each reporting code, one row per installed language.

In Oracle EBS, the pattern associated with this object is a pair of tables: a base (non-translated) table that owns the reporting code identifier and its functional attributes, and the corresponding _TL table that supplies the display name per language. ZX_REPORTING_CODES_TL is therefore a supporting descriptive element for tax reporting configuration rather than a transactional or fact-bearing table.

From a Data Vault modeling perspective, the metadata classifies this object as standalone, meaning no foreign key relationships were mined from the schema. As a modeling suggestion, it is best treated as a satellite attached to a reporting code hub (or as a dependent child of the base reporting code entity), because it carries only descriptive, language-dependent attributes that describe another entity rather than relationships between entities.

Key Information Stored

The table is keyed by REPORTING_CODE_ID and LANGUAGE. The documented primary key constraint, ZX_REPORTING_CODES_TL_PK, is defined on (REPORTING_CODE_ID, LANGUAGE), and a unique index, ZX_REPORTING_CODES_TL_U1, is documented on (REPORTING_CODE_ID, LANGUAGE, ZD_EDITION_NAME). This makes REPORTING_CODE_ID the surrogate key linking back to the base reporting code entity, while LANGUAGE and ZD_EDITION_NAME together form the business-key candidates that determine uniqueness within the translation set. The most significant columns are:

  • REPORTING_CODE_ID (NUMBER) — Surrogate identifier of the tax reporting code; the join key back to the base reporting code table.
  • LANGUAGE (VARCHAR2) — Language code of the translated reporting code description; part of the primary key.
  • SOURCE_LANG (VARCHAR2) — Language code of the record from which this row was copied during an upgrade; used to preserve translation lineage.
  • REPORTING_CODE_NAME (VARCHAR2, 240) — The description of the reporting code as displayed to the user in the specified language.
  • ZD_EDITION_NAME — Edition identifier supporting Oracle's editioning feature, present in the 12.2.2 physical schema and part of the unique index.
  • CREATED_BY, CREATION_DATE — Standard Who columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns recording the most recent modification and session context.

The table is stored in the APPS_TS_TX_DATA tablespace, with the unique index in APPS_TS_TX_IDX and PCT Free of 10.

Common Use Cases and Queries

Typical scenarios include resolving a reporting code identifier to its localized display name for tax reporting and configuration screens, validating that required translations exist for each installed language, and auditing upgrade lineage through SOURCE_LANG. A representative query follows:

  • SELECT rc.reporting_code_id, rc.reporting_code_name, rc.language FROM zx.zx_reporting_codes_tl rc WHERE rc.language = USERENV('LANG') ORDER BY rc.reporting_code_name;
  • SELECT reporting_code_id, COUNT(*) FROM zx.zx_reporting_codes_tl GROUP BY reporting_code_id HAVING COUNT(*) > 1; — verify translation coverage per code.
  • SELECT reporting_code_id, language, source_lang FROM zx.zx_reporting_codes_tl WHERE source_lang <> language; — identify rows generated or copied during upgrade.

Related Objects

The metadata records no outgoing references from ZX_REPORTING_CODES_TL; it is referenced by the APPS synonym ZX_REPORTING_CODES_TL. In practice, the following objects are the most significant associated entities, joined on REPORTING_CODE_ID:

  • ZX_REPORTING_CODES (or the base reporting code entity) — parent table holding the reporting code definition; join on REPORTING_CODE_ID.
  • ZX_REPORTING_CODES_TL through the APPS synonym — the application-facing access point.
  • ZX_REPORTING_CODES_TL_PK / ZX_REPORTING_CODES_TL_U1 — primary key and unique index enforcing identity and edition uniqueness.
  • ZX_TAX_REGIMES / ZX_RATES and other ZX configuration tables that reference reporting codes for statutory reporting.
  • FND_LANGUAGES — reference table resolving LANGUAGE and SOURCE_LANG values.
  • FND_TERRITORIES — supports country-specific reporting code selection.

Because the object is classified as standalone with no mined foreign keys, joins to the base reporting code table should be confirmed against the actual 12.1.1 / 12.2.2 schema before being relied upon in custom reporting.