Results for “datatype_id”

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

Overview

PO_ECX_ATTACHMENTS_V is a Purchasing (PO) module database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name reflects its purpose: it exposes Purchasing attachments in a flattened form consumable by Oracle E-Commerce Gateway (ECX) processing, particularly for outbound purchasing documents such as purchase orders that must carry vendor-related attachments. Rather than presenting attachments broadly, the view filters strictly to documents belonging to the VENDOR category, joining language-specific translation tables so that only the session-language description of each attachment is surfaced. The result is a lightweight, read-only projection intended for reporting and integration consumption rather than transactional maintenance. Because the view is status VALID in ETRM, it can be relied upon as a stable interface in both 12.1.1 and 12.2.2 environments, though the presence of the FND_DOCUMENTS_VL view in the 12.2.2 metadata signals the underlying multi-language object model that is characteristic of the later release.

Underlying Base Objects

The view is defined over five core FND objects, most accessed through APPS synonyms. FND_DOCUMENT_DATATYPES supplies datatype metadata (the source of DATATYPE_ID and the attached-document-type name). FND_DOCUMENTS holds the master document rows that map a document to its datatype and category. FND_DOCUMENT_CATEGORIES_TL provides the translated category names, constrained here to 'VENDOR' and to the user's current language. FND_DOCUMENTS_TL supplies the translated document name/media identifier, and FND_ATTACHED_DOCUMENTS links each document to its owning entity via ENTITY_NAME and PK1_VALUE. In 12.2.2, FND_DOCUMENTS_VL appears as a referenced view, reflecting the standardized multi-language view pattern; the conformance of the join to USERENV('LANG') in each translation table preserves correct language selection. The join conditions enforce category = 'VENDOR', a non-null MEDIA_ID (excluding purely textual or URL attachments), and language consistency across all translation aliases.

Key Columns

• MEDIA_ID — The media identifier of the attached document, sourced from FND_DOCUMENTS_TL. The predicate DT.MEDIA_ID IS NOT NULL guarantees only file-based attachments are returned.
• DATATYPE_ID — The identifier of the document datatype from FND_DOCUMENT_DATATYPES, which uniquely classifies the attachment's document type and is the join key to the datatype definition.
• ATTACHED_DOCUMENT_TYPE — The translated name of the datatype (DAT.NAME), providing a human-readable label for the attachment kind.
• ATTACHMENT_PK1 — The primary key value of the owning entity, taken from FND_ATTACHED_DOCUMENTS.PK1_VALUE, which identifies the specific record (for example, a vendor or vendor site) to which the attachment is bound.
• ATTACHMENT_ENTITY_NAME — The entity name from FND_ATTACHED_DOCUMENTS identifying the owning object type, allowing the consumer to resolve the attachment back to its source record.

Common Use Cases and Queries

The view is typically queried when extracting vendor-linked attachment metadata for interfaces, data conversion, or audit reporting. A representative query lists attachments for a given vendor entity:

• SELECT media_id, datatype_id, attached_document_type, attachment_pk1 FROM po_ecx_attachments_v WHERE attachment_entity_name = 'VENDOR' AND attachment_pk1 = :vendor_id;
• SELECT attached_document_type, COUNT(*) FROM po_ecx_attachments_v GROUP BY attached_document_type;

Because the view already restricts to the VENDOR category and to file-backed media, no additional category filtering is required by callers. Practical scenarios include populating interface staging tables for E-Commerce Gateway outbound documents, verifying which attachments exist for a vendor before a payment or supplier integration run, and reconciliation reporting where attachment presence must be confirmed against supplier master data. The DATATYPE_ID column is frequently used as the pivot for classifying attachments by type in such reports.