Results for “applied_to_trx_line_number”

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

Overview

FV_TC_GL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Federal Financials (FV) product family. Its name reflects its purpose: it exposes Treasury Confirmation (TC) data joined to the General Ledger (GL). The view flattens information from Treasury Confirmations, AP payment checks, and GL journal entries into a single denormalized row set suitable for federal treasury reporting, reconciliation, and inquiry. It is valid in both EBS 12.1.1 and 12.2.2, though the underlying SLA and ledger architecture is most relevant in 12.2.2.

The view is governed by the ETRM documentation and carries Oracle Proprietary, Confidential Information and Legal Notices restrictions. It is not a public API; consumers should treat it as a reporting/integration surface that may change between patch levels. Notably, several of its column aliases reuse unrelated WIP and Payables naming conventions (for example WIP_JOB_NAME, WIP_LINE_ID, APPLIED_TO_TRX_LINE_NUMBER), which is why a search for "wip_job_name" surfaces this object. In practice these aliases map onto Federal Treasury Confirmation and AP Check attributes, not to Work in Process entities.

Underlying Base Objects

The view is defined over the following documented base objects:

• FV_TREASURY_CONFIRMATIONS_ALL (synonym) — the driving Federal Treasury Confirmation records, including confirmation status, treasury document date, checkrun name, treasury confirmation ID, and set of books/ledger.
• AP_CHECKS_ALL (synonym) — AP payment checks supplying vendor name, check number, check date, check ID, and treasury pay number.
• GL_JE_HEADERS (synonym) — journal entry headers filtered to JE_SOURCE = 'PAYABLES' and JE_CATEGORY = 'TREASURY CONFIRMATION', providing currency code.
• GL_JE_LINES (synonym) — journal entry lines providing accounted and entered debit/credit amounts, code combination, and JE line number.

Joins are established as follows: FV_TREASURY_CONFIRMATIONS_ALL.TREASURY_CONFIRMATION_ID is matched to GL_JE_LINES.REFERENCE_1 (as character); SET_OF_BOOKS_ID to LEDGER_ID; the GL header to the GL line on JE_HEADER_ID and LEDGER_ID; AP_CHECKS_ALL.CHECKRUN_NAME to FV_TREASURY_CONFIRMATIONS_ALL.CHECKRUN_NAME with matching ORG_ID; and AP_CHECKS_ALL.CHECK_ID to GL_JE_LINES.REFERENCE_3.

Key Columns

• WIP_JOB_NAME — aliased from APC.VENDOR_NAME, the supplier/payee name on the AP check.
• WIP_FLOW_SCHEDULE_NUMBER — aliased from FTC.CHECKRUN_NAME, the payment checkrun identifier.
• APPLIED_TO_TRX_LINE_NUMBER — Treasury Pay Number, nulled when the confirmation status flag is 'B'.
• PAYMENT_DEPOSIT_DATE — Treasury document date from the confirmation.
• ACCOUNTED_DR / ACCOUNTED_CR / ENTERED_DR / ENTERED_CR — ledger amounts from GL_JE_LINES.
• JE_HEADER_ID, JE_LINE_NUM, CODE_COMBINATION_ID, SET_OF_BOOKS_ID, CURRENCY_CODE — GL accounting identifiers.
• APPLICATION_ID — constant 8901, identifying the Federal Financials application context.
• ORG_ID — multi-org operating unit identifier.

Common Use Cases and Queries

Typical uses include reconciling Treasury Confirmations to their GL journal entries, deriving supplier-level payment detail, and driving federal treasury reporting extracts.

Sample query:

SELECT wip_job_name, wip_flow_schedule_number, payment_deposit_date, accounted_dr, accounted_credit FROM apps.fv_tc_gl_v WHERE set_of_books_id = :ledger_id AND org_id = :org_id;

Additional patterns: joining to GL_CODE_COMBINATIONS via CODE_COMBINATION_ID for account analysis, and filtering on the confirmation status to isolate applied versus unapplied treasury lines.