Search Results reporting_code_char_value

Overview

JE_ES_TAX_TYPE_V is a database view owned by the APPS schema in Oracle E-Business Suite, classified under the JE – European Localizations product family. It is a VALID object in both 12.1.1 and 12.2.2 and exists to support the value set JEES_TAX_TYPE, which drives the Spanish Output VAT Journal Report. In practice, the view functions as the LOV (List of Values) source that restricts the tax type selections available to the report, ensuring that users pick reporting codes and deferred tax lookups that are valid for Spanish VAT reporting rather than arbitrary tax values.

The view answers a recurring integration question: given a reporting code used on the Spanish Output VAT Journal Report, which VAT reporting entity mapping applies? This is the purpose of the MAPPING_VAT_REP_ENTITY_ID column, which ties the reporting code to its mapped VAT reporting entity. The view therefore acts as a lightweight mapping layer between Oracle E-Business Tax (EBTax) configuration tables, the reporting entity definitions in JG_ZZ_VAT_REP_ENTITIES, and the AR lookup set used for deferred tax output.

Underlying Base Objects

Per the ETRM metadata, JE_ES_TAX_TYPE_V is defined over the following referenced objects:

• ZX_REPORTING_TYPES_B (synonym to the EBTax reporting types base table) — provides TAX_REGIME_CODE and TAX, and is filtered to REPORTING_TYPE_CODE = 'EMEA_VAT_REPORTING_TYPE'.
• ZX_REPORTING_CODES_B — supplies REPORTING_CODE_CHAR_VALUE and the effective date range used to restrict valid codes via SYSDATE BETWEEN NVL(EFFECTIVE_FROM, SYSDATE) AND NVL(EFFECTIVE_TO, SYSDATE).
• ZX_REPORTING_CODES_TL — supplies the translated REPORTING_CODE_NAME, restricted to the session language through ZRCTL.LANGUAGE IN USERENV('LANG').
• JG_ZZ_VAT_REP_ENTITIES (synonym) — source of VAT_REPORTING_ENTITY_ID and MAPPING_VAT_REP_ENTITY_ID; the join is on tax regime code using NVL(ZRT.TAX_REGIME_CODE, RPS.TAX_REGIME_CODE) = RPS.TAX_REGIME_CODE.
• AR_LOOKUPS (view) — accessed through a UNION branch to append deferred tax types where LOOKUP_TYPE = 'JE_DEFERRED_TAX_TYPE'.

Because four of the five objects are synonyms, the physical base tables reside in the EBTax and receivables schemas, and the view is a multi-table join with a UNION against AR lookups.

Key Columns

• REPORTING_CODE_CHAR_VALUE — the character reporting code value from ZX_REPORTING_CODES_B; the primary LOV value.
• REPORTING_CODE_NAME — the translated reporting code description shown to the user.
• VAT_REPORTING_ENTITY_ID — identifier of the VAT reporting entity associated with the tax regime.
• MAPPING_VAT_REP_ENTITY_ID — the mapped reporting entity identifier used for Spanish VAT report attribution; this is the mapping_vat_rep_entity_id value searched by users.
• TAX_REGIME_CODE — the tax regime that qualifies the row.
• TAX — the tax name/identifier from the reporting type.

The final four columns are NULL in the UNION branch sourced from AR_LOOKUPS, since deferred tax types exist only as lookup codes and meanings.

Common Use Cases and Queries

The dominant use case is validating the mapping between a reporting code and its VAT reporting entity when configuring or reconciling the Spanish Output VAT Journal Report. To retrieve the mapping for a given reporting code:

• SELECT reporting_code_char_value, reporting_code_name, mapping_vat_rep_entity_id FROM apps.je_es_tax_type_v WHERE reporting_code_char_value = :code;
• SELECT reporting_code_char_value, reporting_code_name, vat_reporting_entity_id, mapping_vat_rep_entity_id FROM apps.je_es_tax_type_v ORDER BY reporting_code_char_value; — to audit all LOV entries including deferred tax lookups (which return NULL entity IDs).
• Join to JG_ZZ_VAT_REP_ENTITIES to resolve entity names for the returned IDs when troubleshooting report output.

Because the view filters on effective dates and session language, queries should be executed in the same language and at a date valid for the reporting period under review, otherwise expected rows may be excluded.