Receipts > Movements 

From this screen, it is possible to:

  • Create/modify/delete an input movement.
  • View an input movement
  • Address an input movement

An input movement is always associated with a single input line.

Input movements are generally created by the system upon creating an input line and upon addressing on input.

A non addressed input movement will give rise to a stock object: it must correspond to the received physical object and can be manually modified.

Accessing the input movements is generally done via the direct input function and the "Movements" button.

Input movements contain a status; they can be modified at status 1- Pending addressing.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The function is divided into 3 screens. The creation, deletion and modification are accessible depending on the direct input line context.

Header

Presentation

The direct input and the line information is displayed.

In modification mode, only the line number and movement number fields can be entered and make it possible to position in the desired line by entering one of the fields.

In creation mode, by entering the line number, a movement is added to the entered line number.

Close

 

Fields

The following fields are present on this tab :

Input

Numerical sequence automatically assigned by the system upon validation of the Input header. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a Direct Input.

  • field REF

 

  • Status (field INHSTA)

 

Line

  • No / Ref (field INPLIN)

Numerical sequence automatically assigned to the line by the system.

  • field LINREF

 

  • Status (field INLSTA)

 

Product code defined in the GEODE product table.

  • Description (field ITMDESAXX)

 

Movement

  • Number (field MVTNUM)

Numerical sequence automatically assigned by the system to the movement. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a movement.

  • Status (field INMSTA)

 

Close

 

Tab General

Presentation

This tab is used to modify or to enter the information associated with the movement.

Close

 

Fields

The following fields are present on this tab :

Quantities

The term Container encompasses the type and code of the container.

  • Quantity (field CTRQTY)

Quantity expressed in container type and code of the line.

The homogeneous container of a stock object is defined as the first container of a level other than level 1 (the pallet) whose CU stock quantity is a multiple.

  • Quantity (field HMGQTY)

Quantity expressed in the homogeneous container.

  • Number of CU (field CSUQTY)

 

  • STK quantity (field STUQTY)

 

  • field UOMSYM1

 

  • No. of line CUs (field INLCSUQTY)

 

  • SU qty line (field INLSTUQTY)

 

  • field UOMSYM2

 

  • field PLAN

 

Dates

  • Input (field INMDAT)

Input creation date. By default, the system retrieves the date and time of the Input Header.

  • Manufacturing (field MND)

Production date corresponding to the end of the item production cycle.

  • Detention (field RTD)

Detention date. This date corresponds to the instant before which

the stock object is unavailable for an output movement.

(for instance, quarantine).

  • SBD (field SLD)

Sale-by Date (SbD). The SbD is generally used

as FIFO date for food products.

  • UBD (field USD)

Best Before Date (BBD). This date is also called

Optimum Use By Date. It is usually mentioned on

the packaging of food or pharmaceutical products.

  • SbD (field SND)

Use-by date (SBD). The UBD makes it possible to limit the circulation of a product in time:

- for instance, within the framework of a commercial operation (discount),

- or because of its expiry date.

  • FIFO (field FIFDAT)

The FIFO date can determine the stock removal order of the products (depending on the setup) when an order picking is launched. This date is used to ensure that some operations like merging are possible.

Characteristics

The movement code is used to make the distinction between movements of the same type.
It is required when creating:

  • An expected input
  • A supplier input
  • A factory input
  • A customer return
  • A DO
  • An adjustment
  • A transfer
  • A consumable input/output

The movement code is checked against the movement code table.

L’The origin’ enables items to be classified on the basis of a criterion chosen by the user.

It is generally used to define or further determine the origin (geographical or other) of the products managed by the system.

It is used to manage the quality-related differences at stock object level: expiry, reconditioning, etc.

Used to impose an input store to the Input line (optional). The store is checked in the Store table.

  • Exclusive store (field STOXCL)

The system exclusively addresses the goods to the requested store. If the search in this store fails, the system does not try to make the link to other stores.

Numerals/numbers

  • Lot no. (field LOT)

Lot number assigned to each stock object created from this entity.

  • Reservation no (field RSA)

Reservation number assigned to each stock object created from this entity.

  • Support no. (field SPT)

Support number assigned to each stock object created from this entity.

Close

 

Tab Checks

Presentation

This screen shows a summary of each movement that is updated by the system as the movement evolves.

Close

 

Fields

The following fields are present on this tab :

Addressing

Store of the input movement further to an addressing or putaway operation.

Address of the input movement further to an addressing or putaway operation.

  • field SLOTYP

 

Identifier created by GEODE upon creation of the stock object.

  • Container link no (field CTRLIKNUM)

In case of merging without accrual with another object, the number of the linked object is displayed.

  • Movement type (field MVTTYP)

Specifies the movement type nature: Normal (the input movement gives rise to a stock object), merging (the input movement is merged with an object that exists in the database).

Storage type

Storage list number to which the input movement is attached if it is dependent on a SL.

  • SL line (field STLLIN)

Line number of the storage list to which the input movement is attached if it is dependent on a SL.

  • Date (field VLDDAT2)

Movement validation date.

  • Time (field VLDTIM2)

Movement validation time.

  • Operator (field VLDOPENAM)

Description of the operator code having validated the movement, if the configuration set-up requires it.

Close

 

Other conditions

The "Delete" button is accessible when the movement is not addressed.
A movement deletion has consequences on the quantity of the input line.
There must be at least one input movement per input line to delete a movement. To completely delete the input movements of a line, the input line must be closed.

Menu Bar

Functions / Addressing

A shortcut makes it possible to automatically address a direct input movement. The addressing launched here does not automatically generates a putaway list.

Functions/Simulation

This shortcut makes it possible to simulate a direct input movement automatic addressing.

Functions / Regeneration

When an input line is created, the entered quantity cannot be modified any more. input movements are created, either from:

  • receipt movements entered by the user on the administrative receipt, if any.
  • or from the entered quantity, the palletization program and the input mode of the product.

These movements can then be modified as long as they have not been addressed.

For putaway list setup or cancellation update reasons, it is possible to "re-create" the movements with this function.

For instance: after addressing, the movements have been split, then addressed. If the user cancels the Warehousing addressing, the movements simply are de-addressed and the addressing splitting is not modified. To re-generate the movements as they were upon creating the input line, it is necessary to select Function/Re-generation.

Warning: If there is at least one input movement with a status other than "Not addressed" for the Direct Inuput (DI), the Regeneration function will not deal with this DI.

Functions / Serial numbers

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

"no./Ref" field error, Input X: Record does not exist

An attempt has been made to enter a non-existent direct input number.

"no./Ref" field error, Input lines X: Record does not exist

An attempt has been made to enter a non-existent direct input line number.

"no./Ref" field error, Indicate the input line where the movement is to be created

The direct input and line numbers MUST be entered.

Container field error, mandatory field

The quantity and the container code MUST be entered.

Product containers: Z, Record does not exist

The entered container is not defined in the palletization program of the product.

Homogeneous container field error, mandatory field

The quantity and the homogeneous container code MUST be entered.

Movement code field error, mandatory field

The movement code is a mandatory entry.

Movement code field error, Record does not exist.

An attempt has been made to enter a non-existent movement code.

Origin field error, record does not exist.

An attempt has been made to enter a non-existent origin.

Stock nature field error, record does not exist.

An attempt has been made to enter a non-existent stock nature.

Store field error, record does not exist.

An attempt has been made to enter a non-existent store.

Lot no. field error, mandatory field

After setup, the lot no. MUST be entered.

Tables used

SEEREFERTTO Refer to documentation Implementation