WMS - Receiving

WMS - ReceivingDELMIA Apriso 2019 Detailed Design

®2019

DassaultSystèmes.Apriso,3D

EXPE

RIENCE,theCom

pass

logo

andthe3D

Slogo,C

ATIA,SOLIDWORKS

,ENOVIA,DELMIA,SIMULIA,GEO

VIA,EX

ALEA

D,3DVIA,BIOVIA,NET

VIBE

S,and3D

XCITE

arecommercialtrademarks

orregistered

trademarks

ofDassaultSystèmes

orits

subsidiariesintheU.S.and/orothercountries.Allothertrademarks

areow

nedby

theirrespectiveow

ners.

Use

ofanyDassaultSystèmes

orits

subsidiariestrademarks

issubjecttotheirexpress

writtenapproval.

Contents1 Introduction 51.1 Functionality 51.2 Roles 5

2 How To Use This Detailed Design 62.1 Glossary 62.2 Diagram Legend 7

3 Prerequisites 84 Assumptions 95 Process Overview 106 Actions 116.1 Receive ASN 116.2 Receive PO 146.3 Put Away 156.4 Complete 176.5 Scan Barcode (RCV-10) 186.6 Scan Barcode (RCV-20) 216.7 Scan Barcode (RCV-21) 21

7 Screen Descriptions 247.1 RCV-10 247.1.1 Barcode Field 257.1.2 Orders List 25

7.2 RCV-20 267.2.1 Barcode Field 277.2.2 Multiselect Button 277.2.3 Containers List 287.2.4 Buttons 30

7.3 RCV-30 317.3.1 Mix Container 327.3.2 One-Item and Multi-Item Containers 33

7.4 RCV-50 357.5 RCV-21 367.5.1 Barcode Field 377.5.2 Multiselect Button 377.5.3 Entities List 387.5.4 Buttons 40

7.6 RCV-40 427.6.1 Barcode Field 437.6.2 Property Fields 437.6.3 Buttons 43

WMS - Receiving | DELMIA Apriso 2019 Detailed Design 2

7.6.4 Creating New Entity and Handling Existing Entity 457.7 RCV-60 487.7.1 Barcode Field 507.7.2 Property Fields 507.7.3 Buttons 507.7.4 Adding New Item To Master Container 52

8 Results 539 Configuration 549.1 Complete Button 549.2 Inventory Status 549.3 Container Class 549.4 Prefixes Recognition 559.5 Automatic Order Line Completion 55

10 Put Away Application 5711 References 58

FiguresFigure 1 Diagram elements 7Figure 2 Receiving Process 10Figure 3 Receive ASN 12Figure 4 Receive single Entity 13Figure 5 Receive PO 15Figure 6 Put Away 16Figure 7 Complete 18Figure 8 Scan barcode (RCV-10) 19Figure 9 WRH_BarcodeExplode Operation 20Figure 10 Scan barcode (RCV-20) 21Figure 11 Scan barcode (RCV-21) 22Figure 12 RCV-10 screen 24Figure 13 RCV-10 screen – ASN Order properties 25Figure 14 RCV-10 Purchase Order properties 26Figure 15 RCV-20 screen 27Figure 16 RCV-20 screen – Multiselect button 28Figure 17 RCV-20 screen – One-Item Container 28Figure 18 RCV-20 screen – Multi-Item Container 29Figure 19 RCV-20 screen – Mix Container 29Figure 20 RCV-20 screen – Container properties 29Figure 21 RCV-20 screen – Put Away dialog box 30Figure 22 RCV-20 screen – Complete button 31Figure 23 RCV-30 screen – Mix Container 32Figure 24 RCV-30 screen – One-Item/multi-Item Container 33Figure 25 RCV-30 screen – Put Away dialog box 34


Figure 26 RCV-50 screen 35Figure 27 RCV-21 screen 37Figure 28 RCV-21 screen – Multiselect button 38Figure 29 RCV-21 screen – One-Item Container 38Figure 30 RCV-21 screen – Multi-Item Containerr 39Figure 31 RCV-21 screen – Mix Container 39Figure 32 RCV-21 screen – Container properties 40Figure 33 RCV-21 screen – Inventory without Container 40Figure 34 RCV-21 screen – Put Away dialog box 41Figure 35 RCV-21 screen – Complete button 41Figure 36 RCV-40 screen 42Figure 37 RCV-40 screen – Put Away dialog box 44Figure 38 RCV-40 screen – New 46Figure 39 RCV-40 screen – Existing Entity 48Figure 40 RCV-60 screen – Existing Entity 49Figure 41 RCV-60 screen – Put Away dialog box 51Figure 42 Complete Order Line dialog box 56Figure 43 Put Away application 57


1 IntroductionThis document describes the Detailed Design of the Receiving application for Warehouse Management System (WMS). The document includes description of various Process aspects such as the prerequisites, assumptions, Process flow description and Process results.

1.1 FunctionalityThe Receiving application is used to receive:

Containers based on an Advanced Shipping Notification Containers and Inventory without Containers based on a Purchase Order

Containers can consist of:

Products placed directly insideProducts placed in Child Containers

The Receiving application can also be used to put away Containers and Inventory without Containers.

1.2 RolesRoles define the user profiles needed to execute the Process described in this Detailed Design.

The Warehouse Operator Role is necessary to execute the actions described in this Detailed Design.


2 How To Use This Detailed Design2.1 Glossary

DELMIA Apriso Term

Description

ASN Advanced Shipping Notification – a type of order downloaded from external system (e.g. ERP). It includes information about Supplier, dates, Products, Containers, etc.

Container It can be anything designed to hold (contain) materials for storage or transport. In this document the term Container will be used.

Container Class

Used for classification purposes.

Entity Container and/or Inventory Without Container.Extension Point

An Extension Point in DELMIA Apriso is a place where an additional, customized validation or business logic operation can be plugged in according to customer needs.

Inventory Products which are physically stored in a warehouse, with assigned Inventory Status, Quantity, Lot and/or Serial Number (if needed).

