Results for “external_reference”

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

Overview

FV_SF224_TEMP is a transient staging table owned by the FV schema within the Federal Financials (FV) product of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its stated purpose is to hold those records selected for reporting in a specified period, making it the intermediate repository for the Treasury SF-224 (Statement of Transactions) reporting process. When the SF-224 report program runs, qualifying journal lines and associated attributes are extracted from the General Ledger and written to this table, where they can be reviewed, adjusted for exceptions, and subsequently published to the final federal report output.

The physical schema in 12.2.2 comprises 64 columns, reflecting the breadth of attributes needed to present federal transaction detail — funds, agencies, symbols, obligations, and reclassifications. From a data-vault modeling perspective, the mined foreign-key structure suggests a link classification, since the table predominantly binds together references to other business entities rather than holding standalone descriptive master data. This classification is a heuristic suggestion rather than a delivered Oracle designation.

Key Information Stored

The most significant columns fall into three groups.

• Foreign key and context identifiers: JE_BATCH_ID references the originating GL_JE_BATCHES row; SET_OF_BOOKS_ID identifies the ledger; FEDERAL_RPT_ID ties the record to a report definition in FV_REPORT_DEFINITIONS. JE_HEADER_ID, JE_LINE_NUM, JE_SOURCE, and JE_CATEGORY further locate the source journal detail.
• Reporting attributes: SF224_TYPE_CODE, D_R_FLAG (debit/credit indicator), RECORD_TYPE, RECORD_CATEGORY, TREASURY_SYMBOL, TREASURY_SYMBOL_ID, ALC_CODE, and ACCOMPLISH_DATE describe the nature and agency ownership of each transaction line. REPORTED_FLAG, REPORTED_GL_PERIOD, REPORTED_MONTH, and SF224_PROCESSED_FLAG track reporting status across periods.
• Amounts and dates: AMOUNT, ACTUAL_AMOUNT, GL_DATE, POSTED_DATE, GL_PERIOD, DEFAULT_PERIOD_NAME, START_PERIOD_DATE, and END_PERIOD_DATE provide the financial and period context used to build the SF-224 statement.

The table includes standard EBS audit and concurrency columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_REQUEST_ID, UPDATED_REQUEST_ID) plus ORGANIZATION_ID and DEF_ORG_ID for multi-organization security. No surrogate primary key is published in the documentation; JE_BATCH_ID combined with JE_HEADER_ID and JE_LINE_NUM is the practical business-key candidate for identifying a line.

Common Use Cases and Queries

Typical usage centers on exception review, reconciliation, and re-run control during SF-224 processing. Analysts query the table to isolate records flagged with EXCEPTION_EXISTS or EXCEPTION_CATEGORY before publishing the statement. A representative pattern:

SELECT je_batch_id, treasury_symbol, d_r_flag, amount
  FROM   fv.fv_sf224_temp
 WHERE  federal_rpt_id = :rpt_id
   AND  reported_flag  = 'N'
   AND  set_of_books_id = :sob_id;

Reconciliation queries join back to GL_JE_BATCHES and GL_JE_HEADERS to confirm the extracted batches were posted and to verify amounts. Processes may also sweep rows by SF224_PROCESSED_FLAG = 'N' to determine what remains to be reported in the current cycle. Because the table is a temporary work area, its contents are typically purged or refreshed on each reporting run.

Related Objects

• GL_SETS_OF_BOOKS_11I — joined on FV_SF224_TEMP.SET_OF_BOOKS_ID to identify the ledger.
• GL_JE_BATCHES — joined on FV_SF224_TEMP.JE_BATCH_ID to reach the source journal batch.
• FV_REPORT_DEFINITIONS — joined on FV_SF224_TEMP.FEDERAL_RPT_ID to identify the report definition.
• GL_JE_HEADERS and GL_JE_LINES — used with JE_HEADER_ID and JE_LINE_NUM for source-line verification.
• FV_SF224 and related SF-224 staging objects — the destination and companion structures populated from this table.
• GL_CODE_COMBINATIONS — reached via ACCOUNT for fund and agency validation.