Search Results format_description




Overview
Explore in AI Chat

Overview

APPS.WMS_LABEL_SET_FORMATS_V is a reporting and integration view within the Oracle E-Business Suite Warehouse Management System (WMS) module. Its purpose is to present a resolved, human-readable representation of the association between label sets and the individual label formats that they contain. In WMS, a label set is a grouping construct that bundles one or more label formats, allowing a warehouse or shipping operation to print a consistent collection of labels in a single request. The underlying association table stores only numeric identifiers; the view enriches those identifiers by joining to the label format definitions on both sides of the relationship, exposing descriptive names and descriptions for the set as well as for each contained format. Because the view joins synonym targets owned by the WMS schema but is exposed under the APPS schema, it is directly available to custom reports, concurrent programs, BI Publisher data templates, and integration extracts that run with APPS credentials. The inclusion of the FORMAT_DESC column and its set-level counterpart SET_DESC makes the view particularly suited to environments where users search on descriptive text rather than internal IDs.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms: WMS_LABEL_FORMATS and WMS_LABEL_SET_FORMATS. WMS_LABEL_SET_FORMATS is the intersection table that records which label format belongs to which label set; it contributes the SET_ID, FORMAT_ID, DISABLE_DATE, and the standard WHO audit columns. WMS_LABEL_FORMATS appears twice, with aliases WLF1 and WLF2. Alias WLF1 supplies the label set header, since a label set is itself stored as a label format row bearing LABEL_ENTITY_TYPE = 1. Alias WLF2 supplies the individual label format rows, filtered by NVL(LABEL_ENTITY_TYPE,0) = 0, which distinguishes a printable format from a set definition. The join is therefore a self-join on WMS_LABEL_FORMATS through the association table, and all three sources are combined with an inner join, so only fully resolved set-to-format pairs are returned.

Key Columns

  • ROW_ID — the ROWID of the association row in WMS_LABEL_SET_FORMATS, useful for uniqueness and for locating the underlying record.
  • SET_ID — the label format identifier that represents the label set header (matches WLF1.LABEL_FORMAT_ID).
  • FORMAT_ID — the identifier of the member label format contained in the set (matches WLF2.LABEL_FORMAT_ID).
  • SET_DOCUMENT_ID — the document identifier associated with the label set header, taken from WLF1.DOCUMENT_ID.
  • DISABLE_DATE — the date on which the set-to-format association becomes inactive; a NULL value generally indicates an active association.
  • LABEL_SET_NAME — the descriptive name of the label set, from WLF1.LABEL_FORMAT_NAME.
  • SET_DESC — the description of the label set, from WLF1.FORMAT_DESCRIPTION.
  • LABEL_FORMAT_NAME — the descriptive name of the member label format, from WLF2.LABEL_FORMAT_NAME.
  • FORMAT_DESC — the description of the member label format, from WLF2.FORMAT_DESCRIPTION; this is the column most frequently used for text-based searching.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns carried from the association table.

Common Use Cases and Queries

Typical uses include listing the formats that make up a given label set, searching for sets by descriptive text, and driving label-printing programs that must resolve set membership before invoking a printer. To find all active members of a named set, a query might read:

SELECT label_set_name, label_format_name, format_desc FROM apps.wms_label_set_formats_v WHERE label_set_name = :p_set_name AND disable_date IS NULL ORDER BY label_format_name;

To search by description text across both levels, a query might read:

SELECT label_set_name, set_desc, label_format_name, format_desc FROM apps.wms_label_set_formats_v WHERE UPPER(format_desc) LIKE '%'||UPPER(:p_text)||'%' OR UPPER(set_desc) LIKE '%'||UPPER(:p_text)||'%';

For integration extracts, the numeric keys SET_ID and FORMAT_ID are usually selected alongside SET_DOCUMENT_ID so downstream systems can reconcile against the base tables. Because the view imposes the entity-type filters internally, custom code can rely on it to return only valid set-to-format pairings without reimplementing the LABEL_ENTITY_TYPE logic.