Inventory Status

It is a property of the Inventory. During Receiving Process the Warehouse Operator can set up a proper Inventory Status or it can be set up by default (depending on configuration options). Mainly used Statuses: Unrestricted use, Quality inspection, Blocked.

Inventory Operation

An action which involves Inventory or Container changes, e.g. Move Inventory, Move Container, Change Status.

Item A Product or a batch of Products which may have different Serial Numbers, Statuses, etc than another batch of the same Products.

Order An Order consists of an Order Header and Order Lines. The Order Header contains information about a Supplier and dates. An Order Line contains detailed information about the Order’s Products, Quantities and Tolerances.

PO Purchase Order – a type of order downloaded from external system (e.g. ERP). It includes an Order Header (information about Supplier, dates, etc.) and one or more Order Lines (information about Products, etc.).

Put Away An action that allows putting Container in a proper Location.Receiving An action of Inventory reception.Receiving Order

A message from an external system (e.g. ERP) with information about planned Receiving.

Warehouse The place where Containers and Inventory can be stored. The terms Location


Location and Warehouse Location can be used alternatively.Warehouse Location Class

Used for classification purposes.

Warehouse Role

The Warehouse Role contains a consistent model and a set of available functions to support WMS operations including internal transport and the recommendation on how to use them when addressing the different business cases.

2.2 Diagram LegendThe diagram elements used in this document:

Figure 1 Diagram elements


3 PrerequisitesTo execute actions described in this Detailed Design the following data needs to be prepared in DELMIA Apriso:

Organizational context description: Facility, Warehouse, Warehouse Location

If an Employee has a Facility assigned, the Warehouse Location name should be unique across this Facility.If an Employee does not have any Facility assigned, it is required that all Warehouse Location names should be unique across the whole system.

Employee Data: Employee details, Employee RolesPossible Inventory StatusesInformation about OrdersContainer list, Products


4 AssumptionsThe functionality described in this document is designed to be used on the following devices:

RF Guns, phones, tabletsOperating systems: Android, iOSScreen size: min. viewport width: 360 px, min. viewport height: 480 px

It is recommended that the application is used in the full screen mode to eliminate the need to scroll.


5 Process OverviewThis section presents the overview of the Receiving Process.

Figure 2 Receiving Process

* Apart from the Receiving application Entities can be also put away in the Put Away application. For more information refer to the 10 Put Away Application section.


6 ActionsThis section contains detailed descriptions of the actions performed by the Warehouse Operator in the Receiving application.

6.1 Receive ASNTrigger – Receive buttonScreen – RCV-20 / RCV-30User Input – N/AExpected Result – Entity is receivedMethod Used – RCV_Receive_Action


Figure 3 Receive ASN

The action flow:

1. The RCV_Receive_Action_Before Extension Point is executed. 2. Receive Single Entity is performed for each selected Entity until all of them are received –

The RCV_ReceiveSingleContainer Operation is called. If new Inventory Status is provided the RCV_ChangeInventoryStatus_Action Operation is called to update the value.

3. Order Status is changed to the Status defined in the APR_INV_Const_OrderStatus_Started System Parameter – the ORDER_HEADER table is updated.

4. The RCV_Receive_Action_After Extension Point is executed.

Receive Single Entity


Trigger – Receive buttonScreen – RCV-20 / RCV-30User input – N/AExpected result – Entity is ReceivedMethod used – RCV_ReceiveSingleEntity

Figure 4 Receive single Entity

The action flow:

1. The RCV_ReceiveSingleEntity_Before Extension Point is executed. 2. The RCV_CreateInventory Operation is called.

If Entity has Lot Number defined, Lot Number is created for it in the LOT_NO table. If Entity has Serial Number defined, Serial Number is created for it in the SERIAL_NO table.

If Entity is Container and it does not exist, a new record is created in the CONTAINER table. The APR_RCV_NewContainerStatus System Parameter is used to provide the Container with Status.

Inventory is created for the provided data (Product or Container) – the INVENTORY2 table is updated.


3. The RCV_DetermineIfCreateNewChildOrder Operation is called. The system checks the value of the APR_RCV_MinDifferenceBetweenReceivingOrders System Parameter.

4. If it is 0, the system uses a parent WIP Order associated with the Order Line and moves to step 6. If no parent WIP Order exists, an error message is displayed.

5. If the APR_RCV_MinDifferenceBetweenReceivingOrders System Parameter is not 0, the system searches for the started child WIP Order and executes one of the following scenarios:

If the started child WIP Order does not exist, the system creates a new one. The system checks if a parent WIP Order exists. If no, an error message is displayed. If a parent WIP Order exists, the newly created child WIP Order is started.If the started child WIP Order exists, the system compares the Order's start date and the value of the APR_RCV_MinDifferenceBetweenReceivingOrders System Parameter with the current time.

If the started child WIP Order can be used, the system moves to step 6.

If the started child WIP Order cannot be used, the system creates a new one. The system checks if a parent WIP Order exists. If no, an error message is displayed. If a parent WIP Order exists, the old child WIP Order is closed and a newly created one is started.

6. Order Status is changed to the Status defined in the APR_INV_Const_OrderStatus_Started System Parameter – the ORDER_DETAIL table is updated.

7. The RCV_ReceiveSingleEntity_After Extension Point is executed.

6.2 Receive POTrigger – Receive buttonScreen – RCV-40 / RCV-60User Input – N/AExpected Result – Entity is receivedMethod Used – RCV_SaveValidate_Action, RCV_Save_Action


Figure 5 Receive PO

The action flow:

1. The RCV_Save_Action_Before Extension Point is called. 2. The system creates Content – the RCV_CreateOrderDetailContent Operation is executed.

A row is added in the ORDER_DETAIL_CONTENT table based on the data provided. 3. Receive Single Entity action is performed. 4. Order Status is changed to the Status defined in the APR_INV_Const_OrderStatus_Started

System Parameter – the ORDER_HEADER table is updated. 5. The RCV_Save_Action_After Extension Point is called.

