Search Results fv_treasury_check_ranges_u1

Overview

FV.FV_TREASURY_CHECK_RANGES is a transactional child table in the Oracle E-Business Suite Treasury module (schema FV), storing the individual check-number ranges assigned to a Treasury confirmation. In the Oracle EBS 12.1.1 and 12.2.2 data models it functions as a detail table to FV_TREASURY_CONFIRMATIONS_ALL, capturing the "from" and "to" check serial numbers that define each contiguous block of checks issued against a confirmation. The object resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10 and carries a status of VALID. Under the heuristic Data Vault classification derived from its foreign-key structure, this table is best modeled as a satellite attached to the FV_TREASURY_CONFIRMATIONS_ALL hub, since it holds descriptive, time-stamped attributes (check ranges) that are dependent on the parent confirmation key rather than acting as an independent hub or a many-to-many link.

Key Information Stored

The table contains nine documented columns. The two-column composite that forms the surrogate primary key and the unique business-key candidate (FV_TREASURY_CHECK_RANGES_U1) is:

• TREASURY_CONFIRMATION_ID – Treasury confirmation unique identifier; foreign key to FV_TREASURY_CONFIRMATIONS_ALL.
• RANGE_SEQUENCE – Sequence number that orders each check range within a confirmation, allowing multiple ranges per confirmation.

The descriptive payload columns are:

• RANGE_FROM – Starting check number of the range.
• RANGE_TO – Ending check number of the range.

Standard WHO audit columns complete the record: CREATION_DATE (row creation date), CREATED_BY (creating user, FK to FND_USER.USER_ID), LAST_UPDATE_DATE (last modification date), LAST_UPDATED_BY (last updating user, FK to FND_USER.USER_ID), and LAST_UPDATE_LOGIN (operating system login, FK to FND_LOGINS.LOGIN_ID). The unique index FV_TREASURY_CHECK_RANGES_U1 on (TREASURY_CONFIRMATION_ID, RANGE_SEQUENCE) enforces uniqueness of the range sequence within a confirmation and is the primary business-key candidate for integration and de-duplication logic.

Common Use Cases and Queries

Typical scenarios include reconciling Treasury check disbursements, auditing which serial-number blocks were consumed on a confirmation, and producing a printable list of issued check ranges for a payment batch. A representative query joins the table to its parent confirmation:

• Base extract: SELECT TREASURY_CONFIRMATION_ID, RANGE_SEQUENCE, RANGE_FROM, RANGE_TO FROM FV.FV_TREASURY_CHECK_RANGES;
• Joining to the parent header: SELECT c.*, r.RANGE_FROM, r.RANGE_TO FROM FV.FV_TREASURY_CONFIRMATIONS_ALL c, FV.FV_TREASURY_CHECK_RANGES r WHERE c.TREASURY_CONFIRMATION_ID = r.TREASURY_CONFIRMATION_ID;
• Aggregating ranges per confirmation to compute total checks: SELECT TREASURY_CONFIRMATION_ID, COUNT(*) ranges, SUM(RANGE_TO - RANGE_FROM + 1) checks FROM FV.FV_TREASURY_CHECK_RANGES GROUP BY TREASURY_CONFIRMATION_ID;
• Auditing recent changes via WHO columns: filter on LAST_UPDATE_DATE and resolve LAST_UPDATED_BY to FND_USER.USER_NAME.

Because Oracle marks the object as Internal Use Only, direct DML should be avoided; queries for reporting are acceptable, while inserts and updates must flow through standard Oracle Applications programs.

Related Objects

The table participates in a parent-child relationship anchored by TREASURY_CONFIRMATION_ID. The most significant related objects are:

• FV.FV_TREASURY_CONFIRMATIONS_ALL – parent confirmation header; the FK FV_TREASURY_CHECK_RANGES.TREASURY_CONFIRMATION_ID references it.
• FV.FV_TREASURY_CHECK_RANGES# – the underlying base table object referenced in the dependency list.
• FV_TREASURY_CHECK_RANGES_U1 – unique index on (TREASURY_CONFIRMATION_ID, RANGE_SEQUENCE).
• FND_USER – referenced by CREATED_BY and LAST_UPDATED_BY for user attribution.
• FND_LOGINS – referenced by LAST_UPDATE_LOGIN for session tracking.

These relationships make the table a reliable dependency for Treasury confirmation reporting and audit extracts across EBS 12.1.1 and 12.2.2.