Results for “jg_zz_vat_rep_status_u2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JG_ZZ_VAT_REP_STATUS is a transactional table in the JG (Global Tax) schema of Oracle E-Business Suite, present in both Release 12.1.1 and 12.2.2. It stores the reporting status of a Tax Registration Number by tax calendar period and by source application, and is the central control record for the VAT reporting lifecycle. Each row represents the processing state of one reporting entity combination (reporting entity, calendar period, and source such as AP, AR, or GL).

The table records four sequential lifecycle stages — selection, allocation, final reporting, and archival — together with the concurrent request identifiers and dates for each stage. Its documented status is VALID, and the object is registered in FND Design Data as JG.JG_ZZ_VAT_REP_STATUS, confirming it is a supported application data structure rather than a custom object.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. The unique business key defined by JG_ZZ_VAT_REP_STATUS_U2 (VAT_REPORTING_ENTITY_ID, TAX_CALENDAR_PERIOD, SOURCE) behaves like a hub key, while the numerous status flags, process identifiers, and process dates are descriptive, time-stamped attributes — characteristic of a satellite. This classification is advisory and intended as a modeling suggestion.

Key Information Stored

The table is physically stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its 33 columns are indexed in the APPS_TS_TX_IDX tablespace. The most operationally significant columns are:

• REPORTING_STATUS_ID — the surrogate primary key (NUMBER(15)), enforced by the unique index JG_ZZ_VAT_REP_STATUS_U1.
• VAT_REPORTING_ENTITY_ID — the reporting entity identifier; with TAX_CALENDAR_PERIOD and SOURCE it forms the unique business key JG_ZZ_VAT_REP_STATUS_U2.
• TAX_REGISTRATION_NUMBER — the VAT registration number of the reporting entity (VARCHAR2(30)).
• TAX_CALENDAR_NAME, TAX_CALENDAR_YEAR, TAX_CALENDAR_PERIOD — identify the tax calendar period being reported.
• PERIOD_START_DATE and PERIOD_END_DATE — the open and close dates of the reporting period.
• SOURCE — the source application of the transactions; documented values are AP, AR, and GL.
• SELECTION_STATUS_FLAG, ALLOCATION_STATUS_FLAG, FINAL_REPORTING_STATUS_FLAG, ARCHIVAL_STATUS_FLAG — the state of each lifecycle stage.
• SELECTION_PROCESS_ID, ALLOCATION_PROCESS_ID, FINAL_REPORTING_PROCESS_ID, ARCHIVAL_PROCESS_ID — process identifiers stamped by each stage.
• SELECTION_PROCESS_DATE, ALLOCATION_PROCESS_DATE, FINAL_REPORTING_PROCESS_DATE, ARCHIVAL_PROCESS_DATE — the dates on which each stage was executed.
• REQUEST_ID — the concurrent request that produced or last updated the record; the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

The primary use case is monitoring the completeness of the VAT reporting cycle for a given registration and period. A typical query retrieves the status flags and process dates for one entity and period:

• SELECT reporting_status_id, tax_registration_number, source, selection_status_flag, allocation_status_flag, final_reporting_status_flag, archival_status_flag FROM jg.jg_zz_vat_rep_status WHERE vat_reporting_entity_id = :entity_id AND tax_calendar_period = :period;
• Identify records not yet finalized: filter WHERE final_reporting_status_flag IS NULL OR final_reporting_process_date IS NULL.
• Audit processing: join REQUEST_ID to FND_CONCURRENT_REQUESTS to trace which concurrent program populated each stage, and PROGRAM_LOGIN_ID to FND_LOGINS for the responsible user session.
• Period performance reporting: group by TAX_CALENDAR_YEAR and TAX_CALENDAR_PERIOD to measure elapsed time between PERIOD_END_DATE and FINAL_REPORTING_PROCESS_DATE.

Related Objects

The table participates in several documented foreign key relationships:

• JG_ZZ_VAT_REP_ENTITIES — referenced from VAT_REPORTING_ENTITY_ID; the parent definition of each reporting entity.
• JG_ZZ_VAT_FINAL_REPORTS — references REPORTING_STATUS_ID; the finalized reporting output.
• JG_ZZ_VAT_TRX_DETAILS — references REPORTING_STATUS_ID; the transaction-level detail selected for reporting.
• FND_CONCURRENT_REQUESTS — referenced from REQUEST_ID, providing execution context for each stage.
• FND_LOGINS — referenced from PROGRAM_LOGIN_ID, identifying the login session that ran the process.

Together these objects form the VAT reporting sub-model within the JG schema, with JG_ZZ_VAT_REP_STATUS acting as the lifecycle control point between reporting entities and their transaction details.