Results for “fnd_documents_long_text”

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

Overview

FND_DOCUMENTS_LONG_TEXT is a table owned by the APPLSYS schema within the Oracle E-Business Suite Application Object Library (FND) product family. It stores long text document content associated with attachments and media records registered in the Oracle EBS document management framework. In both release 12.1.1 and 12.2.2 the object carries a VALID status and is documented in the ETRM repository as "Long text documents."

The table functions as the persistence layer for the actual character payload of text-based attachments — the narrative content behind an attachment a user views when opening a text document from the Attachments form, a Web ADI upload, or an OAF page. Rather than storing text inline in the metadata table, EBS separates descriptive attributes (FND_DOCUMENTS_TL) from the binary or character body, and FND_DOCUMENTS_LONG_TEXT holds the character body.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. It is keyed on a single surrogate identifier, MEDIA_ID, which is referenced from the descriptive table, making it behave like a hub of media identities rather than a pure satellite or link.

Key Information Stored

The documented physical schema contains three columns. The most significant are:

• MEDIA_ID — The surrogate primary key column. It is the single attribute comprising the primary key FND_DOCUMENTS_LONG_TEXT_PK and the unique index FND_DOCUMENTS_LONG_TEXT_U1. MEDIA_ID identifies the media record whose text body is stored here and is the value propagated to dependent tables such as FND_DOCUMENTS_TL.
• LONG_TEXT — The character payload holding the actual long text document content. In the EBS data model this is the column that carries the readable attachment text surfaced to end users.
• APP_SOURCE_VERSION — A version indicator associated with the source application context, used to track the applicable application release or definition version under which the long text row was created.

Because the primary key and the business-key candidate (FND_DOCUMENTS_LONG_TEXT_U1) both resolve to MEDIA_ID, the surrogate identity of a row coincides with the media identifier used throughout the attachment subsystem. The additional unique index listed, SYS_IL0000034992C00003$$, is an Oracle-maintained LOB index rather than a business key, reflecting the large-object storage typical of long text columns.

Common Use Cases and Queries

Reporting and integration scenarios for this table generally revolve around retrieving, auditing, or migrating attachment text. A representative pattern joins the long text body to the translated document metadata:

• Attachment content retrieval — Joining FND_DOCUMENTS_LONG_TEXT to FND_DOCUMENTS_TL on MEDIA_ID to obtain both the descriptive fields and the text body for a given document.
• Text migration and archival — Extracting MEDIA_ID and LONG_TEXT for bulk export of attachment content during a data archiving or cloud migration project.
• Audit and version review — Comparing APP_SOURCE_VERSION values to assess which application release produced a given long text record.
• Orphan detection — Identifying MEDIA_ID rows in the long text table that lack a corresponding row in FND_DOCUMENTS_TL, a common data-integrity check after patching.

Queries should treat LONG_TEXT as a LOB-type column and avoid implicit character conversions in predicates, since the value may exceed ordinary VARCHAR2 limits.

Related Objects

The most significant related object is FND_DOCUMENTS_TL, which references this table through the column MEDIA_ID (documented as FND_DOCUMENTS_TL.MEDIA_ID → FND_DOCUMENTS_LONG_TEXT). This is the primary join path and the source of most access into the long text table. The parent metadata for attachments is carried in the FND documents family, so queries typically traverse from a base documents table into FND_DOCUMENTS_TL for translated descriptions and then into FND_DOCUMENTS_LONG_TEXT for the actual text body, joining each step on MEDIA_ID. The unique index on MEDIA_ID enforces the one-to-one relationship between a media record and its long text payload, making MEDIA_ID the consistent join key across the attachment table family.