An Incoming Shipment can be exported to PDF (and printed) by selecting the option “Reception” in the action menu (under “Reports”).
It can also be exported to Excel (XML Spreadsheet 2003 format) by selecting the option “XMLExport” in the action menu (under “Reports”) although this will only be possible for “Closed” Incoming Shipments.
Exporting an Incoming Shipment to PDF
Incoming Shipment exported to PDF
Note: On the PDF, “Cancelled” lines will not be displayed.
Incoming Shipments (INs) refer to all deliveries that you expect from a partner which can be internal (coordination or a project), external (a supplier), ESC (an MSF European Supply Centre), inter-mission (a coordination instance from your section) or inter-section (a coordination instance from another section). An Incoming Shipment is usually created automatically (in state “Available”) following the confirmation of a Purchase Order (or a PO-line in case of partial PO confirmation) in order to prepare the reception, even if goods could only be delivered by the supplier in some weeks/months. The initial Incoming Shipment document will have the same information (products, quantities, supplier, expected receipt date,…) as the corresponding confirmed PO (or PO-line).
Note that an Incoming Shipment can also be created manually (from scratch) but this is not the normal process and it will only be done in exceptional circumstances.
Products received through Incoming Shipments are often received in the “Input” location (which is a location where quality analysis of received products should be performed) and then transferred to another location (where the products are actually expected). By default, the system will do this automatically in a “one step” process, unless the user activates the “two steps” reception process by anticking the “Direct to Requesting Location” checkbox (and in this case, the user will have to process the second step manually through the processing of an Internal Move (INT) from the “Input” location to the final destination location).
Another option is to receive the products in the “Cross docking” location and transfer them to another destination (internal partner or external consumption unit) via another movement.
An Incoming Shipment is actually a movement from a source location to a destination location. Source location will usually be “Other Supplier” or “MSF Supplier” while the destination location will be “Input” or “Cross docking“.
An Incoming Shipment is very often associated to an Internal Move (INT created automatically and processed either manually either automatically) which is actually another type of movement. The source location of this movement will be “Input” while its destination location will be the final destination of the goods (stock, ICU,…).
An Incoming Shipment can also be associated to a Delivery Order (OUT created automatically but always processed manually) which is another type of movement. The source location will be “Cross docking” while the destination location will be the final destination of the goods (ECU, “MSF Customer”, “Other Customer”).
Finally, an Incoming Shipment can be associated to a Picking Ticket (PICK created automatically and processed manually) which is another type of movement. The source location will be “Cross docking” while the destination location will be the “Packing” location, used to prepare parcels to be shipped to other instances.
This chapter covers all the necessary functionalities related to warehousing. It is divided in three parts: deliveries (inbound and outbound), stock management and reporting.
The deliveries part deals with the reception (IN) and the delivery (OUT) of products in UniField. This includes receiving partial deliveries, receiving alternative goods, processing goods with expiry dates and batch numbers, picking products, packing products, processing outgoing shipments, … The system offers a wide range of functionalities to process these types of warehouse related operations.
The stock management part explains all the necessary functionalities needed to manage a warehouse with UniField. This includes moving goods from a location to another, addressing a claim to a supplier, recording the consumption of products, managing kits, creating inventories, …
The reporting part focuses on reports which are available in UniField to allow traceability, consumption analysis and stock analysis.
Receptions and deliveries are actually movements from one location to another. As we will see, many transactions used in warehouse management trigger the creation of a movement. A movement always has a source location and a destination location.
Stock management in UniField can be compared to a double-entry system in accounting. The stock levels (or stock quantities) do not appear and vanish magically within the warehouse, they are just moved from one location to another and, just like accounting, the double-entry system offers a big advantage for tracing missing stock or inaccurate counts, as you can trace a product’s movements and search for source and destination locations.
In UniField, the inventory management of stocks is based on a hierarchical locations structure, from warehouse to intermediate stocks and consumption units (depending on the warehouse set up). UniField has the capacity to manage batch numbers and expiry dates so as to ensure compliance with the traceability requirements.
The warehouse is designed to reflect physical and non-physical locations from which you can deliver products to the customers and into which you can receive products from suppliers. Furthermore, as stock locations are hierarchically organized, you can carry out analysis at various levels of detail.
UniField also introduces the concepts of “virtual stock” (which can be understood as “future stock”) and “available stock” (which can be understood as “non-reserved” stock). These concepts are very useful to have an overview of products availability analysis and projection in the supply chain.
Throughout this chapter, you will find many acronyms. They are mostly used to shorten English words but can be used in the English manual or the French manual (i.e. you may find the acronym PPL in the French version of the manual). In the below table, you find the main acronyms used in this chapter with their meaning.
French acronyms, such as the names of the documents in French in a less extend, are barely used. English acronyms and documents names are usually preferred. In the software, references of documents are often built with the English acronyms of the documents (e.g. 18/HQ/MW101/PO00045, PPL/00033-01, OUT/00028,…), independently of the language in which the software is used.
The language in which UniField is developed is English. The software is then translated in French. That’s the reason why, even if you are connected in French, you could still find some English terminology (on screens, in messages…) while working on UniField. The translation of the software in French is a work in process and some improvements are still needed on this side.
The below steps show how to cancel & resource a validated Purchase Order which has been generated by the OST following the sourcing of an FO on order.
Go to:Purchases / Purchase Management / Purchase Orders
Click on the line of the Purchase Order on which you need to cancel & resource.
Click on the “Cancel document” button at the bottom of the PO screen.
Cancelling an entire PO
3. Select “Cancel & Resource” on the pop-up window.
Cancelling & Resourcing an entire PO
4. The PO switches to state “Cancelled” while the PO-lines switch to state “Cancelled-r” (use the filter at the top of the “Lines” table to see them).
Cancelled & Resourced PO
5. On the FO which was sourced on order, the original lines switch to state “Cancelled-r” and new lines (copy of the original ones) are added in state “Resourced-v“. These lines can be resourced in the OST. Note that the FO is in state “Sourced-p“.
The below steps show how to cancel & resource 1 line of a draft Purchase Order which has been generated by the OST following the sourcing of an IR on order.
Click on the line of the Purchase Order on which you need to cancel & resource.
Click on the red cross at the right end of the product line.
Cancelling a PO-line
3. Select “Cancel & Resource” on the pop-up window.
Cancelling & Resourcing a PO-line
4. The cancelled & resourced PO-line switches to “Cancelled-r” state (you need to “Show all” lines to see this line) while the PO stays in state “Draft”.
Cancelled & Resourced line on a draft PO
5. On the IR which was sourced on order, the original line switches to state “Cancelled-r” and a new line (copy of the original one) is added in state “Resourced-v“. The reference of the original Cancelled line number is displayed at line level in column “Original IR/FO line”. This line can be resourced in the OST. Note that the IR keeps the status “Sourced“.
Cancelled & Resourced line on the IR
Note that cancelling & resourcing 1 PO line can also be done if the PO is validated. In this case, the scenario is the same but the PO header ends up in state “Validated” while the IR header is in state “Sourced-p“.
The below steps show how to cancel & resource 1 line of a draft Purchase Order which has been generated by the OST following the sourcing of an FO on order.
Go to:Purchases / Purchase Management / Purchase Orders
Click on the line of the Purchase Order on which you need to cancel & resource.
Click on the red cross at the right end of the product line.
Cancelling a PO-line
3. Select “Cancel & Resource” on the pop-up window.
Cancelling & Resourcing a PO-line
4. The cancelled & resourced PO-line switches to “Cancelled–r” state (you need to “Show all” lines to see this line) while the PO stays in state “Draft“.
Cancelled & Resourced line on a draft PO
5. On the FO which was sourced on order, the original line switches to state “Cancelled-r” and a new line (copy of the original one) is added in state “Resourced-v“. This line can be resourced in the OST. Note that the FO keeps the status “Sourced“.
Cancelled & Resourced line on the FO
Note that cancelling & resourcing 1 PO line can also be done if the PO is validated. In this case, the scenario is the same but the PO header ends up in state “Validated” while the FO header is in state “Sourced-p“.
Cancelled & Resourced line on validated PO
Cancelled & Resourced line on the FO
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
