¶ OVERVIEW
¶ The Receiving process consists of the following core features:
Refer to the process flow for more detail.
- Support for Pallet based, or Item based receiving.
- Expiry, Batch/Lot, Serial capture and validation.
- Blind receiving, or Item and Qty validation receiving.
- Allow over receipt (YES/NO)
- Allow under receipt (YES/NO)
- Back orders allowed (YES/NO)
- Trusted receiving (For Qwix WH transfers or where ASN is available)
The users involved in the Receiving process are two main groups:
1. Administrators/Supervisors
These Users predominantly utilize the Qwix Admin Application, and interact with the system to manage and monitor:
- The Purchase Order View
- Release Order (Desktop)
- Print Labels (Desktop)
- Assign scanners (Desktop)
- Monitor receipt (Desktop)
- Evaluate, issue resolution and complete receipt (Desktop)
- Receiving Performance Dashboard
2. Operators
These users are responsible for the execution of the receiving instructions. They do the following:
- Capture: (Performed on the mobile scanner)
- Pallet (If pallet-based receiving)
- Item (If blind receiving then capture Item, or just validate)
- If instructed item switching allowed
- Batch/Lot (If Batch/Lot enabled and item master data set)
- This could come from the barcode or user prompted.
- Expiry date (If expiry is a selected option)
- This could come from the barcode or user prompted.
- Quantity (If instructed allow or deny over receipt)
¶ TYPICAL OPERATING ENVIRONMENT
The main Area of operation of the Receiving process is within the confines of the warehouse receiving area:
- The Receiving process is executed in the Warehouse where raw materials or finished goods are brought into the operation.
- The Qwix Admin application is run on Microsoft Windows based computers.
- The main receiving functions are executed on Mobile Devices used by the operators in the warehouse.
- Labels are printed to dedicated label printers at printing stations in the warehouse.
- The mobile devices are served by a Wi-Fi network providing coverage for the entire operational area within the warehouse.
¶ PROCESS MODEL
¶ PROCESS INITIATION
¶ Import Integration
Integration of the Inbound Documents from the customer ERP System or through manual files, will need to be implemented. These import functions will be implemented in the Qwix AIR application.
Typical source documents include:
There is also the requirement for the master data to be integrated or captured to support this process. This master data information includes the following but may not be limited to this.
¶
¶ PROCESS EXECUTION
¶ Desktop Administration
The Qwix administration desktop can be used to View, Process and Monitor the receiving instructions through the Purchase Order View. Please visit the related document on how the View is used.
¶ Mobile Execution
¶ Main Menu
Once the user logs on to the device, he may navigate to the “Transfers” screen via the main menu. This menu is customizable for users/roles, but for the scope of this project it will be fixed to limited options.
¶ Transfer
Once the User is in the Transfer screen, he/she will see that a receiving instruction is assigned at the top of the screen. From here they will follow the system prompts. These will differ depending on the way the system has been setup and the options selected in the QWIX Standard Configuration. Shown here are some typical screen flows.
|
Receiving will normally be a BIN External just meaning that it is coming from outside the warehouse.
|
 |
|
If the pallet receiving option is configured. The user will scan the pallet/package label. If the item receiving option is configured then the user will proceed straight to scanning the item. The user will then scan the item barcode. |
 |
|
If the system is using Batch and the Item is setup as a Batch managed Item.
|
 |
|
If the system is using Batch and the Item is setup as a Batch managed Item, or the Item is setup as an expiry managed Item.
|
 |
| The user then needs to confirm the quantity being received, They will the select FUNC and NEXT if there are still more pallets or items, or FINISH if all pallet or items have been received. |
 |
