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

How to use AI and ML in Oracle Cloud WMS

How to use AI and ML in Oracle Cloud WMS 

Oracle Cloud WMS is a modern, cloud-based warehouse management system that offers scalability, flexibility, and a host of powerful features. One of the most transformative aspects of Oracle Cloud WMS is its ability to leverage Artificial Intelligence (AI) and Machine Learning (ML) to optimize warehouse operations, improve efficiency, and reduce costs.

In this article, I will explore how AI can be used in Oracle Cloud WMS with real-world use cases, examples, and implementation steps.

AI Capabilities in Oracle Cloud WMS

Oracle integrates AI in WMS through the following areas:

1. Inventory Optimization

Use Case:

AI analyses historical sales data, supplier lead times, and seasonal trends to optimize inventory levels.

Live Example:

A retailer uses Oracle Cloud WMS to manage warehouse stock. By enabling Oracle AI capabilities, it automatically identifies that demand for winter jackets spikes in November based on the last 5 years of sales data and recommends increased stocking in October.

Implementation Steps:

·   Enable AI/ML features from the Oracle Fusion SCM dashboard.

·   Integrate historical inventory and sales data using Oracle Data Integration tools.

·   Use Oracle Analytics Cloud to visualize predictions and suggested actions.

2. Order Fulfilment Predictions

Use Case:

AI predicts the best warehouse to fulfil an order based on delivery time, stock levels, and shipping cost.

Live Example:

A customer from Delhi places an online order. AI suggests fulfilling it from the Noida warehouse instead of Mumbai because it reduces delivery time by 2 days and shipping cost by 20%.

Implementation Steps:

·   Set up multi-warehouse configurations in Oracle Cloud WMS.

·   Integrate Oracle AI Apps for SCM.

·   Configure predictive routing rules using Oracle Process Automation.

3. Labor Forecasting and Optimization

Use Case:

AI predicts labour requirements based on incoming order volume and schedules shifts accordingly.

Live Example:

During Black Friday week, AI forecasts a 300% increase in outbound shipments and recommends hiring 15 additional temporary workers for the week.

Implementation Steps:

·   Use Oracle Workforce Management with Oracle WMS.

·   Upload historical labour and volume data.

·   Enable predictive scheduling in the Workforce Optimization module.

4. Anomaly Detection

Use Case:

Detect unusual stock movements or errors in warehouse operations.

Live Example:

AI detects that Item A has a 50% higher return rate than usual in the past week. It automatically flags the item and notifies QA for investigation.

Implementation Steps:

·   Use Oracle AI Adaptive Intelligence apps.

·   Configure anomaly thresholds in Oracle IoT Cloud apps if using IoT sensors.

·   Automate alerts via Oracle Notification Services.

5. Autonomous Decision Making

Use Case:

AI triggers automatic replenishment, rerouting, or alerts without human intervention.

Live Example:

When stock for a fast-moving item drops below threshold, AI autonomously creates a PO from a preferred supplier.

Implementation Steps:

·   Set rules and thresholds in the Oracle WMS rules engine.

·   Enable autonomous triggers using Oracle SCM Cloud AI engine.

·   Use Oracle Integration Cloud for automated supplier communications.

6. Computer Vision Integration

Use Case:

Use AI-powered cameras for real-time inventory scanning and safety monitoring.

Live Example:

A warehouse installs AI cameras integrated with Oracle IoT Cloud. These detect incorrect stacking of pallets and alert staff to prevent accidents.

Implementation Steps:

·   Integrate computer vision hardware with Oracle IoT Cloud.

·   Train AI models using Oracle Machine Learning (OML) in Autonomous Database.

·   Stream insights into Oracle Cloud WMS dashboards.

Tools and Services Involved

·   Oracle Cloud Infrastructure (OCI) AI Services

·   Oracle Analytics Cloud (OAC)

·   Oracle Machine Learning (OML)

·   Oracle Integration Cloud

·   Oracle IoT Cloud

·   Oracle Digital Assistant (for AI-driven user interfaces)

Getting Started

Prerequisites:

·   Oracle Cloud WMS subscription

·   Access to Oracle Fusion Cloud SCM

·   Historical data for AI model training

Steps:

·   Connect your WMS to Oracle Analytics Cloud.

·   Import relevant data from ERP, CRM, and external systems.

·   Train ML models using Oracle Machine Learning.

·   Deploy AI insights back into Oracle WMS through APIs or dashboards.

AI in Oracle Cloud WMS is not just a concept, it's already being applied by businesses to cut costs, improve efficiency, and make smarter decisions. Whether you're predicting stock shortages or rerouting shipments, AI provides a competitive edge in the modern supply chain.

