Results for “never_processed_flag”

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

Overview

FV_PYA_TRANSACTION_HISTORY is a Federal Financials (FV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores all Prior Year Adjustment (PYA) transactions processed by the PYA Journal Creation Program. Prior Year Adjustments are a federal accounting requirement: when a transaction belonging to a closed prior fiscal year must be recorded, the adjustment is posted against prior-year funds and budget balances rather than the current period. This table functions as the persistent audit and processing ledger for those adjustments, capturing both the source transaction attributes and the resulting journal entry identifiers generated during PYA journal creation.

The table is owned by the FV schema and is documented as VALID in ETRM 12.2.2 with 35 columns. Heuristically, the object exhibits characteristics of a satellite (historized/transaction detail) rather than a hub or link, since it stores descriptive, mutable processing state and adjustment detail keyed by a surrogate identifier; this classification should be treated as a modeling suggestion only. The metadata notes it as "standalone" within the mined FK structure.

Key Information Stored

The table's unique index FV_PYA_TRANSACTION_HISTORY_U2 on TRANSACTION_HISTORY_ID identifies the primary surrogate key and the strongest business-key candidate. Its foreign key to AR_TRANSACTION_HISTORY_ALL (TRANSACTION_HISTORY_ID) links PYA processing back to Receivables transaction history. The most significant columns include:

• TRANSACTION_HISTORY_ID — surrogate primary key and FK to AR_TRANSACTION_HISTORY_ALL.
• SET_OF_BOOKS_ID — the ledger against which the adjustment is posted.
• CODE_COMBINATION_ID — the accounting flexfield combination for the adjustment distribution.
• AMOUNT — the monetary value of the prior year adjustment.
• PERIOD — the accounting period associated with the transaction.
• SOURCE_MODULE and SOURCE_DOCUMENT_NUMBER — the originating application and document reference.
• JE_BATCH_ID, JE_HEADER_ID, JE_LINE_NUM, JE_BATCH_NAME — the generated journal entry identifiers and batch name.
• TRANSACTION_ID and TRANSACTION_CODE — the source transaction identifier and code.
• CATEGORY — the journal category assigned during PYA journal creation.
• NEVER_PROCESSED_FLAG — indicates transactions not yet processed by the program.
• ORG_ID — operating unit (multi-org) context.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Federal-specific attributes include FUND_VALUE, PARENT_REVERSAL_ID, INVOICE_DISTRIBUTION_ID, ACCOUNT_VALUE, TRANSACTION_DATE, FUND_CLASS, FUND_STATUS, EXPENDED_UNEXPENDED, PAID_UNPAID, and APPORTIONED_FLAG, which support Treasury fund accounting and reporting.

Common Use Cases and Queries

Typical uses include auditing which PYA transactions were processed, reconciling generated journal entries back to source Receivables transactions, and reporting on unprocessed adjustments. A representative query to find unprocessed adjustments:

• SELECT transaction_history_id, set_of_books_id, amount, period, source_module FROM fv.fv_pya_transaction_history WHERE never_processed_flag = 'Y';

A reconciliation join back to Receivables transaction history:

• SELECT p.transaction_history_id, p.je_header_id, p.je_batch_name, a.* FROM fv.fv_pya_transaction_history p JOIN ar.ar_transaction_history_all a ON a.transaction_history_id = p.transaction_history_id WHERE p.set_of_books_id = :ledger_id;

Federal fund-level reporting frequently aggregates AMOUNT by CATEGORY, PERIOD, and FUND_CLASS to support PYA journal and Treasury reporting.

Related Objects

• AR_TRANSACTION_HISTORY_ALL — referenced via TRANSACTION_HISTORY_ID; the source transaction history for PYA processing.
• GL_JE_BATCHES and GL_JE_HEADERS — joined via JE_BATCH_ID and JE_HEADER_ID to retrieve journal batch and header details.
• GL_JE_LINES — joined via JE_HEADER_ID and JE_LINE_NUM for line-level journal detail.
• GL_CODE_COMBINATIONS — joined via CODE_COMBINATION_ID for account segment descriptions.
• GL_SETS_OF_BOOKS (or GL_LEDGERS in 12.2.x) — joined via SET_OF_BOOKS_ID for ledger context.
• AP_INVOICE_DISTRIBUTIONS_ALL — related via INVOICE_DISTRIBUTION_ID where Payables-driven adjustments are tracked.
• FV_PYA_TRANSACTIONS / PYA Journal Creation Program concurrent process — the originating program that populates this history table.