Search Results reporting_code_date_value




Overview

The ZX_REPORTING_CODES_B table resides in the ZX schema and is a core configuration object within the Oracle E-Business Tax (E-Business Tax / EBTax) module. It stores the reporting codes used by tax reporting and regulatory reporting processes, which allow tax authorities, fiscal reporting regimes, and internal compliance functions to classify tax transactions according to statutory reporting categories. In Oracle EBS releases 12.1.1 and 12.2.2, this table underpins the reporting code infrastructure that links tax regimes, taxes, and tax jurisdictions to the codes required on tax returns and other regulatory filings.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a standalone table, meaning it functions primarily as a reference or lookup structure rather than a transaction fact or a dependent satellite. In practical terms, it behaves as a configuration hub that defines the universe of valid reporting code values, with effectivity dating to support versioned changes over time. Its rows are relatively static, maintained by tax administrators rather than created by transactional tax calculation.

Key Information Stored

The table holds approximately twenty columns, of which the most significant for functional use and querying are:

The surrogate primary key is ZX_REPORTING_CODES_B_PK. The business-key candidate is represented by ZX_REPORTING_CODES_B_U2, which combines the reporting type, effectivity start, and the character, date, and numeric code values with the edition name — the natural identifier that guarantees uniqueness across reporting code definitions.

Common Use Cases and Queries

Typical scenarios include validating that a reporting code exists before it is attached to a tax configuration, extracting the set of currently effective reporting codes for a given reporting type, and reconciling reported tax amounts to their statutory codes. A representative query retrieving active codes is:

  • SELECT reporting_code_id, reporting_type_id, reporting_code_char_value, effective_from, effective_to FROM zx_reporting_codes_b WHERE TRUNC(SYSDATE) BETWEEN effective_from AND NVL(effective_to, TRUNC(SYSDATE));
  • Joining to reporting type definitions: ... FROM zx_reporting_codes_b b, zx_reporting_types_b t WHERE b.reporting_type_id = t.reporting_type_id;
  • Filtering by edition for multi-edition environments: ... WHERE zd_edition_name = 'SET1';

These queries are frequently embedded in tax reporting extracts, reconciliation reports, and data migration scripts that populate reporting codes into downstream tax return generation.

Related Objects

The following objects are the most significant references or dependents:

  • ZX_REPORTING_TYPES_B — Joined on REPORTING_TYPE_ID; defines the reporting types to which codes belong.
  • ZX_REPORTING_CODES_TL — Translation table for reporting code names and descriptions.
  • ZX_RATES_B and ZX_TAXES_B — Tax configuration tables associating taxes with reporting codes.
  • ZX_REGIMES_B — Tax regimes that scope reporting code assignments.
  • ZX_JURISDICTIONS_B — Jurisdictions governing reporting code applicability.
  • ZX_PARTY_TAX_PROFILE — Party-level tax profiles that may reference reporting codes.
  • ZX_REPORTING_CODES_B_PK / U1 / U2 — Key indexes enforcing integrity for the table.

Together these objects form the reporting code infrastructure that E-Business Tax relies upon for statutory and regulatory tax reporting across Oracle EBS 12.1.1 and 12.2.2.