Search Results wip_entity_comments_v




Overview
Explore in AI Chat

Overview

WIP_ENTITY_COMMENTS_V is an APPS-owned view in the Work in Process (WIP) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes attachments that have been associated with WIP entities — discrete jobs and repetitive schedules — by joining Oracle's generic attachment framework (FND) to the Work in Process execution model. The view returns one row per attached document, carrying the WIP entity identifier, the owning organization, the attachment description, and the standard FND descriptive flexfield (DFF) attribute columns and audit fields.

Its primary role is to make WIP shop-floor attachments queryable in a denormalized, WIP-centric form. Because attachments in EBS are stored generically in FND_ATTACHED_DOCUMENTS using a polymorphic entity/PK model, consumers cannot easily determine which job or schedule an attachment belongs to without decoding the key segments. This view performs that decoding and filters to a single document category, WIP_ENTITY_ATTACHMENTS, so that only WIP execution attachments are returned. It is used for reporting, data migration, and integration extracts rather than for transaction entry.

Underlying Base Objects

The view is defined over three referenced objects:

Joins are mandatory (comma-style inner joins), so only attached documents with a resolvable document and category row are returned. In the documented metadata, FND_ATTACHED_DOCUMENTS appears as a synonym, while the two FND objects are views; no WIP base table is directly referenced, which confirms that the source of truth for these comments is the FND attachment layer keyed by WIP entity name.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all attachments for a discrete job, auditing attachments by organization, and extracting comment text for integrations or migrations. The COMMENT_CODE column is frequently referenced because it holds the human-readable attachment description.

Attachments for a specific discrete job:

  • SELECT wip_entity_id, organization_id, comment_code, creation_date FROM apps.wip_entity_comments_v WHERE wip_entity_id = :job_id AND repetitive_schedule_id IS NULL;

All WIP attachments within an organization:

  • SELECT wip_entity_id, comment_code FROM apps.wip_entity_comments_v WHERE organization_id = :org_id ORDER BY creation_date DESC;

Searching by comment text:

  • SELECT wip_entity_id, organization_id, comment_code FROM apps.wip_entity_comments_v WHERE comment_code LIKE '%HOLD%';

Because the view is read-only and built on FND attachment objects, queries should be run with APPS or a reporting responsibility, and DFF columns returned should be interpreted according to the WIP_ENTITY_ATTACHMENTS category's flexfield setup.