Search Results wip_entity_attachments




Overview
Explore in AI Chat

Overview

APPS.WIP_ENTITY_COMMENTS_V is a reporting view in Oracle E-Business Suite (Release 12.1.1 and 12.2.2) that surfaces attachments and comments associated with Work in Process (WIP) entities. It consolidates data from the Oracle Attachments framework (FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS_VL, and FND_DOCUMENT_CATEGORIES_VL) and filters narrowly to WIP discrete jobs and repetitive schedules.

The view is the standard access point for retrieving WIP entity comments stored as attachments under the document category WIP_ENTITY_ATTACHMENTS. It is commonly used by shop-floor reports, work order dispatch sheets, and custom concurrent programs that print or export job-level notes. Because it joins the EBS Attachments infrastructure, it exposes metadata (creation/update audit fields, attribute columns, document descriptions) rather than the attachment file itself.

Underlying Base Objects

Per the ETRM metadata, the view is defined over three referenced objects:

  • FND_ATTACHED_DOCUMENTS (SYNONYM) — the primary source (alias FAD) that stores the link between an entity (here, a WIP job or repetitive schedule) and a document, and carries the PK1/PK2/PK3 columns and descriptive flexfield ATTRIBUTEn columns.
  • FND_DOCUMENTS_VL (VIEW) — the multilingual document definition (alias D); its DESCRIPTION supplies the view's COMMENT_CODE column.
  • FND_DOCUMENT_CATEGORIES_VL (VIEW) — the category definition (alias C), used in the WHERE clause to restrict results to the category named WIP_ENTITY_ATTACHMENTS.

The PK columns in FND_ATTACHED_DOCUMENTS are decoded based on ENTITY_NAME: for WIP_DISCRETE_JOBS, PK1 is the WIP entity and PK2 is the organization; for WIP_REPETITIVE_SCHEDULES, PK1 is the WIP entity, PK2 is the repetitive schedule, and PK3 is the organization.

Key Columns

Common Use Cases and Queries

Typical uses include printing remarks on work order travelers, feeding external MES/integration layers with job comments, and auditing attachment activity on WIP entities.

  • List all comments for a discrete job, scoped by organization.
  • Report repetitive schedule comments where REPETITIVE_SCHEDULE_ID is not null.
  • Audit who created or last modified a WIP comment.

Sample SQL:

SELECT wip_entity_id, organization_id, repetitive_schedule_id,
       comment_code, last_update_date, last_updated_by
 FROM apps.wip_entity_comments_v
 WHERE organization_id = :org_id
   AND wip_entity_id = :wip_entity_id;

For repetitive schedules:

SELECT wip_entity_id, repetitive_schedule_id, comment_code
 FROM apps.wip_entity_comments_v
 WHERE repetitive_schedule_id IS NOT NULL
   AND organization_id = :org_id;

Because the view reads the FND attachment tables directly, joins to WIP_DISCRETE_JOBS or WIP_REPETITIVE_SCHEDULES are recommended to confirm entity status and to combine comments with shop-floor scheduling data.