6.3 Put AwayTrigger – Put Away button in Receiving app / scanning Container in Put Away appScreen – RCV-20 / RCV-30 / RCV-21 / RCV-40 / RCV-60 / Put Away app


User Input – Enter target LocationExpected Result – Entity is put awayMethods Used – RCV_Putaway_Validate, RCV_Putaway_Action

Figure 6 Put Away

The action flow for one Entity:

1. The system checks if Entity has been received. If not, an error message is displayed. 2. If Entity has been received, the RCV_Putaway_Validate Operation is called. It uses RCV_

GetSuggestedLocations_Action Operation to retrieve data from the APR_WH_PUTAWAY_LOCATION Classic Determination.


3. If no suggested Location is found and the APR_RCV_BlockNotSuggestedPutaway System Parameter is set to True, an error is displayed. If no suggested Location is found but the APR_RCV_BlockNotSuggestedPutaway is set to False, the system moves to the next step.

4. Put Away dialog box with the list of suggested Locations is displayed where the Warehouse Operator can enter the target Location. a. If the APR_RCV_BlockNotSuggestedPutaway System Parameter is set to True, the

Warehouse Operator has to enter one of the suggested Locations. If they enter Location which is different than the suggested one, an error is displayed.

b. If the APR_RCV_BlockNotSuggestedPutaway System Parameter is set to False, the Warehouse Operator can enter one of the listed Locations or any other Location. After tapping OK button, the RCV_Putaway_Action Operation is called.

5. The RCV_Putaway_Action_Before Extension Point is executed. 6. If entered Location does not exist in the system, an error is displayed. 7. Put Away action is performed. The INVENTORY2 table and optionally (depending on

Entity type) CONTAINER table are updated. 8. The RCV_Putaway_Action_After Extension Point is executed.

The action flow for more than one Entity:

1. The system checks if the APR_RCV_BlockNotSuggestedPutaway System Parameter is set to True. If it is, an error is displayed.

2. The system checks if Entities have been received. If not, an error message is displayed. 3. If Entities have been received, the RCV_Putaway_Validate Operation is called. 4. Put Away dialog box is displayed where the Warehouse Operator can enter the target

Location. 5. The RCV_Putaway_Action_Before Extension Point is executed. 6. If entered Location does not exist in the system, an error is displayed. 7. Put Away action is performed. The INVENTORY2 table and optionally (depending on

Entity type) CONTAINER table are updated. 8. The RCV_Putaway_Action_After Extension Point is executed.

Apart from the Receiving application Entities can be also put away in the Put Away application. For more information refer to the 10 Put Away Application section.

6.4 CompleteThe Complete action is not available by default. For configuration details refer to 9.1 Complete Button in the Configuration section.

Trigger – Complete buttonScreen – RCV-20 / RCV-21User Input – Confirm completing OrderExpected Result – Order Status is changedMethods Used – RCV_CompleteOrder_Action


Figure 7 Complete

The action flow:

1. The Complete Order dialog box is displayed where the Warehouse Operator can confirm that they want to complete the Order.

2. If the Warehouse Operator taps No, this is the end of the action. 3. If the Warehouse Operator taps Yes, the Complete Order action is performed – the RCV_

CompleteOrder_Action Operation is called. The Order Status is changed according to one of the following scenarios:

If the APR_RCV_UseCompletedStatus System Parameter is set to True, the Order Status is changed to "3-Completed". If the APR_RCV_UseCompletedStatus System Parameter is set to False, the Order Status is changed to "6-Closed".

The ORDER_HEADER table is updated.

6.5 Scan Barcode (RCV-10)Trigger – Scanning a barcodeScreen – RCV-10User Input – Scan a barcodeExpected Result – User is navigated to the relevant screenMethods Used – RCV-10_ScanBarcodeExplode_Action, WRH_BarcodeExplode


Figure 8 Scan barcode (RCV-10)

The action flow:

1. The WRH_BarcodeExplode Operation is executed. 2. The system checks if it can recognize Container prefix.


3. If Container prefix is recognized, the system move to Step 6. 4. If Container prefix is not recognized, the system tries to find Order/Container based on their

names. If nothing is found, an error is displayed. 5. If Order is found, the system checks what type of Order this is.

a. If it is ASN Order, the RCV-20 screen is displayed. b. If it is Purchase Order, the RCV-21 screen is displayed.

6. If Container is found, the system checks what type of Order it belongs to. a. If Container belongs to Purchase Order, the system checks what type of Entity it is. If it is

a mix or a multi-Item Container, the RCV-60 screen is displayed. If it is one-Item Container, the RCV-40 screen is displayed.

b. If Container belongs to ASN Order, the RCV-30 screen is displayed.

WRH_BarcodeExplode Operation

Figure 9 WRH_BarcodeExplode Operation

The action flow:

1. The WRH_BarcodeExplode_Before Extension Point is executed. 2. The system checks if it can use standard prefix recognition.

a. If yes, prefixes are recognized based on configuration (done in the Prefix Management Cockpit).

b. If not, standard prefix recognition is omitted.


3. The WRH_BarcodeExplode_After Extension Point is executed.

6.6 Scan Barcode (RCV-20)Trigger – Scanning a barcodeScreen – RCV-20User Input – Scan a barcodeExpected Result – User is navigated to the relevant screenMethods Used – RCV-20_ScanBarcodeExplode_Action, WRH_BarcodeExplode


The action flow:

1. The WRH_BarcodeExplode Operation is executed. 2. The system tries to find Container. If Container is not found, an error is displayed. If it is

found, the RCV-30 screen is displayed.

6.7 Scan Barcode (RCV-21)Trigger – Scanning a barcodeScreen – RCV-21User Input – Scan a barcode


Expected Result – User is navigated to the relevant screenMethods Used – RCV-21_ScanBarcodeExplode_Action, WRH_BarcodeExplode


The action flow:


1. The WRH_BarcodeExplode Operation is executed. 2. The system checks if it can recognize the Entity (Container/Inventory without Container)

