Locations, in Oracle Cloud Warehouse Management System (WMS)

In Oracle Cloud Warehouse Management System (WMS), locations are critical for defining where inventory resides or moves within a warehouse or facility. These are organized within facilities, and the types of locations and their functionality determine how inventory is stored, picked, packed, or shipped.

Here’s a detailed explanation of different location types and their functionalities, along with examples:

1. Storage Location

Function: Used to store inventory for longer durations. These are the core locations where stock resides until needed for outbound or replenishment.

Key Uses:

• Inventory putaway
• Cycle counting
• Replenishment to forward pick

Examples:

• STOR-01-A-01: Storage location in Aisle 01, Bay A, Level 01
• Bulk storage like pallets of rice or cartons of electronics

 

2. Forward Pick Location

Function: These are smaller, easily accessible locations used to store fast-moving inventory for quick picking.

Key Uses:

• Picking smaller quantities quickly
• Replenished from storage locations

Examples:

• PICK-FP-01: Forward picking bin for small electronics like chargers
• FP-01-RACK3: Forward pick bin in rack 3 of zone 01

3. Receiving Location

Function: Where inventory first lands when received from suppliers before it is put away or cross-docked.

Key Uses:

• Receipts from ASN
• Inbound inspection
• Putaway staging

Examples:

• RECV-DOCK-01: Dock door for receiving goods
• RECV-STAGE-01: Temporary staging before putaway

4. Staging Location

Function: Temporary locations used to stage inventory before shipping (outbound staging) or after receiving (inbound staging).

Key Uses:

• Order consolidation
• Load planning
• Pallet building for outbound

Examples:

• STAGE-OUT-01: Outbound staging location for Zone 01
• STAGE-IN-01: Inbound staging for inspection

5. Packing Location

Function: Used to pack picked inventory before shipping.

Key Uses:

• Packing items into cartons
• Label generation
• Final verification

Examples:

• PACK-01: Packing station for ecommerce orders
• PACK-ZONE-A: Area for bulk shipment packing

6. Shipping Dock Location

Function: Final location before inventory leaves the facility.

Key Uses:

• Load to trailer
• Load consolidation
• Shipping confirmation

Examples:

• DOCK-01: Outbound dock door
• DOCK-TRAILER-03: Staging for truck 03

7. Non-Allocatable Location

Function: Inventory stored here cannot be picked or allocated. Used for damaged, quarantine, or return goods.

Key Uses:

• Quarantine inventory
• Hold inventory due to QC issues
• Returns processing

Examples:

• HOLD-01: Hold area for inspection
• DMG-01: Damaged goods area

8. Cycle Count Location

Function: Locations flagged specifically for regular cycle counting.

Key Uses:

• Trigger automated or manual counts
• Location-based counting strategies

Examples:

• Any location flagged as part of ABC grouping for cycle count (e.g., CC-A-01)

 

9. Value-Added Services (VAS) Location

Function: Used for locations where items go through additional processing like kitting, labeling, tagging, etc.

Key Uses:

• Kitting
• Repackaging
• Custom labeling

Examples:

• VAS-01: Gift wrapping station
• VAS-KIT-02: Kitting area for promotional bundles

Thank You,

Pratip Chatterjee

  

Explain 3 types of Facilities in Oracle Cloud WMS

Oracle Cloud WMS Facility Types

In Oracle Cloud WMS, a Facility represents a physical or logical location where inventory is stored or handled. Oracle provides 3 main facility types:

Facility Type	Main Purpose	Typical Example
Distribution Center (DC)	Centralized fulfillment, large-scale storage, multiple operations	Regional Warehouse, Fulfillment Center
Store	Direct-to-consumer retail outlet, small-scale storage	Retail Store, Brand Outlet
Site	Third-party location or external processing site	3PL Warehouse, Vendor Managed Inventory site, Yard

Now let's go into deep detail on each:

Distribution Center (DC)

Purpose:

• This is the most common and feature-rich facility type.
• Used for large warehouses, regional distribution centers, and fulfillment hubs.
• Supports full warehouse management operations: receiving, putaway, picking, packing, shipping, inventory management, cycle counting, value-added services, etc.

Key Capabilities:

• Full inbound and outbound processes
• Complex picking methods: wave picking, cluster picking, zone picking, etc.
• Task management and labor management
• Putaway rules, allocation rules, replenishment, cycle counting
• Integration with carriers, transportation, 3PLs
• Highly configurable storage locations (zones, aisles, racks, bins)

Example:

Amazon Regional Fulfillment Center in Dubai

·  

Store

Purpose:

• Represents a retail outlet where customer-facing transactions happen.
• Limited storage — primarily front-of-house inventory with small backroom storage.
• Simplified operations compared to DC.
• Often used for store inventory visibility, store-to-store transfers, store replenishment, and buy-online-pickup-in-store (BOPIS) processes.

