Search Results zx_reporting_types_b

Overview

The ZX_REPORTING_TYPES_B table is a core repository within the ZX (E-Business Tax) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the master definition table for tax reporting types, which are critical classifications used for statutory and regulatory tax reporting. These reporting types categorize taxable transactions for purposes such as filing VAT/GST returns, generating government-mandated reports like SAF-T, or meeting specific country-level legal requirements. The table's role is to establish and maintain the valid set of reporting codes that can be assigned to tax lines, ensuring compliance with the reporting rules defined for a given tax regime and tax.

Key Information Stored

The table's structure centers on a composite primary key that uniquely identifies a reporting type within the context of a specific tax. The most critical columns, as indicated by the primary and foreign key metadata, are:

• REPORTING_TYPE_CODE: The unique identifier for the reporting classification (e.g., codes for Standard Rated, Zero Rated, Exempt, or Non-Taxable supplies).
• TAX_REGIME_CODE: The code identifying the overarching tax regime (e.g., VAT, GST) to which this reporting type belongs. This column is a foreign key to ZX_REGIMES_B.
• TAX: The specific tax code within the identified regime. This, combined with the regime code and reporting type code, forms the unique key.

Additional descriptive columns, common in "_B" base tables in EBS, typically include NAME, DESCRIPTION, and ENABLED_FLAG, though these are inferred from standard design patterns as the provided metadata focuses on keys.

Common Use Cases and Queries

This table is primarily referenced during transaction tax calculation and reporting processes. A common use case is the generation of a VAT summary report, where transaction lines are aggregated by their assigned reporting type. System administrators or implementers may query this table to verify setup or troubleshoot reporting issues. A typical validation query would join to the tax regimes table to list all active reporting types for a specific tax:

SELECT rgt.reporting_type_code, rgt.name, rgt.description
FROM zx_reporting_types_b rgt, zx_regimes_b reg
WHERE rgt.tax_regime_code = reg.tax_regime_code
AND reg.tax_regime_code = 'VAT_REGIME_CODE'
AND rgt.tax = 'STANDARD'
AND rgt.enabled_flag = 'Y'
ORDER BY rgt.reporting_type_code;

Another critical pattern is its use in subqueries within data extracts for statutory reporting, where the REPORTING_TYPE_CODE from transaction tables (like ZX_LINES) is validated against the definitions in ZX_REPORTING_TYPES_B.

Related Objects

Based on the documented foreign key relationship, the primary related object is:

• ZX_REGIMES_B: The ZX_REPORTING_TYPES_B table has a foreign key dependency on this table via the TAX_REGIME_CODE column. This enforces that a reporting type must be associated with a valid, pre-defined tax regime.

Furthermore, as a master definition table, ZX_REPORTING_TYPES_B is almost certainly referenced by child transactional tables (such as ZX_LINES) that store the applied reporting type for a specific invoice line. It is also a likely source for key reporting views within the E-Business Tax module, which present a consolidated and often translated version of this data for application screens and standard reports.