Results for “register_type”

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

Overview

JG_ZZ_VAT_REGISTERS_B is the base table within the JG (Regional Localizations) product family that stores the association between VAT registers and their reporting entities. In Oracle EBS 12.1.1 and 12.2.2, this object is owned by the JG schema and holds a VALID status. It functions as the master (header) table for VAT register definitions used by regional tax localization features, particularly for jurisdictions that require formal VAT register tracking — the register itself is the container that groups document sequences and transactional VAT records under a given legal reporting entity.

The table is a narrow structure with ten documented columns and a single-column surrogate primary key, VAT_REGISTER_ID, enforced through the constraint JG_ZZ_VAT_REGISTERS_B_PK and backed by unique index JG_ZZ_VAT_REGISTERS_B_U1. Heuristic Data Vault classification mined from the foreign-key topology suggests a hub-leaning role: the table introduces and governs the VAT_REGISTER_ID business key, and its only outbound foreign key establishes a link to the reporting-entity dimension (JG_ZZ_VAT_REP_ENTITIES). Under this modeling suggestion it behaves as a hub with a degenerate reference to its parent entity, rather than as a transactional satellite.

Key Information Stored

The ten documented columns break into three logical groupings:

• VAT_REGISTER_ID — the surrogate primary key. It is also the documented unique-index column (JG_ZZ_VAT_REGISTERS_B_U1) and the only business-key candidate in the constraint set, making it the join key for all dependent tables.
• VAT_REPORTING_ENTITY_ID — the outbound foreign key to JG_ZZ_VAT_REP_ENTITIES. It determines which legal reporting entity owns the register and is the principal business attribute of the row.
• REGISTER_TYPE — classifies the register (for example, distinguishing register categories recognized by the localization).
• EFFECTIVE_FROM_DATE and EFFECTIVE_TO_DATE — the date-effective range during which the register association is active. Together they provide the temporal validity window used for date-tracked queries.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns, audited automatically by the framework for row provenance and last-touch tracking.

Notably, all descriptive or translatable text — register names and descriptions — is not held here. Those attributes reside in JG_ZZ_VAT_REGISTERS_TL, the translation table keyed on VAT_REGISTER_ID. Consequently, any user-facing query must join the base table to the TL table and filter by language.

Common Use Cases and Queries

Typical usage covers VAT register maintenance, reporting-entity reconciliation, and document sequence administration. A standard lookup joins the base and translation tables to return register identity, owner, and validity:

• Registers by reporting entity: SELECT b.vat_register_id, t.name, b.register_type, b.effective_from_date, b.effective_to_date FROM jg_zz_vat_registers_b b, jg_zz_vat_registers_tl t WHERE b.vat_register_id = t.vat_register_id AND t.language = USERENV('LANG') AND b.vat_reporting_entity_id = :entity_id
• Active registers at a point in time: filter with TRUNC(SYSDATE) BETWEEN effective_from_date AND NVL(effective_to_date, TRUNC(SYSDATE)), or an explicit as-of date, to honor the date-effective design.
• Document sequence audit: join JG_ZZ_VAT_DOC_SEQUENCES on VAT_REGISTER_ID to enumerate the sequences attached to each register and to verify numbering coverage against posted VAT documents.

These patterns are common in localization support diagnostics, tax-audit extracts, and reconciliation reports that confirm every active VAT register is bound to a valid reporting entity and at least one document sequence.

Related Objects

• JG_ZZ_VAT_REP_ENTITIES — parent of this table via JG_ZZ_VAT_REGISTERS_B.VAT_REPORTING_ENTITY_ID; supplies the legal entity that owns the register.
• JG_ZZ_VAT_DOC_SEQUENCES — child table; its VAT_REGISTER_ID column references this table, so each sequence row is tied to exactly one register.
• JG_ZZ_VAT_REGISTERS_TL — translation child; VAT_REGISTER_ID references this table, holding language-specific names and descriptions.
• Constraint JG_ZZ_VAT_REGISTERS_B_PK (VAT_REGISTER_ID) and unique index JG_ZZ_VAT_REGISTERS_B_U1 (VAT_REGISTER_ID) — the enforcing objects guaranteeing key uniqueness.
• Oracle EBS Forms and concurrent programs in the JG VAT register setup flow, which read and write this base table through the standard EBS DML layer rather than direct SQL.