prefix. 3. If the Entity prefix is recognized, the system move to Step 5. 4. If the Entity prefix is not recognized, the system tries to find the Entity based on its name. If

nothing is found, an error is displayed. 5. The system checks if Entity exists in the system. If it does not, the RCV-40 screen is

displayed. 6. If Entity exists, the system checks what type of Entity that is.

a. If it is Inventory without Container, the RCV-40 screen is displayed. b. If it is one-Item Container, the RCV-40 screen is displayed. c. If it is a mix or a multi-Item Container, the RCV-60 screen is displayed.


7 Screen DescriptionsThis section includes descriptions of the screens used in the Receiving application.

7.1 RCV-10The RCV-10 screen displays a list of Receiving Orders. It shows two types of Orders:

17-ASN Inbound Delivery Orders16-Purchase Orders

The screen is used by the Warehouse Operator to:

scan an Orderscan a Containerbrowse through displayed Ordersnavigate to the Order's details screen (7.2 RCV-20 for ASN Orders, 7.5 RCV-21 for Purchase Orders)

Figure 12 RCV-10 screen

The RCV-10 screen consists of the following elements:

1. The barcode field. 2. The number of Orders displayed in the screen.


3. The Orders list.

7.1.1 Barcode Field

The barcode field is used to scan Orders and Containers.

7.1.2 Orders List

Orders Status

An Order must be in one of the following Statuses to be displayed in the screen:

2-Started 7-Released

Orders Display Sequence

The Orders are displayed in the following sequence:

Orders assigned to the Warehouse OperatorOrders not assigned to anybody

Each of these groups is further sorted by:

Status ("Started" are at the top)Scheduled Reception date (the oldest at the top)

ASN Order Properties

Figure 13 RCV-10 screen – ASN Order properties

1. Indicator that Order is in the "Started" Status. 2. Order Number. 3. Order type. 4. Container icon. 5. The number of received Containers / total number of Containers. 6. Order Scheduled Reception date.

If no Containers have been received, the Container icon (4) and the number of Containers (5) are greyed out.

Purchase Order Properties


Figure 14 RCV-10 Purchase Order properties

1. Indicator that Order is in the "Started" Status. 2. Order Number. 3. Order type. 4. Container icon. 5. The number of received Containers. 6. Product icon. 7. The number of received Products. 8. Order Scheduled Reception date.

If no Containers or Inventories without Container have been received, their icons (4, 6) are greyed out.

7.2 RCV-20The RCV-20 screen displays a list of Containers for a selected ASN Order. The screen is accessed after selecting an ASN Order in the 7.1 RCV-10 screen.


browse through the Containers in the Orderreceive Containersput Containers awayprint labels for Containers(optional) complete an Ordernavigate to the 7.3 RCV-30 screen to view the Container content




1. Barcode field. 2. Multiselect button. 3. Selected Containers / all Containers. 4. Received Containers. 5. Put away Containers. 6. Containers list. 7. Receive, Put Away and Print buttons.

7.2.1 Barcode Field

The barcode field is used to scan Containers.

7.2.2 Multiselect Button

After tapping the multiselect button, you can:

select one or more Containers by tapping them.use Select All, Unselect All and Invert buttons. The first two buttons can be used to select/unselect all Containers at once. The Invert button can be used to invert current selection.


Figure 16 RCV-20 screen – Multiselect button

The multiselect button is also activated when you tap and hold a Container.

7.2.3 Containers List

The Containers list displays all the Containers in the Order. To select one or more Containers, tap and hold it, or use the multiselect button. To navigate to a Container, tap it – you will then be moved to the 7.3 RCV-30 screen where you can view the Container content.

Container Types

In the RCV-20 screen there may be the following types of Containers displayed:

One-Item Container

If a Container consists of one Item of the Product (placed directly in a Master Container or in a Child Container), the screen displays:

1. Product icon. 2. Product Quantity. 3. Product Unit of Measurement.

Figure 17 RCV-20 screen – One-Item Container

Multi-Item Container

If a Container consists of more than one Item of the same Product (placed directly in a Master Container or in Child Containers), the screen displays:

1. Product icon. 2. Product Quantity. 3. Product Unit of Measurement. 4. Items icon. 5. Number of Items.


Figure 18 RCV-20 screen – Multi-Item Container

Mix Container

If a Container consists of different Products, the screen displays:

1. Items icon. 2. Number of Items. 3. Indication that the Container is of a mix type.

Figure 19 RCV-20 screen – Mix Container

Container Remaining Properties

Apart from the properties typical for a given Container type, the system can display the following properties for all types of Containers:

1. Container Number. 2. Container Class. 3. Inventory Status. 4. Product name. 5. Product description.

Figure 20 RCV-20 screen – Container properties


7.2.4 Buttons

Receive

The button is used to receive a Container. Select the Container and tap the Receive button.

You can receive one or more Containers at a time.

Put Away

The button is used to put away a Container. Only received Containers can be put away.

Select the Container and tap the Put Away button. The Put Away dialog box will be displayed.

Figure 21 RCV-20 screen – Put Away dialog box

Enter the target Location and tap OK. The Container will be moved to the target Location.

You can put away one or more Containers at a time.

Print

The button is used to print a label for a Container. Select the Container and tap the Print button.

You can print labels for one or more Containers at a time, regardless of whether they have been received or not.

Currently the Print action is empty and needs to be configured by the user.

Receive, Put Away and Print buttons are also available in the 7.3 RCV-30 screen.

Complete

If all Containers within an Order have been received, it is possible to complete the Order using the Complete button.


The Complete button is not displayed in the screen by default. If you want it to be displayed, use a dedicated System Parameter. To learn more, refer to 9.1 Complete Button in the Configuration section.

Figure 22 RCV-20 screen – Complete button

7.3 RCV-30The RCV-30 screen displays the content of a selected Container belonging to an ASN Order. The screen is accessed after tapping a Container belonging to an ASN Order in the 7.2 RCV-20 screen.


change Inventory Statusreceive a Containerput a Container awayprint a label for a Containernavigate to the 7.4 RCV-50 screen to browse through Items in case of mix and multi-Item Containers

Depending on the Container type the RCV-30 displays different properties.


7.3.1 Mix Container


For a mix Container the RCV-30 screen displays:

1. Container icon (and indicators that the Container has been received or put away, if applicable).

2. Read-only field with information about a mix type of a Container and an editable Status field where you can change the Status of the Container.

3. Receive / Save, Put Away, Print and Items buttons.

To view the remaining properties of the Products in a mix Container, you need to navigate to the 7.4 RCV-50 screen by tapping the Items button.


7.3.2 One-Item and Multi-Item Containers

Figure 24 RCV-30 screen – One-Item/multi-Item Container

For one-Item and multi-Item Containers the RCV-30 screen displays:

1. Container icon (and indicators that the Container has been received or put away, if applicable).

2. Fields with Container properties. 3. Receive / Save, Put Away, Print and Items buttons.

To view the properties of the Items in a multi-Item Container, you need to navigate to the 7.4 RCV-50 screen by tapping the Items button.

Fields

Field DescriptionProduct The Product Number.


Product Description The description of the Product.Status The Inventory Status of the whole Master Container.Serial The Serial Number of the Product.Lot The Lot Number of the Product.Total Quantity (EA) The total Quantity of the Product (Unit of Measurement).

Buttons

Receive

The button is displayed if a Container has not been received. If the Warehouse Operator changes the Inventory Status, the Receive button will save the Status and receive the Container at the same time.

Save

The button is displayed if a Container has already been received. It is used to save the new Inventory Status.

Put Away

The button is used to put away the Container. After you tap the button, the Put Away dialog box will be displayed:


In the dialog box enter the target Location and tap OK. The Container will be moved to the target Location.

Print

The button is used to print a label for the Container. You can print a label for a Container regardless of whether it has been received or not.


Items


The button is available for mix and multi-Item Containers and is used to move to the 7.4 RCV-50 screen.

7.4 RCV-50The RCV-50 screen displays the properties of Items which are placed in a mix and a multi-Item Container belonging to an ASN Order.

The screen is accessed after tapping the Items button in the 7.3 RCV-30 screen.

The screen is read-only and it is used by the Warehouse Operator to browse through Items and view their properties.



Fields

Field DescriptionMaster Container The Master Container Number.Child Container The Child Container Number.Product The Product Number.Product Description The description of the Product.Serial The Serial Number.Lot The Lot Number.Total Quantity (EA) The total Quantity of the Product (Unit of Measurement).

7.5 RCV-21The RCV-21 screen displays a list of received content for a Purchase Order selected in the 7.1 RCV-10 screen. The content can include two types of Entities:

Containers with Inventory placed inside Inventory without Containers

When the term Entity is used in this document, it indicates Container as well as Inventory without Container.


browse through Entities in the Orderdelete Entitiesprint labels for Entities(optional) complete an Ordernavigate to the 7.6 RCV-40 screen to handle basic scenarios related to Order contentnavigate to the 7.7 RCV-60 screen to handle more complex scenarios related to Order content



The screen consists of the following elements:

1. Barcode field. 2. Multiselect button. 3. Selected Entities/all Entities. 4. Received Entities. 5. Put-away Entities. 6. Entities list. 7. New, Put Away, Print and Remove buttons.

7.5.1 Barcode Field

The barcode field is used to scan Containers or Inventory without Container.

7.5.2 Multiselect Button

After tapping the multiselect button, you can:


select one or more Entities by tapping them.use Select All, Unselect All and Invert buttons. The first two buttons can be used to select/unselect all Entities at once. The Invert button can be used to invert current selection.

Figure 28 RCV-21 screen – Multiselect button

The multiselect button is also activated when you tap and hold an Entity.

7.5.3 Entities List

The Entities list displays all of the Order's Containers and/or Inventory without Containers. To select one or more Entities, tap and hold it, or use the multiselect button. To navigate to an Entity, tap it – you will then be moved to the 7.6 RCV-40 or 7.7 RCV-60 screen, depending on the type of Entity.

Container Types

In the RCV-21 screen there may be the following types of Containers displayed:

One-Item Container

If a Container consists of one Item of the Product (placed directly in a Master Container or in a Child Container), the screen displays:

1. Product icon. 2. Product Quantity. 3. Product Unit of Measurement.

Figure 29 RCV-21 screen – One-Item Container

Multi-Item Container

If a Container consists of more than one Item of the same Product (placed directly in a Master Container or in Child Containers), the screen displays:


1. Product icon. 2. Product Quantity. 3. Product Unit of Measurement. 4. Items icon. 5. Number of Items.

Figure 30 RCV-21 screen – Multi-Item Containerr

Mix Container

If a Container consists of different Products, the screen displays:

1. Items icon. 2. Number of Items. 3. Indication that the Container is of a mix type.


Container Remaining Properties

Apart from the properties typical for a given Container type, the system can display the following properties for all types of Containers:

1. Container Number. 2. Container Class.

The Container Class is determined by the APR_WH_CONTAINER_CLASS Determination. To learn how the Determination works, refer to 9.3 Container Class in the Configuration section.

3. Inventory Status. 4. Product name. 5. Product description.


Figure 32 RCV-21 screen – Container properties

Inventory Without Container

For Inventory without Container the screen can display:

1. Product Number. 2. Product description. 3. Product Lot Number/Serial Number. 4. Product Quantity. 5. Product Unit of Measurement. 6. Product Inventory Status. 7. Product Inventory Type.

Figure 33 RCV-21 screen – Inventory without Container

7.5.4 Buttons

New

The button is used to navigate to the 7.6 RCV-40 screen where a new Entity can be created.

The New button is enabled if a given Order has an Order Line in one of the following Statuses:

1-New2-Started7-Released

If none of the Order Lines is in one of these Statuses, the New button is disabled and creating new content is impossible in this Order.


