Search Results datatype_name




Overview
Explore in AI Chat

Overview

APPS.POR_ATTACHMENTS_SUMMARY_V is a reporting view in Oracle E-Business Suite that exposes attachment metadata associated with purchasing (POR) entities. It acts as a thin projection layer over the Oracle Application Object Library attachment infrastructure, presenting document attachment details in a form suited for inquiry, reporting, and integration. The view is owned by the APPS schema and is available in both EBS 12.1.1 and 12.2.2.

The view is defined as a single SELECT statement that projects selected columns from FND_ATTACHED_DOCS_FORM_VL, appending a literal space character as a final column. It does not persist data; it is a read-only query construct. Because it inherits the language-dependent behavior of FND_ATTACHED_DOCS_FORM_VL, display values reflect the current session language.

The column name searched—datatype_name—is central to the view's purpose. It identifies the attachment category type (for example, file, URL, or text) so that consumers can determine how the attached document is stored and how it should be rendered.

Underlying Base Objects

The documented reference lists a single underlying object: FND_ATTACHED_DOCS_FORM_VL, which is itself a view. No base tables are directly referenced in the ETRM metadata for this object. FND_ATTACHED_DOCS_FORM_VL is the standard Application Object Library construct that joins the attachment association table (FND_ATTACHMENTS) with the document entity table (FND_DOCUMENTS) and resolves category and datatype descriptions through FND_DOCUMENT_CATEGORIES_VL and FND_DOCUMENT_DATATYPES.

POR_ATTACHMENTS_SUMMARY_V therefore inherits all filtering, security, and language handling applied by FND_ATTACHED_DOCS_FORM_VL. Any change to that underlying view is reflected immediately in POR_ATTACHMENTS_SUMMARY_V. Because the parent view is a _VL (view with language) object, translated columns such as category_description and datatype_name are returned according to the language of the querying session.

Key Columns

  • seq_num – Sequence number used to order multiple attachments belonging to the same parent record.
  • category_description – Language-dependent description of the attachment category (for example, "To Supplier" or "Internal").
  • datatype_id – Foreign-key identifier for the attachment datatype.
  • datatype_name – Language-dependent name of the datatype, indicating how the document is stored, such as File, URL, or Short Text. This is the column referenced in the user's search.
  • document_description – Free-text description entered by the attaching user.
  • function_name – The application function or form from which the attachment was created.
  • entity_name – The entity context to which the attachment belongs, such as a purchasing document or supplier record.
  • pk1_value / pk2_value – Primary-key value pairs that link the attachment back to its owning business entity.
  • attached_document_id – Identifier of the attachment association record.
  • media_id – Identifier of the stored media or document content.
  • file_name – Name of the attached file, where applicable.
  • (literal ' ') – A constant space column appended by the view definition, typically used as a placeholder for form or report layout purposes.

Common Use Cases and Queries

The view is typically queried to enumerate attachments for purchasing-related entities and to classify them by datatype. A common pattern filters on entity_name and pk1_value to retrieve the attachments belonging to a specific document.

Sample query listing attachment metadata for a given entity key:

SELECT seq_num,
       category_description,
       datatype_name,
       document_description,
       function_name,
       entity_name,
       pk1_value,
       pk2_value,
       file_name
  FROM apps.por_attachments_summary_v
 WHERE entity_name = :p_entity
   AND pk1_value   = :p_pk1
 ORDER BY seq_num;

Sample query counting attachments grouped by datatype, useful for auditing storage usage:

SELECT datatype_name, COUNT(*) attachment_count
  FROM apps.por_attachments_summary_v
 GROUP BY datatype_name;

Because the view is read-only and language-sensitive, it is suited to reporting and integration use rather than transactional inserts or updates. Applications requiring attachment maintenance should operate on the underlying FND_ATTACHMENTS and FND_DOCUMENTS tables through the supported Application Object Library APIs.