Results for “level_value_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WMS_BFLOW_LABEL_TYPE is a Warehouse Management System (WMS) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the mandatory relationship between business flows and label types. Without a row in this table, the WMS label printing engine has no basis on which to resolve which label template to render when a business flow such as receipt, inspection, cross-docking, put-away, or material movement is executed. In effect, the table acts as a governing map: each business flow code is bound to a specific document and to a specific level of the warehouse hierarchy, ensuring that the appropriate label is emitted at the appropriate transaction point. The table is owned by the WMS schema and is reported as VALID in the ETRM data dictionary, with 32 documented columns.

From a Data Vault modeling standpoint, the heuristic classification for this object is standalone. Although the parent key columns (BUSINESS_FLOW_CODE, DOCUMENT_ID, LEVEL_TYPE_CODE, LEVEL_VALUE_ID) reference reference-data and warehouse-hierarchy entities, the object itself does not behave as a classic hub or link; it is best modeled as a satellite-style configuration entity that records flow-to-label associations with their own descriptive attributes.

Key Information Stored

The primary key, WMS_BFLOW_LABEL_TYPE_PK, is a composite unique index named in the metadata as WMS_BFLOW_LABEL_TYPE_U1, built on BUSINESS_FLOW_CODE, DOCUMENT_ID, LEVEL_TYPE_CODE, and LEVEL_VALUE_ID. These four columns together are the business-key candidates; no single surrogate identifier is documented.

• BUSINESS_FLOW_CODE — the identifier of the WMS business flow (for example a receipt or cross-dock flow). This is the column users most often search by, and it is the driver of join and filter logic.
• DOCUMENT_ID — identifies the label document/template to be rendered for the flow.
• LEVEL_TYPE_CODE — the warehouse hierarchy level (warehouse, zone, locator, etc.) against which the label mapping is scoped.
• LEVEL_VALUE_ID — the specific value of the level selected by LEVEL_TYPE_CODE, enabling location-specific label behavior.
• ENABLED_FLAG — indicates whether the flow-to-label mapping is currently active.
• DELIVERY_COMPLETE_FLAG — controls whether the label is deliverable at the completion point of the flow.
• COMMENTS — free-form annotation maintained by the implementer.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit trail columns required by the AuditTrail framework.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context for the row that created or updated the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) columns available for customer-specific extensions.

Common Use Cases and Queries

The most frequent operational questions are which label will print for a given flow and why a label failed to print. Typical reporting and diagnostic patterns include the following.

• Resolve active label mappings: SELECT business_flow_code, document_id, level_type_code, level_value_id FROM wms.wms_bflow_label_type WHERE enabled_flag = 'Y';
• Check a specific flow and level: filter by BUSINESS_FLOW_CODE and LEVEL_TYPE_CODE to confirm that a mapping exists before running a receipt or inspection.
• Find recently changed configuration: order by LAST_UPDATE_DATE with the standard audit columns for change-control review.
• Join to label/document definition tables using DOCUMENT_ID to retrieve the physical label name and printer attributes.
• Detect missing configurations by comparing the set of defined WMS business flow codes against the mappings present here.

Because the mapping is mandatory for printing, a missing or disabled row is a common root cause of "no label produced" incidents and should be checked first when troubleshooting WMS label output.

Related Objects

The FK/PK relationship data supplied classifies this table as standalone, so the join paths below are inferred from the documented key columns rather than from enforced foreign keys.

• WMS business flow reference data keyed by BUSINESS_FLOW_CODE — the source of valid flow definitions.
• Label/document definition tables keyed by DOCUMENT_ID — hold label name, template, and printer settings used at render time.
• Warehouse hierarchy tables keyed by LEVEL_TYPE_CODE and LEVEL_VALUE_ID — warehouse, zone, and locator definitions.
• WMS label printing and label request tables — consume this mapping to determine which label to emit.
• Standard EBS concurrent program and request tables (FND_CONCURRENT_REQUESTS, FND_PROGRAM) — joined via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for audit and lineage reporting.
• WMS_LABEL_REQUESTS and related WMS label views — the runtime consumers of BUSINESS_FLOW_CODE during receipt, inspection, and cross-dock execution.