Search Results zx_reporting_codes_b_u2

Overview

The ZX.ZX_REPORTING_CODES_B table is a core configuration and reference object within the Oracle E-Business Tax (E-Business Tax / ETRM) module of Oracle EBS 12.1.1 and 12.2.2. It stores the reporting codes that a tax jurisdiction or tax regime assigns to transactions for statutory tax reporting purposes. Each row binds a specific reporting type (for example, a country-specific tax box, a VAT return line, or a reporting category) to a concrete reporting value and an effective date range, enabling the tax engine to derive correct reporting classifications on invoices, credit memos, and other taxable documents.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning no enforced foreign key relationships were mined. In practice, however, the table behaves much like a satellite attached to a reporting-type parent, keyed by the business key (reporting type, effective date, and the reporting code value tuple). This classification should be treated as a modeling suggestion rather than a hard rule.

Key Information Stored

The table is defined in tablespace APPS_TS_TX_DATA with 20 columns. The most operationally significant columns are:

• REPORTING_CODE_ID — Surrogate primary key (NUMBER 15); the unique identifier for a reporting code record (index ZX_REPORTING_CODES_B_U1).
• REPORTING_TYPE_ID — Identifies the reporting type to which this code belongs; part of the business key.
• REPORTING_CODE_CHAR_VALUE — Alphanumeric reporting value (e.g., a box code).
• REPORTING_CODE_DATE_VALUE — Date-typed reporting value where applicable.
• REPORTING_CODE_NUM_VALUE — Numeric reporting value where applicable.
• EFFECTIVE_FROM / EFFECTIVE_TO — Validity window controlling which code applies on a given transaction date.
• RECORD_TYPE_CODE — Distinguishes migrated, seeded, or user-defined records.
• ZD_EDITION_NAME — Editioning column supporting the 12.2 online patching / edition-based redefinition model.
• OBJECT_VERSION_NUMBER — Optimistic locking for concurrent updates.
• Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-manager audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID).

Two unique indexes are documented: ZX_REPORTING_CODES_B_U1 on REPORTING_CODE_ID and ZD_EDITION_NAME, and ZX_REPORTING_CODES_B_U2 — the primary business-key candidate — on REPORTING_TYPE_ID, EFFECTIVE_FROM, the three reporting code value columns, and ZD_EDITION_NAME.

Common Use Cases and Queries

Typical uses include validating which reporting code applies to a transaction on a given date, auditing seeded versus user-defined codes, and building statutory reporting extracts. A common pattern resolves effective-dated codes:

• Query active codes for a reporting type as of a date: SELECT * FROM zx_reporting_codes_b WHERE reporting_type_id = :id AND :dt BETWEEN effective_from AND NVL(effective_to, :dt) AND (zd_edition_name IS NULL OR zd_edition_name = 'SET1');
• List user-defined codes only: WHERE record_type_code = 'USER_DEFINED'.
• Join to reporting-type definitions via REPORTING_TYPE_ID for descriptions.

Related Objects

Although the mined classification is standalone, the table logically participates in the following relationships:

• ZX_REPORTING_TYPES_B — parent reporting type; joined on REPORTING_TYPE_ID.
• ZX_REPORTING_CODES_TL — translated name/description; joined on REPORTING_CODE_ID and language.
• ZX_REPORTING_CODES_GT / reporting-code global temporary or interface tables used during data load.
• ZX_LINES — tax lines referencing reporting codes for reconciliation.
• ZX_LINES_DET_FACTORS — detail factors carrying reporting code attributes.

These objects collectively support statutory tax reporting, returning, and audit within E-Business Tax.