Key Capabilities:

• Simplified receiving (store receiving is much lighter than DC receiving)
• Direct fulfillment of customer orders from store inventory
• Store cycle counting
• Stock visibility for omni-channel fulfillment

Limitations (compared to DC):

• No advanced picking methods
• Limited task management
• Minimal putaway logic (generally direct-to-shelf)

Example:

Nike Retail Store in Mall of the Emirates, Dubai

·  

Site

Purpose:

• Used for 3rd-party locations or locations that don't require full warehouse execution.
• Often external sites like 3PLs, suppliers, cross-docks, yards, or remote locations.
• May or may not have full operational control.
• Acts more as an inventory visibility point rather than full WMS operations.

Key Capabilities:

• Inventory visibility
• ASN/receipt information sharing
• Transfers and shipments to/from Site
• Minimal warehouse execution functionality

Example:

• 3PL Partner Warehouse
• VMI (Vendor Managed Inventory) Location at a customer’s site
• Inbound Cross-Dock Yard

·

Thank You,

Pratip Chatterjee

Frequently asked questions on Oracle Cloud WMS

 Frequently asked questions (FAQ) on Oracle Cloud WMS

1. What is Oracle Cloud WMS? How is it different from traditional WMS systems?

 Oracle Cloud WMS is a cloud-based warehouse management solution that manages inventory, orders, and warehouse operations in real time.

Unlike traditional on-premise WMS, it offers scalability, regular automatic updates, lower infrastructure costs, and better integration with Oracle Cloud ERP, SCM, and TMS.

2. What are the key modules in Oracle Cloud WMS?

Key modules include:

• Receiving and Putaway
• Inventory Management
• Picking and Shipping
• Cycle Counting
• Task Management
• Wave Management
• Cross-Docking
• Yard Management
• Value-Added Services (VAS)

3. Explain Inbound and Outbound processes in Oracle WMS. 

·       Inbound: Receiving shipments, inspecting, putaway to storage locations.

·       Outbound: Picking goods based on orders, packing, staging, loading, and shipping.

4. What is a Facility in Oracle WMS?

A Facility represents the physical warehouse or location where inventory is stored and warehouse operations are performed.

 

5. What are IBLPN and OBLPN?

·       IBLPN (Inbound License Plate Number): Tracks received goods at the container level.

·       OBLPN (Outbound License Plate Number): Tracks outbound shipments during picking, packing, and shipping.

 

6. What is a Task and how is it different from a Work Order?

·       Task: A system-generated instruction for an activity like picking, putaway, or cycle counting.

·       Work Order: A broader instruction set for manufacturing or kitting operations involving multiple tasks.

 

7. How do you configure Receiving Rules in Oracle WMS?

You configure receiving rules through inbound shipment types, setting up default putaway types, inspection requirements, ASN (Advanced Shipment Notice) creation, and warehouse-specific receipt processes.

 

8. Explain Putaway in Oracle Cloud WMS.

Putaway is the process of moving received inventory from the dock to its final storage location based on system-directed rules like zone, item type, or FIFO (First-In-First-Out).

 

9. What is Directed Picking?

Directed picking is when the system guides users on exactly which location and which item to pick based on criteria like FIFO, location priority, or customer allocation rules.

 

10. How is Cycle Counting handled in Oracle Cloud WMS?

·       Cycle counting involves scheduled or ad-hoc counting of inventory without stopping warehouse operations.

·       Oracle WMS supports threshold-based counts, location-based counts, and automatic reconciliation with audit trails.

 

11. What are the steps to configure a Wave Template?

1. Define Wave Template Name and Type (e.g., picking, shipping).

2. Set up Allocation Rules (Item, Order priority).

3. Set Pick Type and Pick Method.

4. Link it to specific Facilities or Carrier Service Levels.

5. Activate the Template.

 

12. What is Packing vs Loading?

·       Packing: Consolidating picked items into containers (OBLPNs) for shipment.

·       Loading: Physically moving packed containers onto a vehicle for transportation.

 

13. How do you create a Pack Type?

Navigate to Pack Types Setup → define dimensions, weight limits, container types (like carton, pallet) to guide packing operations and maximize space utilization.

 

14. Explain Inventory Lock Codes.

Lock Codes restrict certain inventory actions (e.g., reserving damaged goods).

For example, inventory with a "Damaged" lock cannot be allocated to outbound orders until unlocked.

 

15. How do you manage User Roles and Permissions?

Through Security Setup, assign specific roles (e.g., Picker, Supervisor) and permissions (create, view, update) to users or user groups based on warehouse function.

 

16. What are Custom Screens?

Custom Screens are user-configurable RF or desktop screens that modify workflows without coding.

Admins can adjust fields, steps, and validations via a drag-and-drop interface.

  

17. How do you integrate Oracle WMS Cloud with ERP systems?

Using REST/SOAP APIs, B2B messaging (EDI, XML), or Integration Cloud Service (ICS) for real-time data exchange like Inventory Status, Purchase Orders, or Sales Orders.

 

18. What is Item Master Setup?

Setting up product-specific details like SKU code, description, units of measure, storage attributes, and compliance rules required for inbound, outbound, and inventory operations.

 

19. How would you handle a missing item during receiving?

·       Record the discrepancy at receiving.

·       Mark the item as short received.

·       Notify procurement.

·       Adjust inventory.

·       Update ASN (if applicable).

 

20. What steps would you take if a Wave fails to allocate?

Review Wave Details and Allocation Exceptions.

Check inventory availability and location status.

Verify allocation rules.

Re-run the Wave or manually allocate orders.

Thank You,

Pratip Chatterjee

Oracle WMS Implementation Best Practices: A Comprehensive Guide

Oracle WMS Implementation Best Practices: A Comprehensive Guide

Below are the Step-by-Step Oracle WMS Implementation Guide

1. Project Planning and Discovery Phase

• Objectives Setting: Clearly define the goals of the WMS implementation (e.g., reducing picking errors, improving inventory accuracy, optimizing labor).
• Stakeholder Alignment: Engage all stakeholders including operations, IT, finance, and supply chain teams.
• Current State Assessment: Document existing warehouse processes, systems, and infrastructure.
• Budgeting and Resource Allocation: Plan for software, hardware, training, and consulting costs.

2. System Design and Blueprinting

• Functional Design: Identify key WMS functionalities such as receiving, putaway, picking, shipping, cycle counting, and task interleaving.
• Process Mapping: Design future state processes aligned with Oracle WMS capabilities.
• Data Requirements: Define master data needs (items, suppliers, locations, UOMs).
• Integration Design: Plan integrations with ERP, transportation systems, automation equipment, and other third-party systems.

3. System Configuration and Development

• Module Setup: Configure WMS modules based on the blueprint.
• Customizations: Develop custom solutions if required (e.g., RF screen personalization, label formats).
• Data Migration: Prepare and migrate master and transactional data.
• Integration Testing: Validate end-to-end system connectivity and data flow.

4. Testing and Validation

• Unit Testing: Test individual components and configurations.
• System Integration Testing (SIT): Test complete process flows involving multiple modules and systems.
• User Acceptance Testing (UAT): Conduct real-world scenario testing with end users.
• Performance Testing: Ensure system can handle peak loads and volumes.

5. Training and Change Management

• Training Programs: Provide hands-on training to warehouse staff and super users.
• Documentation: Develop SOPs, training manuals, and quick reference guides.
• Change Management: Address cultural resistance, communicate benefits, and involve employees in the transition.

6. Go-Live Preparation and Execution

• Cutover Planning: Define a detailed cutover plan with rollback options.
• Monitor System Performance: Track key performance indicators (KPIs) such as order accuracy and processing times.
• Provide Ongoing Support: Offer helpdesk services and regular system updates.
• Continuous Improvement: Collect feedback and make iterative improvements to optimize warehouse operations. 

Common Challenges and Solutions

1. Resistance to Change

Solution: Implement a robust change management plan that includes clear communication, involvement of key stakeholders, and addressing concerns through training and support. 

2. Data Migration Issues

Solution: Perform thorough data cleansing before migration, conduct pilot migrations, and validate data accuracy post-migration. 

3. Integration Complexities

Solution: Use standard integration protocols, involve experienced integration specialists, and conduct comprehensive testing to ensure seamless data flow between systems. 

4. Inadequate Training

Solution: Develop role-based training programs, utilize various training methods (e.g., classroom, e-learning, hands-on), and provide ongoing support to reinforce learning. 

5. System Performance Issues

Solution: Regularly monitor system performance, optimize configurations, and address any bottlenecks promptly to maintain efficiency. 

Real-World Case Studies

1. Retail Sector

• Challenge: Managing multiple warehouse facilities with legacy systems.
• Solution: Implemented Oracle Cloud WMS across 10 warehouses, streamlining operations and improving inventory visibility.
• Outcome: Enhanced operational efficiency and scalability to support business growth.  

2. Manufacturing Sector

• Challenge: Low space utilization and high mis-shipment rates.
• Solution: Re-engineered business processes, consolidated picking areas, and implemented barcode scanning for accurate shipments.
• Outcome: Achieved 99.9% picking accuracy and improved space utilization.  

3. Logistics Sector

