Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

layout default
title FND Application Context File | Oracle EBS SQL Report
description Context XML files retrieved from the database – Oracle E-Business Suite SQL report
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Enginatics, FND, Application, Context, File, fnd_oam_context_files
permalink /FND%20Application%20Context%20File/

FND Application Context File – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Context XML files retrieved from the database

Report Parameters

Oracle EBS Tables Used

fnd_oam_context_files

Report Categories

Enginatics

Related Reports

XDO Publisher Data Definitions, AD Applied Patches, CST Inventory Value - Multi-Organization (Element Costs) 11i, AD Applied Patches 11i, DBA Tablespace Usage, Blitz Report Templates, DBA Blocking Sessions, AR Transactions and Lines

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output FND Application Context File 06-Jul-2019 174000.xlsx
Blitz Report™ XML Import FND_Application_Context_File.xml
Full SQL on Enginatics www.enginatics.com/reports/fnd-application-context-file/

Executive Summary

The FND Application Context File report retrieves the content of the Oracle E-Business Suite context file directly from the database. This file contains critical configuration details about the environment, such as port numbers, hostnames, and directory paths.

Business Challenge

  • Configuration Management: Keeping track of environment-specific configurations without logging into the OS.
  • Troubleshooting: Quickly checking parameter values (e.g., s_web_port) during system issues.
  • Cloning Verification: Verifying that context variables were correctly updated after a clone.

The Solution

This Blitz Report provides immediate access to the context file:

  • Database Access: Reads the XML stored in FND_OAM_CONTEXT_FILES, eliminating the need for shell access.
  • Version History: Can potentially show previous versions of the context file if they are stored in the history table.
  • Searchability: The output can be searched in Excel for specific variable names.

Technical Architecture

The report queries FND_OAM_CONTEXT_FILES. This table is populated by the adautocfg.sh (AutoConfig) process. The report typically retrieves the most recent active file.

Parameters & Filtering

  • None: Typically runs for the current environment.

Performance & Optimization

  • Data Size: The context file is a large XML CLOB. The report handles this by extracting relevant fields or downloading the full content.

FAQ

  • Q: Can I edit the context file here?
    • A: No, this is a read-only report. Changes must be made via the Oracle OAM dashboard or by editing the XML file on the OS and running AutoConfig.
  • Q: Why is the table empty?
    • A: If AutoConfig has never been run or the feature to upload the context file to the database is disabled, this table might be empty.

Useful Links

© 2026 Enginatics