1 Parameters for the creation of movements

To create movements from the frontend see user guide. To create movements from ERP, use the form Movements, in the Main Menu → Warehouse → Movements → Movements. The visualization of this form can be seen in the following image.

Initial blank display of a new movement.

As input parameters we have:

  • Type of movement
  • Movement warehouse
  • Origin store
  • Destination store
  • Movement note
  • Employee identifier
  • Status
  • Type (automatic/manual)
  • Date of movement
  • Reference

1.1 Movement type code

The type of movement must be a type that exists in the 'Types of movements' table. This table is in charge of storing all the new types of movements that are wanted to be generated, assuming that they must be associated with a MODE of movement (transport, recount, adjustment or inventory). To create a new type of movement, use the form 'Movement types', in the Main Menu → Warehouse → Movements → Movement types. This form can be seen in the following image:

Form to create new types of movements

As can be seen in the image, a new type of movement has six fields, of which four are required:

  • Type code (required): indicates the abbreviated code that will refer to the new type of movement.
  • Type name (required): indicates the full name of the new type.
  • Type mode (required): indicates which mode (transport, count, adjustment or inventory) the type belongs to.
  • Account: FILL IN THIS FIELD
  • Destination table: destination table of the type (if you want to outsource the movements).
  • Destination document: document in which the type of movement in the destination table will be outsourced.

The type of movement that is chosen will indicate the states through which the movement will be able to pass throughout its existence. See section Status for more details.

1.2 Movement warehouse, origin store and destination store

These three fields are related, and must be considered together. It is important to know that these three fields cannot be informed at the same time, but only two of three must be informed. To find out which fields to report, depending on the type of movement, see section Modes of movements, and its explanation in detail.

1.2.1 Examples

For a better understanding of these three fields, see the following examples.

Transportation from store A to store B

In this case, it is wished to carry out a transport from store A to store B. To do this, a type of movement will be chosen, transport, and store A will be reported as origin store, and destination store, the store B. The field movement warehouse must not be reported.

Transportation from store A to warehouse B

In this case, it is wished to carry out a transport from store A to warehouse B. To do this, a type of movement will be chosen, transport, and store A will be reported as origin store , and movement warehouse, the warehouse B. The field destination store must not be reported.

Recount or inventory

In this case, it is wished to perform a recount or inventory of store A. To do this, a movement type will be chosen, such as recount or inventory, and store A will be reported as origin store. The fields movement warehouse and destination store must not be reported.

1.3 Employee identifier

This number identifies the store employee who last made a change to the movement.

It is a 'no input' field so it will be modified automatically once the movement starts.

1.4 Estado

This field informs what state the movement is in. See section Status for further information. This field is a "no input" type and therefore cannot be reported, and its update throughout the movement is automatic (except to cancel or process a movement).

1.5 Type (automatic/manual)

This field informs on which platform the movement was created (ERP or frontend). The movements created from the ERP are automatic type movements, while the movements generated from the frontend are manual type.

1.6 Date of movement

This field informs of the day, hour and minute in which it is wished to carry out the movement.

1.7 Movement reference

In case it is necessary to refer to a movement from an external system, this field must be informed.

 

2 Parameters for creating movement lines

The movements, once created, contain lines with the products transported, adjusted, counted, etc. From the ERP, the table of lines is under the heading of the movement.

Initial display of the table of lines

The input parameters are:

  • Order (auto)
  • Location
  • EAN of the product
  • Product code
  • Product name
  • Quantity, quantity shipped and quantity confirmed
  • Note
  • Status

2.1 Order

The order of the line refers to the position of the product in the line table. It is an unreported field, which is completed automatically.

2.2 Location

This field indicates where the selected product is located in the warehouse, in case that there is more than one location with the same product in that warehouse. For example: 'Section 1A', 'Loc.1 ', etc. By default this field takes the value 0.

2.3 Product EAN, Product Code and Product Name

The field that must be informed is the EAN of the product, which must correspond to the EAN of an existing product in the catalog. The fields product name and product code will be automatically informed.

2.4 Quantity, quantity shipped and quantity confirmed

These three quantities are the quantities that must be filled throughout the movement, in their different states.