Thanks,

Pratip Chatterjee

How to use Agile methodology during an Oracle Cloud WMS (Warehouse Management System) implementation

Using Agile for Oracle Cloud WMS Implementation

When implementing Oracle Cloud WMS, the company decided to shift from the traditional waterfall approach to Agile, aiming for faster results and better adaptability. The project was broken down into sprints — short, focused periods (2–3 weeks each) — where small, manageable pieces of the WMS system were configured, tested, and reviewed.

Sprint 1 started with basic warehouse setup: defining facility structures, inventory organizations, and users. During the sprint, daily stand-up meetings were held to track progress and solve issues immediately. At the end of the sprint, a demo was given to warehouse managers for feedback.

Sprint 2 focused on inbound operations: receiving, putaway rules, and ASN (Advanced Shipment Notice) setups. Based on early feedback, the team quickly adapted the putaway strategies to match the real-world needs of the warehouse.

Sprint 3 tackled outbound operations: including picking, packing, and shipping flows. User stories (business requirements written from the user’s perspective) guided configuration and testing, ensuring every function added real operational value.

Parallel to the sprints, training and UAT (User Acceptance Testing) were continuous activities. Users were involved early, practicing on partial builds instead of waiting for the final rollout.

Benefits:

•  Faster visibility of issues
•  Early feedback reduced rework
•  Users felt ownership from Day 1
•  Flexibility to adjust to unexpected business needs

After about 4–5 sprints, the core functionalities were ready, and a final stabilization sprint was done before going live.

Agile Approach for Oracle Cloud WMS Implementation

1. Agile Phases Overview

Initiation (Sprint 0):  Identify high-level business processes (Receiving, Putaway, Picking, Shipping, Cycle Counting). Define Epics (big features) and break them into User Stories (small tasks).

 Sprints (2–3 weeks each): 

• Sprint Planning
• Daily Standups
• Mid-Sprint Reviews
• Sprint Demo to Business Users
• Sprint Retrospective
• Go-Live and Stabilization Sprint.

 2. Detailed Use Case Example: "Automate Receiving Process"

 As a warehouse manager, you want to automate the receiving process so that received goods are accurately updated into inventory with minimal manual entry.

 User Stories:

• Configure supplier ASN (Advance Shipment Notice) integration.
• Set up default putaway rules after receiving.
• Auto-generate LPNs (License Plate Numbers) during receiving.
• Customize receiving UI to show mandatory fields (PO number, Quantity, Condition Code).

 3. Development Team Procedure Management 

Step	Action
Backlog Grooming	Work with Product Owner to refine user stories with clear Definition of Done (acceptance criteria).
Sprint Planning	Pick 4-6 stories (depending on capacity), estimate effort in story points.
Configuration	WMS Functional Consultants configure receiving parameters, shipment types, defaulting rules.
Development	If customizations are needed (e.g., extensions, REST API, ASN import), developers create extensions in Oracle Visual Builder Cloud Service (VBCS) or through API's
Testing	QA team and warehouse user test the configures processes inside the Sprint.
Demo	At Sprint end, showcase Auto Receiving workflow to business user for approval or feedback.
UAT Preparation	Collect feedback adjusted in the next Sprint if needed.
Deployment Management	Use Oracle Migratior tools (Export/Import Setup Data or Functional Setup Manager) to move configurations across environments (Dev to Test to Production).

 4. Important Agile Best Practices for Dev Team

•  Daily Standup: Quickly share blockers, e.g., ASN payload from supplier missing required fields.
•  Backlog Updates: After demo, if user asks for small changes, create new user stories for next sprint.
•  Incremental Deployment: Every sprint should create a working, testable WMS feature.

 Collaboration with Oracle Cloud Services: Engage Oracle SRs (Service Requests) if a platform issue arises and track separately from sprint deliverables.

 DevOps: If using custom code (extensions or integrations), maintain versioning in GitHub or DevOps tools.

 Summary Diagram (Flow) 

• Sprint 0 → Identify Epics and Stories
• Sprint 1 → Configure Receiving → Test → Demo
• Sprint 2 → Configure Putaway → Test → Demo
• Sprint 3 → Configure Picking → Test → Demo
• Sprint 4 → Integrations/Customizations → Test → Demo
• Sprint 5 → Stabilization → Final UAT → Go-Live

 

Thank You,

Pratip Chatterjee

How SaaS (Software as a Service) and PaaS (Platform as a Service) work in the context of Oracle Cloud Warehouse Management System (WMS)

