Results for “rcv_shipment_header_id”

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

Overview

FV_PYA_GL_V is an APPS-owned database view in the Oracle E-Business Suite Federal Financials (FV) product family. It exposes Prior Year Adjustment (PYA) transaction activity that has been interfaced into Oracle General Ledger, joining the PYA transaction history tables to the resulting GL journal headers, lines, and batches. The view therefore serves as a reconciliation and audit bridge between the PYA Treasury Symbol accounting layer and the General Ledger postings it generates, presenting each PYA GL line alongside the fund, Treasury Symbol, and lookup context in which it originated. In release 12.1.1 and 12.2.2 the view is reported as VALID and is a read-only reporting construct; it holds no data of its own and inherits the Multi-Org and ledger security of the underlying GL and FV tables.

Underlying Base Objects

The view is defined over eight documented base objects: FV_PYA_TRANSACTION_HISTORY, FV_FUND_PARAMETERS, FV_TREASURY_SYMBOLS, FV_LOOKUP_CODES, GL_JE_HEADERS (referenced twice, aliased JEH1 and JEH2), GL_JE_LINES, GL_JE_BATCHES, and the FND_GLOBAL package. The driving table is FV_PYA_TRANSACTION_HISTORY (FPT), which supplies the transaction identity and amounts. FV_FUND_PARAMETERS (FFP) is joined on both FUND_VALUE and SET_OF_BOOKS_ID to resolve the fund, while FV_TREASURY_SYMBOLS (FTS) joins through TREASURY_SYMBOL_ID and FV_LOOKUP_CODES (FLC) resolves the Treasury Symbol TIME_FRAME against LOOKUP_TYPE = 'FUND_TIME_FRAME'. GL_JE_HEADERS is joined twice: JEH1 supplies the 'PYA TRANSACTIONS' sourced journal header matched on LEDGER_ID and JE_HEADER_ID, and JEH2 returns the original PYA journal header via JE_HEADER_ID, JE_BATCH_ID, and SET_OF_BOOKS_ID. GL_JE_LINES (JEL) links the transaction by TO_CHAR(TRANSACTION_ID) = REFERENCE_6, and GL_JE_BATCHES (JEB) is joined by JE_BATCH_ID. The constant APPLICATION_ID of 8901 identifies the FV application.

Key Columns

• PA_PERIOD_DATE — the searched column, mapped from FV_TREASURY_SYMBOLS.EXPIRATION_DATE, expressing the period of availability for the Treasury Symbol.
• ACCOUNTED_DR / ACCOUNTED_CR — ledger-currency debit and credit amounts from GL_JE_LINES.
• ENTERED_DR / ENTERED_CR — entered-currency debit and credit amounts from GL_JE_LINES.
• SET_OF_BOOKS_ID, JE_HEADER_ID, JE_LINE_NUM, CODE_COMBINATION_ID, CURRENCY_CODE — GL identifiers linking the PYA posting to its accounting flexfield and currency.
• WIP_BASIS, TRX_REASON_NAME, BOM_DEPARTMENT_NAME, WIP_FLOW_SCHEDULE_NUMBER, WIP_JOB_NAME, AR_ADJUSTMENT_TYPE — descriptive attributes derived from SOURCE_MODULE, JE_CATEGORY, SOURCE_DOCUMENT_NUMBER, and lookup descriptions, providing the PYA transaction context.
• UNIT_PRICE, PRICE_OVERRIDE, RCV_SHIPMENT_HEADER_ID — legacy-named columns mapped to TRANSACTION_ID, TRANSACTION_HISTORY_ID, and JE_LINE_NUM.
• APPLICATION_ID — constant 8901, the Federal Financials application identifier.

Common Use Cases and Queries

Typical uses include reconciling PYA transactions to GL postings, validating period-of-availability dates against journal activity, and producing audit extracts by fund and Treasury Symbol.

To isolate PYA activity by expiration period:

SELECT je_header_id, pa_period_date, accounted_dr, accounted_cred FROM apps.fv_pya_gl_v WHERE pa_period_date BETWEEN :from_date AND :to_date ORDER BY pa_period_date;

To reconcile a single transaction to GL:

SELECT unit_price, je_header_id, je_line_num, code_combination_id FROM apps.fv_pya_gl_v WHERE unit_price = :transaction_id;

Because PA_PERIOD_DATE is sourced from the Treasury Symbol rather than a date column on the transaction line, it is essential to filter by the correct SET_OF_BOOKS_ID when querying multiple ledgers.