Results for “adi_kiosk_image”

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

Overview

The APPS.ADI_WEB_FILES_VL view is a denormalized reporting and integration object within Oracle E-Business Suite, exposed in the APPS schema in both release 12.1.1 and 12.2.2. Its purpose is to present the binary content of web-deliverable files — specifically kiosk-related images — alongside descriptive metadata derived from the FND Documents data model. Rather than querying the generic document tables directly, consumers can select from this view to obtain a single flat result set combining document identifiers, filenames, MIME descriptions, declared sizes, and the raw file payload.

The view is restricted by design. It does not expose all documents held in the FND Documents repository; it returns only those records whose document category resolves to one of two named values: ADI_KIOSK_IMAGE or ADI_KIOSK_DEFAULT_LOGO. This constraint reflects the view's origin as a delivery mechanism for the Oracle Applications Desktop Integrator (ADI) kiosk image and default logo files. A user searching for the term adi_kiosk_default_logo is effectively searching for the category name that governs which rows this view returns, rather than a column value or a primary key.

Underlying Base Objects

The view text is defined as a three-way join across the following documented objects:

• FND_DOCUMENTS_VL (view) — aliased as D, supplying the document identifier, filename, description, media identifier, category identifier, and program identifier.
• FND_DOCUMENT_CATEGORIES_VL (view) — aliased as CL, supplying the category name used in the filtering predicate.
• FND_DOCUMENTS_LONG_RAW (synonym to the underlying raw content table) — aliased as LR, supplying the LONG_RAW content column that holds the actual binary or textual file payload.

The join conditions are D.MEDIA_ID = LR.MEDIA_ID and D.CATEGORY_ID = CL.CATEGORY_ID, with the row filter applied through CL.NAME IN ('ADI_KIOSK_IMAGE','ADI_KIOSK_DEFAULT_LOGO'). Because the content is stored in a LONG/LONG RAW column, the view inherits the limitations of that datatype, including restriction of certain SQL operations and a single LONG column per query.

Key Columns

• NAME — a synthetic identifier produced by concatenating the document identifier and the filename with an underscore separator (D.DOCUMENT_ID || '_' || D.FILE_NAME). This is not a natural key from any base table; it exists solely to give consumers a unique, readable handle.
• MIME_TYPE — mapped from D.DESCRIPTION rather than from a true MIME-type column. The value therefore reflects the document description stored in FND Documents and should not be assumed to be a standards-compliant MIME string.
• DOC_SIZE — mapped from D.PROGRAM_ID, again a repurposed column. It does not represent a computed byte length; it carries whatever value the originating document record holds in the program identifier field.
• CONTENT — the LR.LONG_RAW value containing the file body, suitable for streaming to a client or writing to a filesystem when extracted through an appropriate tool such as a concurrent program or a PL/SQL routine using DBMS_LOB.

Common Use Cases and Queries

The view is typically used to retrieve kiosk branding assets for display or to validate that required logo files have been loaded. A representative query listing the available assets follows:

• SELECT name, mime_type, doc_size FROM apps.adi_web_files_vl ORDER BY name;

To target the default logo specifically, filtering on the synthetic name or inspecting the underlying category provides the required row. Because the content column is LONG RAW, retrieval of CONTENT is normally performed through PL/SQL, a report, or an extraction concurrent program rather than through interactive tools that cannot render LONG values. Administrators troubleshooting missing kiosk imagery frequently confirm existence first with a metadata-only query, then extract CONTENT separately. The view is read-only and is not intended as a maintenance path; image and logo records are loaded and maintained through the standard FND Documents administration interfaces.