¶
¶ PROCESS FINALIZATION
¶ Desktop Administration
¶ INTEGRATION – Write-back
Once the Inbound Document has been processed the receipt information needs to be written back to the ERP system. The technical details of the writeback will depend on the ERP system and what interface formats are supported. The typical information of this writeback will include the Document number, Item, Quantity, Batch (If batch used).
¶ Status Update
The Qwix system uses an automation engine built into the Qwix Air module. This is used to automate steps within Qwix. These happen without the user being required to do anything and should happen with a frequency that the user does not realize these are being performed. In the case of the receiving module the automations perform the following functions:
- Change the receiving document status.
- Create put-away instruction.
¶
¶ CONFIGURATION OPTIONS
The receiving process will cover the move of materials from external to the warehouse into the warehouse. This will include some options which are standard to allow common variation of process to be included in the standard product.
Variations include but may not be limited to:
- Pallet based or Item based receiving.
- Expiry, Batch/Lot, Serial required.
- Blind receiving, or Qty validation receiving.
- Allow for over receipt (YES/NO)
- Allow for under receipt (YES/NO)
- Back orders allowed (YES/NO)
- Trusted receiving support (YES/NO)
¶
¶ AUTOMATION SUMMARY
The Qwix system uses an automation engine built into the Qwix Air module. This is used to automate steps within Qwix. These happen without the user being required to do anything and should happen with a frequency that the user does not realize these are being performed. In the case of the receiving module the automations perform the following functions:
- Execute purchase order integration.
- Create receiving instructions.
- Status Update.
- Execute writeback integration.
- Create put-away instructions (Next process)
¶ STANDARD REPORTS
¶ PROCESS STEP DESCRIPTION
| ERP System | |
| 1. Inbound documents are created in the customer ERP system. | System |
| Qwix WMS | |
| 2. These inbound documents are imported into the Qwix database through the integration engine (Qwix Air). These documents then wait in Qwix for the items to be available for receipt. | System |
| Qwix Desktop | |
| 3. The stock becomes available for receipt. This would typically be through the supplier delivering the required goods. | Manual |
| 4. The delivery paperwork is received. From this there should be a reference to the inbound document number. This allows the user to find the document on the Qwix administration desktop. | User |
| 5. The user captures the delivery quantities into Qwix. This is used for the receipt validation and is done through the Qwix administration desktop. | User |
| 6. The user captures the delivery note reference. This reference can be written back into the ERP system as this is often used for further financial processing. | User |
| 7. The user will then select and release the inbound document for receipt on the Qwix administration desktop. The system will then creation the receiving instructions. | User |
| 8. The user will then assign the receiving instructions to the scanner of the operator that will capture the receiving on the operational floor. | User |
| 9. OPTION: If the system is set for pallet receiving then steps 10 and 11 will be performed. If the system is set for Item based receiving, then the process proceeds from step 12. | System Option |
| 10. The user can generate and print pallet barcode labels from the Qwix administration desktop, often also referred to as pallet license plate labels. Here we refer pallets, but this can be any grouping of Item or Items into a package, that can then be moved as a single unit. | User |
| Qwix Scanner | |
| 11. The operator will logon to the Qwix scanner application if not already done. They will then proceed to the transfers menu option to find the receiving instructions assigned to them. From here they will apply the pallet label to the Pallet/Package. They will scan the label to capture that Pallet number into the scanner application. | Operator |
| 12. The operator scans the item barcode to identify the items. Based on the quantity representation of this barcode the system will reflect that qty as being scanned. | Operator |
| 13. OPTION: The system will respond differently based on some master data that identifies if the product requires to be batch/lot, expiry, or serial managed. If none of these are required then the process procedure to step 18. | System Option |
| 14. If Batch/Lot required, and it is not imbedded in the item barcode, then the operator will be prompted to capture the Batch/Lot number. This is always coupled with Expiry in step 15. | Operator |
| 15. If expiry is required, and it is not imbedded in the item barcode, then the operator will be prompted to capture the expiry date. | Operator |
| 16. If this item is serial managed, and it is not imbedded in the item barcode, then the system requests the user to capture the serial number. NOTE: With serial number items they need to be processed one item at a time, as each item requires a serial number to be captured. | Operator |
| 17. OPTION: If there are more serial numbers to be captured then repeat step 16 until all are captured. | Operator Option |
| 18. The operator will be required to capture, adjust, or confirm the quantity. This will depend on whether each item was scanned, or one item scanned, and the quantity entered. | Operator |
| 19. OPTION: If the system is set for pallet receiving and there are more pallets, then return to step 11. If the system is set for Item based receiving and there are more items to receive, then return to step 12. If nothing more to receiving, then proceed with the next step. | Operator Option |
| 20. The operator will return the paperwork to the inbound clerk for further processing of the inbound document. | Operator |
| 21. From here the process splits with both paths being performed. | |
| 22. The operator will wait for his next inbound receipt to be performed. | Operator |
| 23. The process exits | Exit |
| Qwix Desktop | |
| The user on the Qwix administration desktop will validate that the receipt quantities and information that the operator captured look correct. This will look at the inbound document quantities, the delivery quantities that were captured, and the receipt quantities that were captured. This allows the user to evaluate if there are any issues that need to be checked. | User |
| 24. The supervisor can be dispatched to check any concerns. | Manual |
| 25. If there are any discrepancies or concerns remaining, these can be double checked or resolved through a series of options. | Manual |
| 26. Reset, and reprocess the inbound document. |
Desktop/ Scanner |
| 26. Reopen the receiving and capture additional items or quantities. |
Desktop/ Scanner |
| 26. Remove items or pallets. |
Desktop |
| 27. With issues resolved the user will confirm the receipt. | User |
| Qwix WMS | |
| 28. The system will then write the receipted information back to the ERP system. | System |
| 29. If require, Qwix can print the receipt documents as a reference to both the company and the supplier. | |
| ERP System | |
| 30. Here the process ends ready for the next process which is the Put-away of inbound stock. | Exit |
¶