Search Results comment_description

Overview

APPS.WIP_COMMENT_CODES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered in the FND Design Data repository under the internal identifier WIP.WIP_COMMENT_CODES_V. It exposes the comment code definitions used by Oracle Work in Process (WIP) to categorize the free-text comments attached to discrete jobs, repetitive schedules, and shop floor transactions. The view carries a status of VALID and has an object type of VIEW, meaning it is a stored query rather than a physical table.

In Oracle EBS 12.1.1 and 12.2.2, the view is the primary reporting and integration surface for comment code setup. Each row represents one comment code belonging to a specific organization, and the view supplies the code value together with its descriptive text, descriptive flexfield context, attribute segments, and standard WHO audit columns. The view is documented as Oracle Internal Use Only; Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Report developers and integration architects should therefore treat it as a read-only construct and avoid DML against it.

Underlying Base Objects

Per the documented view metadata, WIP_COMMENT_CODES_V is defined over the following referenced objects:

• FND_DOCUMENTS_SHORT_TEXT (SYNONYM) — the short-text storage segment that holds the actual comment description body for a document record.
• FND_DOCUMENTS_VL (VIEW) — the language-enabled view over the FND_DOCUMENTS entity, supplying the document identity, category, and language context.
• FND_DOCUMENT_CATEGORIES_VL (VIEW) — the language-enabled view over document categories, used to constrain the underlying document set to the WIP comment category.

The view therefore does not select from a dedicated WIP table. Instead, it resolves WIP comment definitions through the common Oracle Attachment and document infrastructure, joining document metadata to its short-text body and filtering by the appropriate document category. This architecture explains why COMMENT_DESCRIPTION is stored as a long description rather than a short code name: the free-text body lives in the short-text segment, while the code identity is carried on the document record.

Key Columns

• COMMENT_CODE (VARCHAR2, 255) — the comment code value, used as the reference key when a comment type is selected on a WIP transaction or job.
• ORGANIZATION_ID (NUMBER) — the inventory organization in which the comment code is defined, supporting multi-org filtering and security.
• COMMENT_DESCRIPTION (VARCHAR2, 4000) — the detailed description of the comment type; this is the column most frequently targeted when users search on "comment_description".
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide auditability for each row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield administrative context and segment columns, available for user-defined extensions.
• APP_SOURCE_VERSION — an unused column retained for backward compatibility.

Common Use Cases and Queries

The most common requirement is to list the comment codes and their descriptions for a given organization, typically for validation extracts or LOV reconciliation.

SELECT comment_code, comment_description
FROM   apps.wip_comment_codes_v
WHERE  organization_id = :org_id
ORDER  BY comment_code;

Integrations that populate or verify WIP comments join this view to job or transaction data to resolve the human-readable text. A search on "comment_description" is usually a lookup or a text match against the description body:

SELECT comment_code, comment_description
FROM   apps.wip_comment_codes_v
WHERE  UPPER(comment_description) LIKE '%SCRAP%';

Because the object is documented as Oracle Internal Use Only, all access should be read-only and sourced from custom reporting schemas or views rather than embedded directly in unsupported transactional logic.