Results for “fnd_documents_short_text”

50+ results




Overview
Explore in AI Chat

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

Overview

FND_DOCUMENTS_SHORT_TEXT is a table in the APPLSYS schema owned by the FND — Application Object Library product within Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the short text payload of "short text documents," one of the several media types that the Oracle EBS document management (Attachments) framework supports. When a user attaches a free-form note or a block of text to a business entity — an invoice, a purchase order, a journal entry, an employee record — the text itself is persisted here rather than in the generic document metadata table.

The table anchors the storage side of the attachment architecture. FND_DOCUMENTS_TL holds the descriptive, translatable metadata about each document (title, description, usage type), while FND_DOCUMENTS_SHORT_TEXT holds the actual short-text content keyed by the same MEDIA_ID. This separation allows the framework to support numerous media types — short text, long text (LONG_TEXT), files (FILE), URLs (URL), and images (IMAGE) — under a single logical document model.

Relationship metadata classifies this object as hub-leaning under a heuristic Data Vault assessment. In modeling terms, that suggests FND_DOCUMENTS_SHORT_TEXT behaves as a hub-like entity: it owns a stable business key (MEDIA_ID) and is referenced by dependent tables, rather than acting as a pure satellite or an associative link. This is a suggestion derived from FK topology, not a declared Oracle design.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains three columns. Because the table is narrow, the important attributes are correspondingly few:

  • MEDIA_ID — The surrogate primary key and the single column comprising FND_DOCUMENTS_SHORT_TEXT_PK. It uniquely identifies the short-text payload and is the join key to the document framework.
  • SHORT_TEXT — The stored textual content of the attachment. This is the substantive payload of the row; for short-text media type the value is constrained to the short-text length limit enforced by the document framework.
  • APP_SOURCE_VERSION — A version or source identifier used by the application layer to track the source release context of the row, supporting upgrade and compatibility processing.

Only MEDIA_ID is a documented business-key candidate via the unique index FND_DOCUMENTS_SHORT_TEXT_U1. No other unique index is documented, so MEDIA_ID is both the surrogate PK and the only candidate business key in the exposed schema.

Common Use Cases and Queries

The most common operational need is to resolve the text of an attachment for a given entity. This requires traversing the document framework from the entity–document association down to the payload:

  • Retrieve short text for a specific media: SELECT s.SHORT_TEXT FROM APPLSYS.FND_DOCUMENTS_SHORT_TEXT s WHERE s.MEDIA_ID = :media_id;
  • Join descriptive metadata to content: SELECT t.TITLE, s.SHORT_TEXT FROM APPLSYS.FND_DOCUMENTS_TL t, APPLSYS.FND_DOCUMENTS_SHORT_TEXT s WHERE t.MEDIA_ID = s.MEDIA_ID AND t.LANGUAGE = USERENV('LANG');
  • Audit attachments by source version to identify rows created under a prior application release: filter or group by APP_SOURCE_VERSION.
  • Reporting the volume of text attachments per media type by counting rows keyed by MEDIA_ID against FND_DOCUMENTS_TL.DOCUMENT_TYPE or media category.

Because MEDIA_ID is a narrow numeric key, joins against document-association tables (FND_ATTACHED_DOCUMENTS, FND_DOCUMENT_ENTITIES) perform efficiently and are typical in attachment-based reporting.

Related Objects

The documented FK relationship is the anchor point. The most significant related objects are:

  • FND_DOCUMENTS_TL — Referenced parent table; join on FND_DOCUMENTS_TL.MEDIA_ID = FND_DOCUMENTS_SHORT_TEXT.MEDIA_ID. Holds title, description, and translatable metadata. This is the sole documented foreign-key relationship, with FND_DOCUMENTS_TL as the referencing (foreign) table and FND_DOCUMENTS_SHORT_TEXT as the referenced table.
  • FND_DOCUMENTS — Base document definition table supplying document-level attributes and the media category that determines whether content resides in FND_DOCUMENTS_SHORT_TEXT versus LONG_TEXT, FILE, or URL tables.
  • FND_ATTACHED_DOCUMENTS — Associates a document with an entity instance (invoice, PO, journal) and ultimately points to the media record via MEDIA_ID.
  • FND_DOCUMENT_ENTITIES — Defines the entity types to which documents can be attached, governing how short-text content is surfaced in the UI.
  • FND_DOCUMENTS_LONG_TEXT — Parallel payload table for long-text documents, useful in any query that enumerates all text-based media.
  • FND_DOCUMENTS_TYPES_TL — Defines document/usage types that control how short text is categorized.

Queries spanning these objects should always key on MEDIA_ID to preserve the integrity established by FND_DOCUMENTS_SHORT_TEXT_PK and its enforced unique index.