Search Results wip_comment_codes_v

Overview

WIP_COMMENT_CODES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under the Work in Process (WIP) product and presents the set of comment codes and their descriptive text that may be attached to WIP entities such as discrete jobs, repetitive schedules, and flow schedules. In practice, the view acts as the seeded lookup source for WIP attachment and comment functionality, allowing forms, reports, and integrations to resolve a comment code into human-readable text without querying the underlying Oracle Documents (FND) tables directly.

Because the view already joins the document definition, its short text, and the governing document category, it abstracts the multi-table structure of the FND document model. Consumers receive a flat, denormalized result set that is suitable for LOV definitions, concurrent program parameters, and ad hoc reporting against WIP transactions.

Underlying Base Objects

The view text joins three documented base objects:

• FND_DOCUMENTS_VL (VIEW, alias D) — the document header definition, supplying DESCRIPTION, SECURITY_ID, the DOC_ATTRIBUTE1 through DOC_ATTRIBUTE15 flexfield columns, and the audit columns.
• FND_DOCUMENTS_SHORT_TEXT (SYNONYM, alias T) — the media/short-text record, supplying SHORT_TEXT, joined on MEDIA_ID = D.MEDIA_ID.
• FND_DOCUMENT_CATEGORIES_VL (VIEW, alias C) — the category definition, joined on CATEGORY_ID = C.CATEGORY_ID.

The join is filtered so that only documents with DATATYPE_ID = 1, SECURITY_TYPE = 1, USAGE_TYPE = 'S', and PUBLISH_FLAG = 'N' are returned, and the category name must equal 'WIP_ENTITY_ATTACHMENTS'. This restricts the view to short-text, internal, unpublished documents belonging to the WIP entity attachments category.

Key Columns

• COMMENT_CODE — the identifier used by WIP forms and APIs to reference a specific comment.
• COMMENT_DESCRIPTION — the descriptive text of the comment code, derived from the document description.
• ORGANIZATION_ID — the inventory organization context for the comment code.
• SECURITY_ID — the security identifier associated with the underlying document.
• SHORT_TEXT — the short-text media content linked to the document.
• DOC_ATTRIBUTE_CATEGORY and DOC_ATTRIBUTE1..15 — descriptive flexfield context and segment values carried from the document definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns for auditing.
• APP_SOURCE_VERSION — a fixed NULL placeholder column exposed to satisfy the consuming interface.

Common Use Cases and Queries

Typical scenarios include populating a comment-code LOV on a WIP workbench, validating a comment code passed into a WIP API, and extracting the available comment text for a reporting layer. A representative query is:

• SELECT COMMENT_CODE, COMMENT_DESCRIPTION, ORGANIZATION_ID FROM APPS.WIP_COMMENT_CODES_V WHERE ORGANIZATION_ID = :org_id ORDER BY COMMENT_CODE;
• SELECT COMMENT_CODE, SHORT_TEXT FROM APPS.WIP_COMMENT_CODES_V WHERE COMMENT_CODE = :comment_code;
• SELECT c.COMMENT_CODE, c.COMMENT_DESCRIPTION, c.DOC_ATTRIBUTE1, c.DOC_ATTRIBUTE2 FROM APPS.WIP_COMMENT_CODES_V c WHERE c.DOC_ATTRIBUTE_CATEGORY IS NOT NULL;

The frequent association with FND_DOCUMENT_CATEGORIES_VL reflects the fact that WIP comment codes are governed by the WIP_ENTITY_ATTACHMENTS document category; any query restricting category membership should reference that view or the seeded category name. Because the view is not a table, no DML is permitted, and all joins should be treated as read-only metadata lookups.