Search Results driving_date_code

Overview

JG_ZZ_VAT_REP_ENTITIES_V is an APPS-owned database view that exposes VAT reporting entity configuration used by the JG (Regional Localizations) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents a complete projection over the JG_ZZ_VAT_REP_ENTITIES base object, carrying configuration attributes that govern how a legal entity or party is treated as a VAT reporting entity within a given tax regime. Its status is VALID, indicating the view is compiled and available for querying in the ETRM environment.

The view plays a configuration-facing role rather than a transactional one. It is referenced by VAT reporting and localization processes that must determine, for a given reporting entity, the applicable tax regime, tax registration number, tax calendar, allocation and register behavior, and the reporting-entity hierarchy relationships captured by entity type and entity level codes. Because it exposes ROWID alongside the primary key VAT_REPORTING_ENTITY_ID, the view supports both read-only reporting and correlation with the underlying row for maintenance or diagnostic purposes.

Underlying Base Objects

The documented definition is a straightforward, unfiltered selection from the JG_ZZ_VAT_REP_ENTITIES synonym:

• JG_ZZ_VAT_REP_ENTITIES — the single referenced base object, accessed through its APPS synonym. No joins, unions, or filters are applied.
• Projection — the view selects ROWID plus twenty-four named columns from the base object, preserving column names and data types exactly as defined at the table level.

Because the view is a direct projection with no filtering or aggregation, it behaves as a logical alias for the base table. This is significant for tuning: predicates applied against view columns are pushed to the base object, and indexes on JG_ZZ_VAT_REP_ENTITIES remain usable through the view. The absence of DISTINCT or GROUP BY means no implicit sort or deduplication occurs, and all rows in the base object are visible to any query with sufficient privileges.

Key Columns

• ROW_ID — the ROWID of the underlying base row, useful for direct row identification.
• VAT_REPORTING_ENTITY_ID — primary identifier of the VAT reporting entity.
• LEGAL_ENTITY_ID, PARTY_ID — the legal entity and party associated with the reporting entity.
• TAX_REGIME_CODE — the tax regime under which the entity reports.
• TAX_REGISTRATION_NUMBER, TAX_CALENDAR_NAME — registration identifier and reporting calendar.
• THRESHOLD_AMOUNT — the monetary threshold configured for the reporting entity, used to drive threshold-based VAT reporting or allocation behavior.
• ENABLE_ALLOCATIONS_FLAG, ENABLE_ANNUAL_ALLOCATION_FLAG, ENABLE_REGISTERS_FLAG, ENABLE_REPORT_SEQUENCE_FLAG — feature switches controlling allocation processing, annual allocations, register maintenance, and report sequencing.
• ENTITY_TYPE_CODE, ENTITY_LEVEL_CODE, ENTITY_IDENTIFIER — classification of the reporting entity and its position within the reporting hierarchy.
• LEDGER_ID, BALANCING_SEGMENT_VALUE — ledger and balancing segment linkage for reporting.
• MAPPING_VAT_REP_ENTITY_ID — reference to a mapped reporting entity, supporting parent/child or mapping relationships.
• DRIVING_DATE_CODE — determines which date drives reporting period determination.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried to inspect VAT reporting entity configuration, especially where threshold or enablement settings affect reporting output. A common pattern retrieves entities above or at a configured threshold amount:

• Threshold inspection — list entities and their THRESHOLD_AMOUNT to audit configuration prior to running VAT reports.
• Feature enablement review — identify entities with allocations, annual allocations, registers, or report sequencing enabled.
• Regime/registration lookup — resolve TAX_REGISTRATION_NUMBER and TAX_CALENDAR_NAME by TAX_REGIME_CODE.
• Hierarchy mapping — trace MAPPING_VAT_REP_ENTITY_ID and entity level/type codes.

Example query addressing the threshold search:

SELECT vat_reporting_entity_id, legal_entity_id, tax_regime_code, tax_registration_number, threshold_amount, enable_allocations_flag, enable_registers_flag FROM jg_zz_vat_rep_entities_v WHERE threshold_amount IS NOT NULL ORDER BY threshold_amount DESC;

Example filtered by regime and calendar:

SELECT vat_reporting_entity_id, entity_type_code, entity_level_code, ledger_id, balancing_segment_value, driving_date_code FROM jg_zz_vat_rep_entities_v WHERE tax_regime_code = :regime AND tax_calendar_name = :calendar;

All queries should be run with APPS-level or appropriately granted privileges, and results validated against the base object where maintenance is required.