Search Results blk_dtl




Overview

FV_FACTS_EDIT_CHECK is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Funds Validation (FV) module used by federal agencies to prepare and submit Treasury reporting data. It belongs to the FACTS (Financial Analysis and Control System) family of objects that manage the edit-checking and validation of reported financial data before submission to Treasury. The package is classified as OTHER in the ETRM 12.2.2 documentation, meaning it is not a public API but an internal business logic component invoked by other FV packages and processes.

The primary business role of the package is to execute a series of numbered edit checks against facts rows staged in the temporary table FV_FACTS_TEMP. These edit checks validate budgetary and proprietary account balances — including debit/credit ending balances for SGL accounts beginning with the prefix "4" — and record the outcome in the edit-check status table. A secondary function is logging and diagnostic recording, supported by internal helper routines such as Create_log_record and create_status_record, and an initialization routine (init_vars) that resets global variables such as the treasury symbol ID, edit-check number, edit-check status, and accumulated amount variables before each check executes.

The source header indicates the package body carries a revision line (B.pls 120.14) and a modification history dating to older releases, with a comment crediting an internal developer for a logging enhancement. The internal cursors are keyed against the treasury symbol identifier and filter on record category "REPORTED_NEW", record type "BLK_DTL", and ending balance rows.

Because the user search term is "blk_dtl", the relevant anchor in this package is the cursor condition fct_int_record_type = 'BLK_DTL'. In FACTS processing, BLK_DTL denotes a "block detail" transaction or record type identifying detail-level reported facts that must be validated before aggregation and submission. The package therefore filters FV_FACTS_TEMP for BLK_DTL rows when performing its credit/debit balance edit checks.

Key Procedures and Functions

  • PERFORM_EDIT_CHECKS — The single documented public procedure, and the main entry point for the package. It drives the execution of the individual edit-check modules (such as edit_check_1, which evaluates credit and debit ending balances for budgetary SGL accounts), routes failures and diagnostics into the logging and status-recording helpers, and raises the module error flag when discrepancies are found.
  • Create_log_record — Internal logging procedure that writes diagnostic text, including the text captured from v_log_text and exception messages obtained via SQLERRM, using the FV_UTILITY logging facility.
  • create_status_record — Internal procedure that persists the outcome of an individual edit check (check number and status) into the edit-check status table for later reporting and review.
  • init_vars — Internal initialization procedure that resets all package-level counters and identifiers before each check, and handles exceptions using FV_UTILITY.LOG_MESG at the FND_LOG.LEVEL_UNEXPECTED level before re-raising the error.

Tables Accessed

Usage Notes

FV_FACTS_EDIT_CHECK is an internal package and is not intended to be called directly by custom code. It is referenced by one other package in the FV module, which drives it during the edit-check phase of the FACTS reporting cycle. It is typically invoked after facts data has been loaded or populated into FV_FACTS_TEMP and before submission to Treasury, either through the Funds Validation setup forms, a validation concurrent program, or programmatically from the parent package that orchestrates edit checking.

Because the package depends on the current treasury symbol context (g_treasury_symbol_id), the caller must set this context before invoking PERFORM_EDIT_CHECKS. Results are stored in FV_FACTS_EDIT_CHECK_STATUS for user review and remediation. Developers extending FV validation logic should use the documented tables and the module error and logging conventions rather than altering this package, which is shipped as an Oracle-owned object.