Search Results fnd_lob_access




Overview
Explore in AI Chat

Overview

The FND_LOB_ACCESS table is a core data object within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the primary access control and tracking mechanism for the Generic File Manager (GFM). The GFM is a centralized framework for managing Binary Large Objects (BLOBs) and Character Large Objects (CLOBs) within the EBS architecture, such as file attachments, documents, and other unstructured data. This table is owned by the APPLSYS schema and is responsible for logging and regulating access events to these stored LOBs, ensuring a secure and auditable trail of interactions with file data managed by the system.

Key Information Stored

The table's structure is designed to record discrete access instances. Its primary key is ACCESS_ID, which uniquely identifies each access event. A critical foreign key relationship exists via the FILE_ID column, which references the FND_LOBS table. FND_LOBS is the master repository storing the actual LOB locators and metadata. Therefore, each record in FND_LOB_ACCESS is linked to a specific file in FND_LOBS. While the provided ETRM excerpt does not list all columns, typical data stored in such an access table includes timestamps of access, the identifier of the user or concurrent program initiating the action, the type of operation performed (e.g., READ, DOWNLOAD, UPDATE), the session or module from which the access originated, and potentially the IP address or machine name for enhanced auditing.

Common Use Cases and Queries

The primary use case for FND_LOB_ACCESS is auditing and security analysis. System administrators and auditors query this table to monitor file usage, investigate data access patterns, or comply with regulatory requirements. Common reporting queries include identifying all accesses to a specific document, tracking file download activity by user over a date range, or listing the most frequently accessed files. A fundamental sample query would join to the master FND_LOBS table to retrieve meaningful file details.

  • Sample Query: SELECT fl.file_name, fl.file_data_type, fl.upload_date, fla.access_date, fla.accessor FROM apps.fnd_lob_access fla, apps.fnd_lobs fl WHERE fla.file_id = fl.file_id AND fl.file_name LIKE '%CONTRACT%' ORDER BY fla.access_date DESC;
  • Use Case: Generating an audit report for all accesses to files containing "CONTRACT" in their name.

Related Objects

FND_LOB_ACCESS has a direct and essential relationship with the FND_LOBS table, which is enforced by a foreign key constraint. FND_LOBS contains the core file metadata and LOB locators, while FND_LOB_ACCESS records the transactional history against those files. This table is intrinsically linked to the Generic File Manager's internal APIs and user interfaces, which populate it whenever a managed file is accessed. Other related objects may include FND_DOCUMENTS and application-specific attachment tables, which often store pointers to file IDs in FND_LOBS, thereby creating a logical chain: application table -> FND_LOBS -> FND_LOB_ACCESS for complete file tracking.