In today's article, I am discussing how SaaS (Software as a Service) and PaaS (Platform as a Service) work in the context of Oracle Cloud Warehouse Management System (WMS).

Understanding SaaS and PaaS in Oracle Cloud WMS

Cloud computing has revolutionized how businesses manage enterprise applications like warehouse management systems (WMS). Oracle offers a robust, scalable, and integrated solution through Oracle Cloud WMS, using both SaaS and PaaS models. This article breaks down how each model works and supports logistics operations.

What is Oracle Cloud WMS?

Oracle Cloud WMS is a cloud-based warehouse management system that helps organizations manage warehouse operations efficiently—from inventory tracking and order fulfillment to labor management and real-time analytics.

SaaS (Software as a Service) in Oracle Cloud WMS

SaaS delivers a fully-managed software application over the internet. In the case of Oracle Cloud WMS:

 How it works:

• Oracle hosts and maintains the WMS software.
• Customers access it via a web interface or API.
• All backend processes like updates, patches, security, and scalability are managed by Oracle.

 Features Offered via SaaS:

• Pre-configured workflows for receiving, picking, shipping, inventory control.
• Real-time visibility into warehouse operations.
• AI/ML-powered demand forecasting and inventory optimization.
• Seamless integration with Oracle ERP Cloud and other third-party systems.

 Benefits:

• Quick deployment: No need to install or maintain software.
• Scalability: Easy to add new warehouses or users.
• Lower TCO: No infrastructure costs.
• Automatic updates: Stay current with the latest features.

 Use Case Example:

A retailer with multiple fulfilment centers uses Oracle Cloud WMS SaaS to manage distributed inventory. The software helps streamline operations without needing IT teams to deploy or maintain the system locally.

PaaS (Platform as a Service) in Oracle Cloud WMS

PaaS provides a platform and environment for developers to build, customize, and deploy applications on top of Oracle’s infrastructure.

 How it works:

• Oracle offers a set of development tools, APIs, and services like Oracle Integration Cloud, Oracle Visual Builder, and Oracle APEX.
• Developers can create extensions or custom apps that interact with Oracle WMS.

 Common PaaS Use Cases in WMS:

• Custom dashboards: Building specific visualizations not available in the standard SaaS dashboard.
• Integrations: Connecting Oracle WMS with legacy ERP or third-party logistics systems.
• Custom business logic: Adding unique workflows or rule sets for specialized warehouse processes.
• Mobile app extensions: Enhancing mobile UIs for handheld devices used in the warehouse.

 Benefits:

• Customization: Tailor Oracle WMS to your unique business needs.
• Faster innovation: Deploy new features quickly without waiting for SaaS releases.
• Secure and scalable: Built on the same robust Oracle Cloud Infrastructure (OCI).

 Use Case Example:

A pharma company needs a custom temperature tracking system in its cold storage warehouse. Developers use Oracle PaaS to create a module that interfaces with IoT sensors and integrates the data into Oracle WMS.

So, SaaS + PaaS: A Powerful Combination; Oracle Cloud WMS is designed to leverage the best of both models:

Oracle Cloud WMS provides an enterprise-grade, cloud-native solution using both SaaS and PaaS models. While SaaS enables rapid deployment and standardized best practices, PaaS offers the flexibility to customize and extend functionality. Together, they empower businesses to operate smarter, faster, and more efficiently in today’s dynamic supply chain landscape.

Thank You,

Pratip Chatterjee

Purchase Order Full Flow - Fusion to WMS to Fusion

Purchase Order Full Flow - Fusion to WMS to Fusion

PO Created in Fusion > Run/Schedule Generate Receipt Advice > Interface (OIC) >  PO created in WMS > Create IB Shipment in WMS (or ASN import from Fusion) > Appointment for Load > Dock Check In > Cartonization > IBLPN (Print Blind IBLPN) > RF Receiving > Putaway > Dock Check Out > Verification  > Interface (OIC) > GRN is created per IB Shipment in Fusion 

- Purchase Order Status during Receiving (Header and Line): In Receiving

- IB Shipment Status during Receiving : Header = Receiving Started and Line = Received

- IB Shipment Status after Receiving is completed : Header = Receiving Completed and Line = Received

- IBLPN Status : Received

- After Receiving : This will send an interface to Fusion Inventory Management to create receipts. (Receipt Confirmation)

- After Put away : This will again send an interface back to Fusion to initiate the GRN process. (Receipt Confirmation)

- PO receipt : One GRN is created per IB Shipment in Fusion based on the shipment verification file from WMS.

Thank You,

Pratip Chatterjee