Slide 1

Slide notes: In this tutorial we look at the 1st step for Stock Transfers by Dispatch. The Dispatch method for Stock Transfers is typically used when Stock is moved between geographically separated Stores. Therefore, the dispatch is 1st processed at origin, and then processed again as a Receipt of Stock at the Receiving Store.

 

 

 

 

Slide 2

Slide notes:

 

 

 

Slide 3

Slide notes: We start by looking at the Capture method.

 

 

 

Slide 4

Slide notes:

 

 

 

Slide 5

Slide notes: An internal document number may be supplied, or else the lookup can be used to generate a unique document number.

 

 

 

Slide 6

Slide notes:

 

 

 

Slide 7

Slide notes:

 

 

 

Slide 8

Slide notes:

 

 

 

Slide 9

Slide notes:

 

 

 

Slide 10

Slide notes:

 

 

 

Slide 11

Slide notes:

 

 

 

Slide 12

Slide notes: A Dispatch Stock Transfer is from 1 Store to 1 other Store. Therefore, to transfer various Stock Items from 1 Store to multiple other Stores, we will create multiple dispatches. For this dispatch, we are transferring Stock from Store 01 to Store 02.

 

 

 

Slide 13

Slide notes:

 

 

 

Slide 14

Slide notes:

 

 

 

Slide 15

Slide notes: For each Stock Item to be transferred, we capture the Stock Code and the Quantity to transfer.

 

 

 

Slide 16

Slide notes:

 

 

 

Slide 17

Slide notes:

 

 

 

Slide 18

Slide notes:

 

 

 

Slide 19

Slide notes: There is no limit to the number of Stock Items that can be included in a Transfer, and each line that is captured is immediately saved and also updates that Stock Item with a pending TRANSIT OUT indicator.

 

 

 

Slide 20

Slide notes: We can view the Stock status for any captured Stock Item.

 

 

 

Slide 21

Slide notes:

 

 

 

Slide 22

Slide notes:

 

 

 

Slide 23

Slide notes: And this will reveal the current Stock levels for the selected Stock Item in different Stores, plus we can also see the TRANSIT OUT and IN indicators, showing the current process of Stock being dispatched, but not yet received at the other end.

 

 

 

Slide 24

Slide notes:

 

 

 

Slide 25

Slide notes: The Stock Transfer record is saved when we have finished with all Items for this dispatch. However, the dispatch record may still be edited before it is processed as a Dispatch.

 

 

 

Slide 26

Slide notes:

 

 

 

Slide 27

Slide notes:

 

 

 

Slide 28

Slide notes:

 

 

 

Slide 29

Slide notes: As a matter of interest, we will now just check on the Stock Code enquiry how the impending dispatch is shown on the Stock status.

 

 

 

Slide 30

Slide notes:

 

 

 

Slide 31

Slide notes:

 

 

 

Slide 32

Slide notes: Stock Item 002 is being dispatched from Store 01, and a quantity of 10 is shown as TRANSIT OUT.

 

 

 

Slide 33

Slide notes:

 

 

 

Slide 34

Slide notes:

 

 

 

Slide 35

Slide notes:

 

 

 

Slide 36

Slide notes: Whereas Stock Item 002 is being dispatched to Store 02, and a quantity of 10 is shown as TRANSIT IN.

 

 

 

 

Slide 37

Slide notes: Before we conclude, we will briefly consider that there is also an option to automatically generate Stock Transfers.

 

 

 

Slide 38

Slide notes: This option is typically used in Retail environments where fast moving goods are replenished daily or at least regularly in various Outlets or Branches, from a main Warehouse.

 

 

 

Slide 39

Slide notes:

 

 

 

Slide 40

Slide notes: The date range always defaults to today, and although it can be changed, this is typically an end-of-day procedure, where the system looks at Stock Receipts in the Warehouse for today, then considers Stock Sales in the outlets over the last 2 weeks, and generates suggested Transfers to replenish fast moving Stock in the Outlets, based on what is available in the Warehouse, or has just been received in the Warehouse today. The help at this point, if accessed, will explain the default business rule logic for this process, and which is a proven concept. At the same time, if for our specific business we require different logic, then this business rule program can be changed by the IES Service Provider.

 

 

 

 

Slide 41

Slide notes: In this example, no Transfers have been generated, but we note that the Transfers that are generated by the system are actually "suggested" transfers, and they can still be evaluated and amended by the User before actually being processed.

 

 

 

Slide 42

Slide notes: In the other Tutorials for Transfer by Dispatch we look at the other steps in this process.

 

 

 

Slide 43

Slide notes: