Results for “to_account”

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

Overview

The FV_YE_SEQUENCE_ACCOUNTS table is a Federal Financials (FV) application table that stores the account-level detail lines associated with year-end (YE) processing sequences. It functions as the detail companion to FV_YE_GROUP_SEQUENCES, which holds the parent sequence or grouping headers. Where the group sequence table defines the overall year-end grouping and execution context, FV_YE_SEQUENCE_ACCOUNTS captures the individual account entries that participate in that sequence, including source and target account ranges and a set of descriptive flexfield attributes.

From a Data Vault modeling perspective, this table is heuristic-classified as satellite-leaning. That classification reflects its structure: it owns a surrogate primary key (SEQUENCE_ACCT_ID) and carries descriptive and transactional attributes, while its relationship to FV_YE_GROUP_SEQUENCES via SEQUENCE_ID resembles a dependent detail or satellite attached to a parent entity. This is a modeling suggestion only; in the EBS operational schema, the table is a normalized detail table with no Data Vault artifacts.

Key Information Stored

The table contains 30 documented columns. The most significant are:

• SEQUENCE_ACCT_ID — the surrogate primary key, enforced by unique index FV_YE_SEQUENCE_ACCOUNTS_U1.
• SEQUENCE_ID — the foreign key to FV_YE_GROUP_SEQUENCES, linking each detail row to its parent sequence.
• ACCOUNT_FLAG — indicates the account role or category within the sequence.
• FROM_ACCOUNT and TO_ACCOUNT — define the account range boundaries for the sequence entry.
• SET_OF_BOOKS_ID — identifies the ledger (set of books) against which accounts are resolved.
• YEAR_ENTRY — the year-end entry / period context for the sequence.
• ORDER_BY_CTR — controls processing or display order of detail rows.
• REQUISITION — a reference flag or identifier tied to requisition processing.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard EBS audit/WHO columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) segment columns.

Beyond the primary key, a second unique index — FV_YE_SEQUENCE_ACCOUNTS_U2 on (SEQUENCE_ID, ACCOUNT_FLAG, FROM_ACCOUNT) — serves as the business-key candidate, ensuring a given account/flag combination is not duplicated within the same sequence.

Common Use Cases and Queries

Typical uses involve validating year-end account ranges, reconciling sequence detail to parent sequences, and reporting on account participation across ledgers.

• Retrieving all accounts for a specific sequence:
  SELECT a.sequence_acct_id, a.account_flag, a.from_account, a.to_account, a.set_of_books_id FROM fv.fv_ye_sequence_accounts a WHERE a.sequence_id = :p_sequence_id ORDER BY a.order_by_ctr;
• Joining detail to the parent group sequence to obtain header context and description.
• Detecting overlapping or duplicate account ranges using the business-key columns (ACCOUNT_FLAG, FROM_ACCOUNT) within a sequence.
• Reporting on year-end processing by ledger, filtering on SET_OF_BOOKS_ID and YEAR_ENTRY.
• Auditing changes via LAST_UPDATE_DATE / LAST_UPDATED_BY for compliance traceability.

Related Objects

The principal related objects and join paths are:

• FV_YE_GROUP_SEQUENCES — parent table; join on FV_YE_SEQUENCE_ACCOUNTS.SEQUENCE_ID = FV_YE_GROUP_SEQUENCES.SEQUENCE_ID.
• FV_YE_SEQUENCE_ACCOUNTS_U1 / _U2 — the unique indexes enforcing the surrogate and business keys.
• GL_SETS_OF_BOOKS (GL_LEDGERS) — resolved via SET_OF_BOOKS_ID for ledger identification.
• GL_CODE_COMBINATIONS — relevant when resolving FROM_ACCOUNT / TO_ACCOUNT values to valid chart-of-accounts combinations.
• FV year-end concurrent programs and APIs that consume the group sequence and its account detail during the year-end close process.

Searches for fv_ye_sequence_accounts should focus on the SEQUENCE_ID-to-parent join and the business-key columns for data integrity checks.