Search Results doc_attribute_category




Overview
Explore in AI Chat

Overview

ECE_ATTACHMENT_V is a reporting and integration view owned by the APPS schema within the Oracle E-Business Suite e-Commerce Gateway (EC) module. Its purpose is to extract attachment data associated with outbound Purchasing transactions, specifically the outbound Purchase Order (850/ORDERS) and the outbound Purchase Order Change (860/ORDCHG) transaction sets. The view consolidates attachment information that may be attached at multiple levels of the purchasing document hierarchy, including header, line, shipment, distribution, item, and master item levels.

In ETRM 12.1.1 and 12.2.2, this object carries a VALID status and is used by the e-Commerce Gateway extraction logic to assemble the attachment payload transmitted to trading partners. Because attachments are stored generically in the FND document framework, this view normalizes the relationship between a purchasing document, its attachment association records, and the underlying attachment content. The view references the user's current language session (USERENV('LANG')), so category descriptions are returned in the session language, and it filters on DATATYPE_ID = 1 in the primary branch, which corresponds to short-text document content.

Underlying Base Objects

The view is defined over six documented base objects. Four are referenced as synonyms in APPS: FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS, FND_DOCUMENTS_LONG_TEXT, and FND_DOCUMENTS_SHORT_TEXT. Two are language-aware definitions: FND_DOCUMENTS_VL, which is a view, and FND_DOCUMENT_CATEGORIES_TL, a translation table for document category names.

The joins establish the core relationships:

  • FND_ATTACHED_DOCUMENTS (FAD) — links an attachment to its owning entity via ENTITY_NAME and the PK1_VALUE through PK5_VALUE pivot columns, and supplies ATTACHED_DOCUMENT_ID and SEQ_NUM.
  • FND_DOCUMENTS (FDD) — the master attachment record, joined to FAD on DOCUMENT_ID and restricted by DATATYPE_ID.
  • FND_DOCUMENTS_VL (FDT) — provides the description and DOC_ATTRIBUTE1 through DOC_ATTRIBUTE15 descriptive flexfield columns.
  • FND_DOCUMENTS_SHORT_TEXT / FND_DOCUMENTS_LONG_TEXT (FDS/FDL) — hold the actual short-text and long-text content, outer-joined in the first branch, with the long-text join additionally constrained by FDL.MEDIA_ID(+) = -9999. FDL and FDS relate through a shared MEDIA_ID.
  • FND_DOCUMENT_CATEGORIES_TL (FDC) — supplies the translated CATEGORY_NAME and LANGUAGE, joined on CATEGORY_ID.

Key Columns

  • DOCUMENT_ID — the attachment document identifier from FND_DOCUMENTS, the key searched term's parent context.
  • ATTACHED_DOCUMENT_ID — the identifier of the attached document record from FND_ATTACHED_DOCUMENTS, the column most often searched directly.
  • ENTITY_NAME — the owning entity type (e.g., header, line, shipment, distribution).
  • PK1_VALUE … PK5_VALUE — the key values locating the attachment's parent purchasing record.
  • CATEGORY_NAME / LANGUAGE — the translated document category and its language.
  • DATATYPE_ID / USAGE_TYPE — content type discriminator and usage classification.
  • SHORT_TEXT / LONG_TEXT — the textual attachment body.
  • DESCRIPTION and DOC_ATTRIBUTE_CATEGORY, DOC_ATTRIBUTE1-15 — descriptive flexfield context and values.
  • ATT_SEQ_NUM — the sequence number of the attachment association.

Common Use Cases and Queries

Typical scenarios include verifying that PO attachments will be exported in an 850 or 860 transmission, diagnosing missing attachments on a specific order, and reconciling attached-document identifiers during integration troubleshooting.

To locate an attachment by its identifier:

  • SELECT document_id, attached_document_id, entity_name, category_name, pk1_value, short_text FROM apps.ece_attachment_v WHERE attached_document_id = :p_id;

To list header-level PO attachments:

  • SELECT pk1_value po_number, category_name, description FROM apps.ece_attachment_v WHERE entity_name = 'PO_HEADERS' ORDER BY pk1_value;

To review all attachments for a given transaction level, query by ENTITY_NAME and PK1_VALUE, returning DOC_ATTRIBUTE columns for any flexfield context. Because the view resolves category text by session language and relies on outer joins for text content, queries should anticipate null SHORT_TEXT or LONG_TEXT values for non-text media.