Here's a comprehensive guide on Lock Codes in Oracle Cloud WMS, covering setup, screen-level detail, column-wise descriptions, and real-world usage scenarios.
What are Lock Codes in Oracle Cloud WMS?
Lock Codes in Oracle Cloud Warehouse Management (OCWMS) are
used to restrict certain operations on inventory, locations, or LPNs (License
Plate Numbers). They're essential for managing quality control, damaged goods,
quarantine stock, or inventory under inspection.
Where Lock Codes Are Used?
Lock codes can be applied to:
· Inventory at a specific location
· Entire LPNs
· Inventory at the item level
· Inventory at the lot or serial level
Setup Path in Oracle Cloud WMS
Navigation: Warehouse Configuration > Lock Codes
Lock Code Screen – Column/Field Level Details
|
Field Name |
Description |
|
Lock Code |
Unique identifier (alphanumeric) used to tag and restrict
inventory or locations |
|
Description |
Free-text field for detailing the purpose of the lock code |
|
Lock Type |
Defines the scope of lock application: - Inventory
- LPN - Location |
|
Prevent Picking |
If checked, items with this lock cannot be picked in tasks |
|
Prevent Putaway |
Prevents inventory with this lock from being put away |
|
Prevent Cycle Counting |
If enabled, prevents this inventory from being included in
cycle counting |
|
Prevent Inventory Adjustment |
Prevents adjustment (e.g., quantity change, item change) |
|
Prevent Transfers |
Disables transfer transactions (manual or system
generated) |
|
Prevent Picks to Outbound |
Specifically restricts the use of locked inventory for
outbound tasks |
|
Prevent Cross-dock Allocation |
Stops locked inventory from being used for cross-docking |
|
Prevent Inbound Receiving |
Blocks receiving tasks from placing inventory under this
lock directly |
|
Enable Auto Locking |
Automatically apply the lock based on configuration/rules
(like QC triggers) |
|
Auto Locking Reason |
Describes the trigger/reason for the auto-locking |
|
Allow Manual Unlock |
If false, only system or workflow can remove the lock |
|
Allow Lock Override |
If checked, users with roles can override the lock during
tasks |
|
Active |
Indicates if the lock code is currently active |
Usage Scenarios
1. Quality Control Hold (QC_HOLD)
· Lock Type: Inventory
· Prevent: Picking, Putaway, Transfers
· Auto-applied based on ASN or lot status
· Manual unlock post-inspection
2. Damaged Goods (DAMAGED)
· Lock Type: LPN
· Prevent: Picking, Transfers, Cycle Count
· Used when scanning items with reported damage
3. Quarantine Location (QUARANTINE_BIN)
· Lock Type: Location
· Prevent: Putaway, Picking
· Entire bin marked as restricted – e.g., pest control treatment area
4. Serialized Item Audit Lock (AUDIT_LOCK)
· Lock Type: Inventory
· Prevent: Adjustment, Transfers, Picking
· Applied on specific serials under investigation
Configuration Tips
· Use auto-locking rules for high-risk suppliers.
· Leverage Oracle Rules Framework to dynamically apply lock codes during:
· ASN receiving
· Inspection failures
· Return processing
· Build Reports on locked inventory for daily warehouse reviews.
· Add user role validation to manage override permissions for sensitive locks.
Unlocking Inventory
Unlocking can be done via:· Manual Unlock action in UI
· Bulk Unlock Process for mass changes
· System Workflow (e.g., after inspection approval)
· REST API or RF transactions, with appropriate permissions
If you need detail example from real implementation, please comments.
Thanks,
Pratip Chatterjee