Put Away

The button is used to put away an Entity. Select the Entity and tap the Put Away button. The Put Away dialog box will be displayed.


Enter the target Location and tap OK. The Entity will be moved to the target Location.

You can put away one or more Entities at a time.

Print

The button is used to print labels for Entities. Select the Entity and tap the Print button.

If you want to print labels for more than one Entity, you can do this, provided that you select Entities of the same type (either Containers or Inventories without Container).


Remove

The button is used to remove Entities. Select the Entity and tap the Remove button.

You can remove one or more Entities at a time.

Entity which has been put away cannot be removed.

Complete

It is possible to complete the Order using the Complete button. The button is not displayed in the screen by default. If you want it to be displayed, use a dedicated System Parameter. To learn more, refer to the 9.1 Complete Button in the Configuration section.

Figure 35 RCV-21 screen – Complete button


7.6 RCV-40The RCV-40 screen is used to execute basic scenarios related to Purchase Order content. To execute more complex scenarios you will need to navigate to the 7.7 RCV-60 screen.


create Inventory without Container, one-Item Containers, and multi-Item Containers with Child Containers having the same number of the same Product handle existing Inventory without Container and one-Item Containers

To create or handle all other multi-Item Containers or mix Containers you need to navigate to the 7.7 RCV-60 screen by tapping the Items button.



1. The barcode field. 2. Property fields.


3. Receive, Put Away, Print and Items buttons.

7.6.1 Barcode Field

The barcode field is used to scan Containers or Inventory without Container. After parsing prefixes the following fields can be populated:

Master ContainerProductSerial Lot Quantity (if Quantity prefix is specified and has been found in the scanned barcode)

7.6.2 Property Fields

Field DescriptionMaster Container The Master Container Number.Inventory Status The Inventory Status of the Master Container (to learn more,

refer to 9.2 Inventory Status in the Configuration section).Product The Product Number.Product Description The description of the Product.Serial The Serial Number of the Product.Lot The Lot Number of the Product.Quantity The Quantity of the Product (per Child Container when Child

Containers field is active).

If the Fraction Allowed option is selected in the Product Maintenance M&M screen, it is possible to enter fractions in the Quantity field. Otherwise, if a fraction is entered into the field, the system will round the provided Quantity to an integer.

Child Containers (available only when creating new Entity and after selecting the checkbox above the field)

The number of Child Containers with the same Quantity of the Product.

7.6.3 Buttons

The following buttons are available in the RCV-40 screen:

Receive


New Entity:

The button is used to save the new Entity with all its properties and receive it.

Existing Entity:

Once a new Inventory Status is selected, the button changes into Save and is used to save the changes to the Status.

Put Away

The button is used to put away the Entity. After you tap the Put Away button, the Put Away dialog box will be displayed:


In the dialog box enter the target Location and tap OK. The Entity will be moved to the target Location.

Print

The button is used to print a label for the Entity.

Items

The button is used when you want to execute more complex scenarios related to Order Content – to create or handle mix Containers or multi-Item Containers. After tapping the button you are moved to the 7.7 RCV-60 screen.

The button is not available for Inventory without Container.

Remove

The button is only available for Inventory without Container. If you want to remove a Container, you need to navigate to the 7.7 RCV-60 screen.

If Inventory without Container has been put away, it cannot be removed.

Generate Master Container


The button is available only in case of creating a new Entity. After tapping the button the WRH_GenerateContainerNo_Action Operation is called and the Container Number is generated from the WMS_CONTAINER sequence.

7.6.4 Creating New Entity and Handling Existing Entity

Below you can find the details of what you can do when creating a new Entity and handle an existing one in the RCV-40 screen.

New Entity

The screen is accessed after tapping the Create button in the 7.5 RCV-21 screen.

In the screen the Warehouse Operator can:

create Inventory without Containercreate one-Item Containercreate a multi-Item Container including Child Containers with the same number of the same Products (after creation the Container will be later displayed in the 7.7 RCV-60 screen)move to the 7.7 RCV-60 screen to create a more complex multi-Item Container or a mix Containerreceive the Entityput away the Entityprint a label for the Entity

If in the process of creating a Container in the RCV-40 you decide you want it to be a mix Container or a more complex multi-Item Container, you can tap the Items button to navigate to the 7.7 RCV-60 to continue. You can do this at any time before tapping the Receive button.


Figure 38 RCV-40 screen – New

Creating Master Container

To create a Container:

1. Create a Master Container. A new Master Container can be created in one of the following ways: a. scanning the Container Number (or entering it manually into the Master Container field)

– the system will try to create the Container with the specified name (the validation takes place after the Receive button is tapped)

a. tapping the button next to the Master Container field 2. Scan the Product (or select it by tapping the button next to the Product field). After the

Product is entered, the Inventory Status field is populated with the right Status. The Status is determined by the APR_WH_INVENTORY_STATUS Determination. To learn more about how the Determination works, refer to 9.2 Inventory Status in the Configuration section.


If you fill the Inventory Status field before entering the Product, and enter the Product afterwards, the system will keep the Status that you have entered and the APR_WH_INVENTORY_STATUS Determination will not be used.

3. If the Product is tracked by Serial or Lot Number, complete the required fields.

If the Product is tracked by Serial Number the Quantity is always 1 and you cannot define the number of Child Containers.

If the Product is not tracked by Serial Number, you need to specify the Quantity and optionally the number of Child Containers (to specify the number of Child Containers select the checkbox above the Child Containers field).

4. Tap the Receive button. If you provided the number of Child Containers the WRH_GenerateContainerNumbersWithValidation_Action Operation is called and the Child Containers are generated.

Creating Inventory Without Container

To create Inventory without Container:

1. Scan the Product (or select it by tapping the button next to the Product field). After the Product is entered, the Inventory Status field is populated with the right Status. The Status is determined by the APR_WH_INVENTORY_STATUS Determination. To learn more about how the Determination works, refer to 9.2 Inventory Status in the Configuration section.


