Planned Functions

Owned by Johannes Sebastian Nielsen

Last updated: Dec 22, 2023

2 min read

Description

Planned functions uses Header/Lines and includes actions for posting, viewing registrations and "order locking"

Planned functions

Receive
Put-away
Pick
Ship
Move
Count
Assembly
Production

Key points

Displays data is in two levels. Header and Lines
Uses a Header defined in Reference Data with search filters
Can have Unplanned Functions as actions on both Orders and Order Lines
Standard Steps are definned by Workflows in Mobile Configuration Files but can be changed using Customization

Hierarchy

Each order can have multiple Order Lines

Steps

Workflows defines the Steps.

Workflows are stored directly in the Mobile Configuration Files, but somewhat configurable from the backend using Order Lines GetOrderLines Response

ValidateToBin
ValidateFromBin
RegisterLotNumber
RegisterSerialNumber
and many more..

Customization

You can customize the existing functionality or create your own Planned function.

Document Flow

The document type name is shown (parantheses)

A list of Orders are displayed. (GetOrders)
User selects an order.
1. (Optional) Mobile user edits the Header to search for a desired Order
2. Mobile user selects an order
Lock the selected order (LockOrder)
List of Order Lines from the selected order are displayed. (GetOrderLines)
1. User selects a line.
Collector Steps are displayed (Device can go Offline now)
User completes the steps
The user is returned to the Order Lines (Still offline)
User "Posts" (If done) (PostOrder)
Unlock the selected order (UnLockOrder)

The user is returned to Step 1

Mobile Configuration

Page types

Planned functions always uses two pages, called "OrderList" and "OrderLines".

Explore the Mobile WMS App