• Challenge: Inefficient supply chain processes and lack of real-time data.
• Solution: Integrated Oracle Cloud WMS with Oracle Fusion and Logistics Suite, automating workflows and enhancing data visibility.
• Outcome: Optimized supply chain operations and improved decision-making capabilities.  

Key Takeaways

• Comprehensive Planning: Thoroughly assess current operations and define clear objectives to guide the implementation process.
• Stakeholder Involvement: Engage all relevant parties early to ensure the system meets business needs and to foster user adoption.
• Robust Training and Support: Provide extensive training and ongoing support to ensure users are proficient and confident in using the new system.
• Continuous Monitoring and Improvement: Regularly evaluate system performance and make necessary adjustments to optimize operations. 

Implementing Oracle WMS is a strategic investment that, when executed with careful planning and attention to detail, can significantly enhance warehouse operations and contribute to overall business success.

Thank You,

Pratip Chatterjee

Redwood UI (RF-based) functionalities for Oracle Cloud WMS

Revolutionizing Warehouse Operations with Redwood UI (RF-Based) in Oracle Cloud WMS

In the ever-evolving world of warehouse management, Oracle’s Redwood UI is setting a new standard for user experience and efficiency—especially when it comes to RF-based transactions. Having worked for 18+ years in Oracle Cloud WMS and ERP WMS environments, I've witnessed firsthand how UI transformation impacts user adoption, productivity, and operational clarity.

Today, let's dive into how Redwood UI is reshaping RF (Radio Frequency) operations within Oracle Cloud WMS.

What Is Redwood UI in Oracle Cloud?

Redwood is Oracle’s modern, consistent design system that offers a clean, intuitive, and responsive user interface across all Oracle Cloud applications. For RF devices, Redwood takes the traditional telnet-based black-and-green screens and transforms them into visually engaging and easy-to-navigate touch UIs.

In RF terms, Redwood UI means:

• Large, touch-friendly buttons
• Minimal text input
• Visual feedback for each action
• Integrated error-handling with clearer messaging
• Faster onboarding of warehouse staff

 I can say, RF + Redwood = A Game Changer

 Use Case 1: Picking

 With Redwood UI:

•  The RF picking screen dynamically updates after each scan.
• Color-coded progress bars guide the user.
• Optional product images help verify the SKU.

 Before: Users had to read long instructions on a green screen and manually keep track of picks.

Now: With icons, image previews, and real-time validations, errors and training time are significantly reduced.

 Use Case 2: Receiving

 Redwood-enabled RF devices:

• Display ASN and shipment lines with item thumbnails.
• Allow toggling between “Scan Item” and “Scan LPN” modes with a tap.
• Provide instant warnings for over-receipts or mismatched barcodes.

 Real-Life Benefit: In one UAE implementation, a team reduced their inbound cycle time by 25% after switching to Redwood-enabled RF screens.

 Key Functional Enhancements

Feature	Traditional RF (Telnet)	Redwood RF
UI Design	Text-based	Icon & touch-based
Navigation	Manual entries	Button taps & swipe
Device Compatibility	Mostly handheld	Touchscreen & mobile responsive
Error Handling	Minimal	Interactive alerts
Training Time	2–3 weeks	Less than 1 week

 Why Warehouse Users Love Redwood

•  Speed: Reduced clicks and quicker task flows
• Clarity: Clear on-screen instructions with visual aids
• Accuracy: Immediate validation avoids costly mistakes
• Adoption: New users are trained faster due to intuitive design

Example Workflow: Picking a Sales Order

Old Flow:

• Enter Task
• Enter LPN
• Scan Item
• Enter Quantity
• Confirm

Redwood RF Flow:

• Tap “Start Pick”
• System auto-fills LPN and Location
• Scan or tap Item (w/ picture)
• Quantity defaults in
• Tap “Confirm Pick”

 Result: What used to take 30–40 seconds now takes 15–20 seconds. Multiply that by hundreds of picks per day, and the savings become substantial.

Technical Tip: Enabling Redwood RF in Oracle Cloud WMS 

• Admins can enable Redwood RF pages via:
• Manage RF Screens task
• Assign Redwood-style screen flows (e.g., redwood_pick, redwood_receive)
• Customize layouts using Page Composer

Oracle continues to roll out more Redwood-compliant RF screens in every quarterly update, so stay current via Release Notes.

Final Thoughts

As Oracle accelerates its transition to Redwood across its cloud ecosystem, RF-based Redwood UI in WMS is no longer a “nice to have”, it's a competitive advantage.

If you're running high-volume warehouse operations, embracing Redwood UI is a strategic move toward leaner, faster, and smarter processes.

Let’s connect if you’re implementing this in your warehouse or need guidance on Oracle WMS transformations.

Thank You,

Pratip Chatterjee