2. If the selected Product is tracked by Serial and Lot Number, complete the required fields. If the selected Product is tracked by Serial Number the Quantity is always 1.

3. Tap the Receive button.

Existing Entity

The screen is accessed after tapping one of the two types of an Entity in the RCV-40 screen:

One-Item ContainerInventory without Container

The screen can be used by the Warehouse Operator to:

view the properties of the Entity change the Entity Inventory Status (disabled when Entity has been put away)put away the Entityprint a label for the Entity


remove the Entity (only applicable for Inventory without Container, disabled when Inventory without Container has been put away)move to the 7.7 RCV-60 screen to execute more actions (not applicable for Inventory without Container)

Figure 39 RCV-40 screen – Existing Entity

7.7 RCV-60The RCV-60 screen is used to execute complex scenarios related to Order Content. To handle more basic scenarios navigate to the 7.6 RCV-40 screen.

In the RCV-60 screen you can create and handle mix Containers and multi-Item Containers. You can access the screen after tapping:

a mix Container in the 7.5 RCV-21 screena multi-Item Container in the 7.5 RCV-21 screenthe Items button in the 7.6 RCV-40 screen



add Items to a new or existing Containerview the properties of the Container and its contentchange the Inventory Status

If you change the Inventory Status of one Item within the Container, the Status of all the other Items within this Container will be changed accordingly.

browse through the Container's Itemsput away the Containerremove Items from the Container (disabled when Container has been put away)

The action of removing the last Item in a Container removes the whole Container.

print a label for an Item

Figure 40 RCV-60 screen – Existing Entity



1. The barcode field. 2. Property fields. 3. Buttons

7.7.1 Barcode Field

The barcode field is used to scan Containers. After parsing prefixes the following fields can be populated:

Master ContainerProductSerial Lot Quantity (if Quantity prefix is specified and has been found in the scanned barcode)Child Container (only if Master Container field was already populated)

7.7.2 Property Fields

Field DescriptionMaster Container

The Master Container Number.

Inventory Status

The Inventory Status of the whole Master Container.

Product The Product Number.Product Description

The description of the Product.

Serial The Serial Number of the Product.Lot The Lot Number of the Product.Quantity The Quantity of the Product.

If the Fraction Allowed option is selected in the Product Maintenance M&M screen, it is possible to enter fractions in the Quantity field. Otherwise, if a fraction is entered into the field, the system will round the provided Quantity to an integer.

Child Container

The Child Container Number.

7.7.3 Buttons

Prev / Next

The buttons are used to browse through Items.

New


The button is used to add a new Item to the Master Container.

ReceiveNew Item:

The button is used to save the new Entity with all its properties and Receive it.

Existing Item:

Once a new Inventory Status is selected, the button changes into Save and is used to save the changes to the Status.

Put Away

The button is used to put away Container. After you tap the Put Away button, the Put Away dialog box will be displayed:


In the dialog box enter the target Location and tap OK. The Entity will be moved to the target Location.

Print

The button is used to print a label for the Item.

Remove

The button is used to remove the Item.

The action of removing the last Item in a Container removes the whole Master Container.

If Container has been put away, its content cannot be removed.

Generate Master Container/Child Container

After tapping the button the WRH_GenerateContainerNo_Action Operation is called and the Container Number is generated from the WMS_CONTAINER sequence.


7.7.4 Adding New Item To Master Container

The logic which applies to adding an Item to a Master Container in the RCV-60 screen is the same as the logic standing behind creating a Container in the 7.6 RCV-40 screen. The only difference is that instead of the Child Containers field (which is used to define the number of Child Containers) there is a Child Container field which is used to generate a Child Container.

The scenario below describes the full flow of creating a new Container in the RCV-60 screen. If you have already started creating the Container in the 7.6 RCV-40 screen or you add Items to an existing Container, you will not have to follow all the steps, because some of the fields will be already filled.

1. Create a Master Container. A new Master Container can be created in one of the following ways: a. scanning the Container Number (or entering it manually into the Master Container field)

– the system will try to create the Container with the specified name (the validation takes place after the Receive button is tapped).

a. tapping the button next to the Master Container field. 2. When you add a first Item to the Master Container – scan the Product (or select it by tapping

the button next to the Product field). If you do not fill the Inventory Status field, after entering the Product the Inventory Status field will be populated by the APR_WH_INVENTORY_STATUS Determination. To learn more about how the Determination works, refer to 9.2 Inventory Status in the Configuration section.

When you add the next Item to the existing Master Container, the Product field will already be populated by the last received Item. The Inventory Status field will be already filled too.

The Inventory Status field displays the Inventory Status of the entire Container. Changing the Status in any Item results in changing the Status of the whole Container.

3. If the Product is tracked by Serial or Lot Number, complete the required fields.

If the Product is tracked by Serial Number the Quantity is always 1.

If the Product is not tracked by Serial Number, you need to specify the Quantity. Optionally you can define a Child Container with the Product – to do this scan the Child Container or generate it by tapping the button next to the Child Container field.

4. Tap the Receive button.


8 ResultsThe results of all the actions in the Receiving application are:

1. Containers and Inventory received or put away. 2. Updated information about Statuses of Orders Lines.


9 Configuration9.1 Complete ButtonIf all Containers within an Order have been received, it is possible to complete the Order using the Complete button.

The button can be displayed in the following screens:

7.2 RCV-207.5 RCV-21

To have the Complete button displayed in the screen set the APR_RCV_EnableCompleteOrder System Parameter to True.

9.2 Inventory Status When you create a new Entity (Container or Inventory without Container) the Inventory Status field is populated by default with the Status determined by the APR_WH_INVENTORY_STATUS Determination. The Determination is used to populate the Inventory Status field only after a Product has been scanned or typed in.

The APR_WH_INVENTORY_STATUS Determination is based on three variables: Employee, Product and Supplier. During validation the system looks for the default Status in the APR_WH_INVENTORY_STATUS Determination and populates the Inventory Status field if default Status is found. The system works according to the following flow:

