Stock > Assembly > Movements 

This screen is used to view all the assembling movements.

    Prerequisite

    SEEREFERTTO Refer to documentation Implementation

    Screen management

    A movement no. is selected and the system displays its characteristics:

    Header

    • AO data
    • AO line data
    • Movement data

    Tabs

    • General tab for the movement detail
    • Management for the traceability data relating to the movement

    Note: an assembling movement is not necessarily associated with an AO/AO line. In effect, for an assembling wave without incomplete container management ("Transfer incomplete" option set to no), more kits/components than necessary (or at least the same quantity) are transferred. In this way, only the necessary quantity is associated with the AO.

    Header

    Fields

    The following fields are present on this tab :

    AO

     

    • field REF

     

    • Status (field BMHSTA)

     

    Line

    • No / Ref (field BOMLIN)

     

    • field LINREF

     

    • Status (field BMLSTA)

     

    Movement

    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.

    Product code defined in the GEODE product table.

    • Description (field ITMDESAXX)

     

    • Status (field MVTSTA)

    Movement status.

    Close

     

    Tab General

    Fields

    The following fields are present on this tab :

    Quantities

    Container of the stock object.

    • Quantity (field ORIQTY)

    Stock object quantity.

    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.

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

    • Quantity (field CTRQTY)

    Quantity expressed in container type and code of the line.

    • Number of CU (field CUQ)

    Quantity of the stock object expressed in CU

    • No. of kit CUs (field CUQKIT)

    Number of necessary components to form a compound product.

    • field TYP2

     

    • Palletization plan (field PLAN)

     

    Dates

    • Input (field INPDAT)

    Date corresponding to the input to store of the stock object.

    • 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.

    Numerals/numbers

    • Lot no. (field LOT)

    Requested lot number.

    • Reservation no (field RSA)

    Requested reservation number.

    • Support no. (field SPT)

    Requested support number.

    Close

     

    Tab Controls

    Fields

    The following fields are present on this tab :

    Addressing

    Numerical sequence assigned automatically by the system upon wave launching.

    Transfer number.

    Identifier created by GEODE upon creation of the stock object.

    Code used to identify the store. This code is controlled in the store table.

    Physical storage address of the stock object.

    • Type (field SLOTYP)

    The location type determines whether the locations are of the reserve type (the allocation and vacating of the locations are carried out in dynamic mode) or of the picking type (the locations are assigned to a container for the Depositor/Product pair).

    Preparation

    Validation

    • 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.

    Transfer

    • Authorization (field TRFAUZ)

    If this box is checked, the operator will be entitled to validate transfers.

    Close

     

    Error messages

    The only error messages are the generic ones.

    Tables used

    SEEREFERTTO Refer to documentation Implementation