Search Results ja_cn_voucher_bank_num

Overview

The JA_CN_VOUCHER_BANK_NUM table is a localization data object within the JA (Asia/Pacific Localizations) product family in Oracle E-Business Suite, specifically supporting the China country-specific accounting requirements. It stores the sequential numbering state used to generate voucher numbers for bank-related accounting entries, including voucher types such as bank payments, bank receipts, and bank deposit/withdrawal transactions that must follow Chinese statutory numbering rules. Accounting divisions in China frequently require separate, gapless, period-based voucher number sequences for banking transactions, and this table acts as the persistent counter that enforces those sequences.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is modeled as a satellite. It holds descriptive, mutable state (the NEXT_NUMBER counter and audit columns) that changes over time as vouchers are generated, and it is keyed by a business composite that references the parent legal entity. This differs from a hub or link, which would normally hold only immutable identifier or relationship data.

Key Information Stored

Each row represents the numbering state for a unique combination of ledger, legal entity, accounting period, and balance segment. The business-key uniqueness is enforced by the index JA_CN_VOUCHER_BANK_NUM_U1, which covers the four columns that define that combination.

• LEDGER_ID — Identifies the ledger (chart of accounts / accounting setup) within which the voucher numbering applies. Part of the unique business key.
• LEGAL_ENTITY_ID — The legal entity for which the numbering sequence is maintained; foreign key to FV_LEGAL_ENTITIES. Part of the unique business key.
• PERIOD_NAME — The accounting period the numbering sequence belongs to, enabling period-by-period reset of bank voucher numbers. Part of the unique business key.
• BALANCE_SEGMENT — The balancing segment value, allowing separate numbering per accounting entity or balancing segment. Part of the unique business key.
• NEXT_NUMBER — The next voucher number to be assigned. This is the operative column that advances each time a bank voucher is created.
• CREATED_BY, CREATION_DATE — Standard "who created" audit columns.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "who last updated" audit columns, which track when the counter was most recently incremented.

The documented metadata does not expose a separate surrogate primary key column; the unique index JA_CN_VOUCHER_BANK_NUM_U1 on (LEDGER_ID, LEGAL_ENTITY_ID, PERIOD_NAME, BALANCE_SEGMENT) is the effective row identity.

Common Use Cases and Queries

Typical usage includes reconciliation of issued bank voucher numbers, auditing for gaps in numbering sequences, and reporting on remaining capacity for a given period. A representative query to inspect the current counter state for a ledger and period might resemble:

• SELECT ledger_id, legal_entity_id, period_name, balance_segment, next_number FROM ja.ja_cn_voucher_bank_num WHERE ledger_id = :p_ledger AND period_name = :p_period;
• Reconciliation reporting: joining to voucher/journal line tables to detect duplicates or skipped numbers between the assigned voucher number and the NEXT_NUMBER value.
• Audit queries: listing all rows by legal entity and period to verify that each balancing segment has its own valid sequence.
• Capacity / monitoring: identifying periods where NEXT_NUMBER approaches configured limits before the next accounting period rollover.

Because the table is updated transactionally during voucher generation, direct DML should be avoided in production; extraction is best performed through read-only reporting views or by the localization APIs that own the numbering logic.

Related Objects

• FV_LEGAL_ENTITIES — Referenced through LEGAL_ENTITY_ID; the primary parental relationship for this satellite.
• GL_LEDGERS — Corresponds to LEDGER_ID, identifying the accounting ledger context.
• GL_PERIODS / GL_PERIOD_STATUSES — Provide the period-name and open/closed status context for PERIOD_NAME.
• JA_CN_VOUCHER (and related China voucher tables) — Consume the NEXT_NUMBER value to produce actual generated vouchers.
• FND_FLEX_VALUES — Supplies the balancing segment value referenced by BALANCE_SEGMENT.
• JA_CN_VOUCHER_BANK_NUM_U1 — The unique index enforcing the business key, referenced here as a schema object.

These relationships define the table's integration point into the China localization voucher-numbering framework and its dependency on core General Ledger and legal-entity setup.