1. The system looks for default Status for provided Employee, Product and Supplier. 2. If Status is not found, the system looks for default Status for one of the variables being null

and the remaining two as provided. If more than one Status is found, the first one which matches is used.

3. If Status is not found, the system looks for default Status for two of the variables being null and the remaining one as provided. If more than one Status is found, the first one which matches is used.

4. If Status is not found, the system looks for default Status for Employee, Product and Supplier fields being null.


9.3 Container ClassThe Container Class displayed in the 7.5 RCV-21 screen is determined by the APR_WH_CONTAINER_CLASS Determination. The Determination is based on two variables: Supplier and Product. During validation the system looks for the default Container Class in the


Determination and populates the Container tile if the default Class is found. The system works according to the following flow:

1. The system looks for Class for provided Supplier and Product. 2. If Class is not found, the system looks for one of the variables being null and the other one

as provided. If more than one Class is found, the first one which matches is used.

Container Class is displayed only for Master Containers. It is never displayed for Child Containers.

9.4 Prefixes RecognitionWhen the Warehouse Operator scans a barcode, the system recognizes the Prefix and populates the screen with data.

In the Receiving app prefixes can be recognized for the following Object Types:

ContainerProductLot NumberSerial NumberQuantity (if Quantity prefix is specified and has been found in the scanned barcode)

To learn how Prefixes are configured so that they can be recognized when an Entity is scanned, refer to Prefix Management Cockpit Detailed Design.

9.5 Automatic Order Line Completion

Automatic Order Line completion is available only for Purchase Orders.

Automatic Order Line completion is a functionality which allows for completing an Order Line during Receiving process in the Receiving app.

Automatic Order Line completion is based on the Completed Quantity set for an Order Line. The Order Line can be automatically completed if the value of the Completed Quantity is greater than or equal to Ordered Quantity and less than or equal to Ordered Quantity enlarged by the Over Tolerance percentage.

Order Line completion is dependent on the APR_INV_AutoCompleteLineScenario System Parameter value:

0 – automatic Order Line completion is disabled1 – Order Line will be completed automatically without any message2 – Order Line will be completed automatically with the "Order Line completed." message3 – before completion a dialog box will be displayed where the Warehouse Operator can decide whether they want to complete this Order Line:


Figure 42 Complete Order Line dialog box

By default the APR_INV_AutoCompleteLineScenario System Parameter is set to 1.


10 Put Away ApplicationIn DELMIA Apriso WMS solution Entities can be put away in two applications: the Receiving app and the Put Away app.

The Put Away (PTA) app is a stand-alone app dedicated just for putting away Entities.

Figure 43 Put Away application

The put away logic is very similar in both apps, however there are some differences:

Receiving App Put Away AppIt is possible to put away Containers as well as Inventory without Container.

It is possible to put away only Containers.

It is possible to put away one or more Containers/Inventories without Container at a time.

It is possible to put away only one Container at a time.

Container/Inventory without Container can be put away only one time.

Container can be put away as many times as needed.

Container/Inventory without Container must belong to a Receiving Order.

Container does not need to belong to a Receiving Order.

It is not possible to move Child Container.

It is possible to move Child Container (but only if it does not belong to a Receiving Order and if the APR_PTA_AllowPutawayInnerContainer System Parameter is set to True).


All the internal documents referenced in this section are available from the DELMIA AprisoStart page, which can be accessed on your DELMIA Apriso server (<server name>/apriso/start).The newest versions of all documents are available from 3DS Support at:http://www.3ds.com/support/documentation/overview/

11 ReferencesInternal Documentation

1. WMS - Conceptual Design

Provides the conceptual design of Warehouse Management System that includes a configuration specification, functional description, and Process flow in the respective business areas.

2. WMS - Technical Design

Describes the technical design of the Warehouse Management System (WMS). The document includes descriptions of Screen Flows, Standard Operations, Extension Points, System Parameters, Determinations, etc.

3. WMS - Inventory Lookup Cockpit Detailed Design

Describes the detailed design of Inventory Lookup Cockpit for Warehouse Management System. The document includes descriptions of various Process aspects such as the prerequisites, assumptions, Process flow description, and Process results.

4. WMS - Inventory Operations Detailed Design

Describes the detailed design of the Inventory Operations for Warehouse Management System. The document includes descriptions of various Process aspects such as the prerequisites, assumptions, Process flow description, and Process results.

5. WMS - Interfaces Detailed Design

Describes the detailed design of Interfaces for Warehouse Management System.

6. WMS - Prefix Management Cockpit Detailed Design

Describes the detailed design of Prefix Management Cockpit for Warehouse Management System. The document includes descriptions of various Process aspects such as the prerequisites, assumptions, Process flow description, and Process results.

7. WMS - Receiving Cockpit Detailed Design

Describes the detailed design of Receiving Cockpit for Warehouse Management System. The document includes descriptions of various Process aspects such as the prerequisites, assumptions, Process flow description, and Process results.

8. WMS - Shipping Detailed Design


http://www.3ds.com/support/

All the internal documents referenced in this section are available from the DELMIA AprisoStart page, which can be accessed on your DELMIA Apriso server (<server name>/apriso/start).The newest versions of all documents are available from 3DS Support at:http://www.3ds.com/support/documentation/overview/

Describes the detailed design of Shipping for Warehouse Management System. The document includes descriptions of various Process aspects such as the prerequisites, assumptions, Process flow description, and Process results.

9. WMS - Shipping Cockpit Detailed Design

Describes the detailed design of Shipping Cockpit for Warehouse Management System. The document includes descriptions of various Process aspects such as the prerequisites, assumptions, Process flow description, and Process results.

3DS Support Knowledge Base

If you have any additional questions or doubts not addressed in our documentation, feel free to visit the 3DS Support Knowledge Base at https://www.3ds.com/support/knowledge-base/.


http://www.3ds.com/support/

https://www.3ds.com/support/knowledge-base/

WMS - Receiving

Documents

Transcript of WMS - Receiving