Search Results zx_reporting_codes_b




Overview
Explore in AI Chat

Overview

ZX_REPORTING_CODES_VL is a validation-level (VL) view owned by the APPS schema in Oracle E-Business Suite, registered under the FND – Application Object Library product. It presents reporting code definitions maintained within the ETRM (E-Business Tax / Tax Reporting) data model, combining the language-independent base records with their translated, user-facing names. The view follows the standard Oracle EBS "_VL" convention: the "_B" suffix denotes the base table holding all transactional and descriptive attributes, while the "_TL" suffix denotes the translation table holding the language-specific reporting code name. As a view rather than a table, it stores no data of its own and exists purely as a read-only projection used for reporting, integration, and validation lookups.

The object is documented with a status of VALID in the ETRM metadata for 12.2.2 and is present in both 12.1.1 and 12.2.2 environments. Users searching for "zx_reporting_codes_b" are typically directed to this view when a name-resolved, language-filtered result set is required, since the base table alone does not expose the translated name column.

Underlying Base Objects

The view text is defined as a join between two documented base objects:

The join is performed on REPORTING_CODE_ID and is constrained by T.LANGUAGE = USERENV('LANG'), which restricts the result set to the session's current language. This ensures that the joined row returns the correct localized name for the calling environment. The view text also exposes the base table ROWID as ROW_ID.

Key Columns

  • ROW_ID — the ROWID of the underlying ZX_REPORTING_CODES_B row.
  • REPORTING_CODE_ID — the primary key linking the base and translation records.
  • REPORTING_CODE_NAME — the language-specific name for the reporting code.
  • REPORTING_CODE_CHAR_VALUE, REPORTING_CODE_DATE_VALUE, REPORTING_CODE_NUM_VALUE — the reporting code's value in character, date, and numeric forms respectively.
  • REPORTING_TYPE_ID — the identifier of the reporting type to which the code belongs.
  • EXCEPTION_CODE — a code indicating exception handling or classification.
  • EFFECTIVE_FROM / EFFECTIVE_TO — the date range during which the reporting code is valid.
  • RECORD_TYPE_CODE and OBJECT_VERSION_NUMBER — the record classification and the optimistic locking version column.
  • Audit and context columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID.

Common Use Cases and Queries

The most frequent use of this view is in tax reporting extracts and validation lookups where a reporting code must be presented by name in the user's language. Because the view encapsulates the language join, custom reports and interfaces need not re-join the base and translation tables. A typical query retrieving active codes by type is shown below.

  • Retrieving all codes with their translated names:
    SELECT reporting_code_id, reporting_code_name, reporting_code_char_value, effective_from, effective_to FROM apps.zx_reporting_codes_vl WHERE effective_to IS NULL OR effective_to >= SYSDATE;
  • Filtering by a specific reporting type and code value:
    SELECT reporting_code_name, reporting_code_num_value FROM apps.zx_reporting_codes_vl WHERE reporting_type_id = :p_type_id AND reporting_code_char_value = :p_code;
  • Correlating with the base table when audit or concurrent program context is required, or when a language-independent lookup is needed and the base table must be queried directly.

Because the view is read-only and driven by USERENV('LANG'), custom code should join it only within a session where the intended language is set, and should avoid relying on name uniqueness across reporting types.