Results for “zx_reporting_types_b”

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

Overview

ZX_REPORTING_TYPES_B is an E-Business Tax (ZX) repository table that defines the tax reporting types available within each tax regime. In Oracle EBS 12.1.1 and 12.2.2, E-Business Tax uses reporting types to couple a reporting code set with a specific tax regime, TAX, and data format, enabling statutory, regulatory, and internal tax reporting. Each row describes a reporting type's data type, format mask, permissible length, and whether the associated reporting codes and legal messages are enabled. In modeling terms, the mined foreign-key structure of this object is satellite-leaning: it hangs off the ZX_REGIMES_B regime definition and carries descriptive, version-aware attributes rather than acting as a pure hub or link.

Key Information Stored

The physical schema exposes 24 documented columns. The most significant are:

• REPORTING_TYPE_ID — surrogate identifier for the reporting type; part of the unique index ZX_REPORTING_TYPES_B_U1 together with ZD_EDITION_NAME.
• REPORTING_TYPE_CODE and TAX_REGIME_CODE, TAX — the business-key triple that, with ZD_EDITION_NAME, forms ZX_REPORTING_TYPES_B_U2 and the primary key ZX_REPORTING_TYPES_B_PK.
• REPORTING_TYPE_DATATYPE_CODE — the data type governing valid reporting-code values (for example, text or numeric).
• FORMAT_MASK, MIN_LENGTH, MAX_LENGTH — validation rules applied to reporting codes reported under this type.
• HAS_REPORTING_CODES_FLAG — indicates whether reporting codes may be attached to the type.
• LEGAL_MESSAGE_FLAG — controls whether legal messages are surfaced for this reporting type.
• EFFECTIVE_FROM / EFFECTIVE_TO — date-range validity used in date-effective lookups.
• RECORD_TYPE_CODE — classification of the record for ETRM processing.
• ZD_EDITION_NAME — edition identifier supporting date-effective (ZD) editions of the row.
• OBJECT_VERSION_NUMBER and the standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID) — concurrency control and WHO-column auditability.

Common Use Cases and Queries

Typical scenarios include validating configuration after regime setup, driving reporting-code entry in tax determination, and building regulatory extracts. A basic lookup by regime joins the table to ZX_REGIMES_B and filters to the current edition:

• SELECT reporting_type_code, reporting_type_datatype_code, format_mask, min_length, max_length FROM zx_reporting_types_b WHERE tax_regime_code = :p_regime AND zd_edition_name = 'CURRENT';
• Retrieving the surrogate key: SELECT reporting_type_id FROM zx_reporting_types_b WHERE reporting_type_code = :p_code AND tax_regime_code = :p_regime AND tax = :p_tax AND zd_edition_name = 'CURRENT';
• Auditing recent changes: SELECT reporting_type_code, last_updated_by, last_update_date FROM zx_reporting_types_b WHERE last_update_date > SYSDATE - 7;
• Confirming reporting-code eligibility: SELECT reporting_type_code FROM zx_reporting_types_b WHERE has_reporting_codes_flag = 'Y';

Related Objects

The documented foreign key links TAX_REGIME_CODE to ZX_REGIMES_B, so regime-level queries and validations join these two directly. Related E-Business Tax objects that depend on or reference this table's keys include ZX_REPORTING_CODES, which defines the codes permitted per reporting type; ZX_REPORTING_TYPES_TL, which supplies translated names and descriptions; and the configuration and tax-determination APIs that consume reporting type identifiers. From a reporting standpoint, ZX_REPORTING_TYPES_B also feeds the ETRM-generated descriptions and standard E-Business Tax repository views that expose regime-to-reporting-type relationships for administrators and extract programs.