Receipts > Expected inputs 

From this screen, it is possible to:

Create/modify the header of an expected input and its lines.

View the header of an expected input and its associated lines.

Close the header/line of an expected input

View and print the load of an active, i.e. non-closed, EI.

The expected input can also be created via an interface.

    Prerequisite

    SEEREFERTTO Refer to documentation Implementation

    Screen management

    An expected input is created using 3 tabs for the header and 2 tabs for the lines.

    Header

    Presentation

     

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

    Reference.EI reference. Optional entry.
    If this field is left blank, the system automatically assigns the EI number. This field can be modified.
    If this field is entered, the system imposes the uniqueness of the field depending on the input configuration setup.

    Status.This field specifies the status code of the EI header.

    Date.Date of creation of the EI. When creating an EI, the system date is proposed by default. This field is mandatory. The EI date can be modified by the user.

    Close

     

    Fields

    The following fields are present on this tab :

    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 an Expected Input.

    • Status (field EIHSTA)

     

    • Reference (field REF)

    Document reference.

    • Date (field DAT)

    Creation date of the document (expected input, input, DO, etc.).

    Close

     

    Tab General

    Presentation

     

    Movement code.The movement code is used to qualify an expected input (Supplier input, Factory input, Customer Return,...). The possible values are those of the Table of the movement codes authorized on input.

    Receipt method. Specifies the management rules in order to process the EI: this field is set up in the table of the receipt methods.

    Transmitted by L3. Specifies if the expected input has been created by the expected input interface.

    Previsional receipt

    Date and time. Planned receipt date and time of the expected input. When creating an Expected Input, the system date and time are proposed by default. This field is mandatory. The planned receipt date and time can be modified by the user.

    Carrier.Code of the carrier responsible for the goods to be received. Optional entry, but in case of entry, the system checks that the code exists in the table of the Carriers.

    Transport method. Optional entry, but in case of entry, the system checks that the code exists in the table of the Transport methods.

    Transport reference. Carrier reference

    Last receipt

    Number : specifies the last receipt no.

    Status: specifies the receipt status.

    Date and time. of receipt creation

    Carrier, transport method and carrier reference: values entered upon receipt

    Close

     

    Fields

    The following fields are present on this tab :

    Management

    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.

    Code of the receipt mode. A number of management rules relating to the expected input is associated with this code.

    • QC management (field QLYFLG)

    Used to trigger the quality control for the Expected Input: if the parameter is set to yes, the quality control processing will be triggered upon EI receipt validation.

    NB: When the "Submitted to quality control" flag of the EI supplier is activated, the "Submitted to control" flag of the EI is automatically set to yes.

    • Transmitted by L3 (field TRM)

     

    • Order number (field ORDNUM)

     

    • Order reference (field ORDREF)

     

    Forecasted receipt

    • Date (field APTDAT)

    Planned receipt date for the expected input (compulsory). Upon

    creation of an Expected Input, the system date is proposed

    by default. It can be modified by the user.

    • Time (field APTTIM)

    Planned receipt time for the expected input (compulsory). Upon

    creation of an Expected Input, the system time is proposed

    by default. It can be modified by the user.

    Code identifying the carrier. This code must be defined in the carrier table.

    • field CRRNAM

    Carrier trade name.

    Usually, the transport mode corresponds to the notions of messaging, freight, express,... The transport mode is checked against the transport modes table.

     

    • Reference (field CRRREF)

    Carrier reference.

    Last receipt

     

    • Status (field RCHSTA2)

     

    • Date (field DAT2)

     

    • Time (field TIM2)

     

     

    • field CRRNAM2

     

    • Carriage reference (field CRRREF2)

     

     

    Close

     

    Tab Supplier

    Presentation

    This tab specifies the information previously entered in the table of the Suppliers. After the supplier code has been selected, their company name, address, etc. are displayed. The information modified in this tab is not picked up in the supplier table.

    Close

     

    Fields

    The following fields are present on this tab :

    Code of the supplier who must be defined in the supplier table.

    Code making it possible to identify the country. This code is controlled in the country table. The name corresponding to the country code is then displayed automatically. If the country code is not entered by the user, then the country name can be entered freely.

    • field DVRNCY

    Country name. If the country code is entered, then this field is automatically entered on the basis of the country table. If the country code is not entered, then this field can be entered freely by the user.

    • field DVRNAM

    Supplier's company name (by default the company name is defined for the supplier in the supplier table).

    • field DVRADD

    Supplier's address (by default the address is defined for the supplier in the supplier table).

    • Postal code (field DVRPOS)

    Postal code where the entry format is defined in the Country table.
    The postal code is used to determine the city/town. When the postal code is changed the city/town corresponding to the new code is automatically displayed.
    Particular cases:

    • For ANDORRA, indicate 99130
    • For MONACO, indicate 99138
    • For the other overseas countries, indicate the postal code of the country or 99999 if not known.
    • City (field DVRCTY)

    Name of the town/city. The city automatically proposed is the one associated with the postal code previously indicated.
    It is also possible to manually enter the city.

    * If the city is already defined, the associated postal code is automatically displayed.

    * if it does not exist, a warning message will appear and proceeding with the entry is authorized.

    • Region (county, state, ..) (field DVRSAT)

    This field includes the geographical subdivision which is part of the postal address definition.
    For instance, it can be the department for France or the state for the United States. The subdivision title and the potential control on its entry are defined in the Country setup.
    If it is controlled, this code depends on the corresponding geographical subdivision.

    This subdivision is automatically fed after the postal code and town/city have been entered, based on the Postal codes setup.

    • Telephone (field DVRTEL)

    Telephone number with en entry format dependent on the country.

    • Fax (field DVRFAX)

    Fax number where the entry format is identical to that of the telephone and is dependent on the country.

    Close

     

    Tab Lines

    Presentation

    This tab displays in the form of a grid all the characteristics of the expected input lines previously entered (reference, quantity put-away, FIFI, etc.).

    To directly access the expected input lines, a simple click on the

     

    Close

     

    Fields

    The following fields are present on this tab :

    Grid

    Product code defined in the GEODE product table.

    • Reference (field LINREF)

    Reference of the document line. Can be used to establish a link between L2 and L3 during interfaces; in that case, this field is automatically fed.

    • STK (field UOMSYM)

     

    • Expected (field EXPCSUQTY)

    CU quantity planned for receipt for the expected input line.

    Note: This field cannot be modified from the moment that a receipt has been saved onthe line.

    • Balance (field BLCCSUQTY)

    CU quantity remaining to be received for the expected input line.

    Note: this field can be modified from the moment that a receipt has been saved on the line.

    • Received (field RCPCSUQTY)

    CU quantity received for the input line.

    • Disputed (field DSCCSUQTY)

    CU quantity received as dispute for the expected input line. This quantity is calculated by the system as the sum of the blocked received quantities with acode indicating a dispute (inputs to stock or not).

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

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

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

    • Date (field DAT)

    Receipt date of the expected input. By default, the system retrieves the date and time of the header of the expected input. This field is mandatory but it can be modified.

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

    • Return (field CLTRTN)

    Used to specify if it is a customer return. This parameter is used witin the framework of the serial number management. This update is going to generate a specific processing upon entry of the serial numbers.

    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.

    Type and code of the input container of the line. By default, it is the product default input container.

    • Multi (field MLTITM)

    Available in a later version.

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

    • Status (field EILSTA)

    The field specifies the status code of the expected input line. This flag can take the following values: 1 = Not received, 2 = Partial Receipt, 8= Received/closed.

    Close

     

    Other conditions

    The modification of an expected input is possible from the moment that it has the status 1- Not Received or 2-Partial Receipt.

    The line can no longer be modified as soon as it has been partly received.
    To modify a line:
    - if it is not received, all the fields on the line can be modified.

    - if it is partly received, only the remaining quantity can be modified.

    - if it is fully received, no field can be modified.

    Specific Buttons

    Used to close a header or a line. Closure is an operation that consists in switching to status 8 of the header or lines; in effect, the deletion is not authorized for entities that can be transmitted via an interface.

     

    The creation/modification screens of an expected input line are accessible via this button.

    The expected input line is created via a function comprised of 3 screens.

    Header

    The elements specified here are those that come from the header of the expected input previously created or selected. The following data are mentioned here:

    Number, Reference, Status and Date.

    Line

    Number Number assigned by the system. Within the frame of an inquiry, the number of the line to be queried needs only to be entered and its content is displayed automatically.

    Status. The field specifies the status code of the input line.

    Item. Code of the item to be received for the expected input line

    Title.Description of the item code.

    General

    CU quantities

    Expected.Expected quantity of the entry line, expressed in the smallest unit, in CU.

    Balance: if receipts already took place, this quantity mentions the balance to be received for the line (in CU).

    Received: mentions the quantity (CU) received for the line

    Disputes: indicates the line quantity declared as being disputed upon EI declaration.

    Reference. Reference of the Expected Entry line. Optional entry. Can be used to establish a link between L2 and L3 during interfaces; in that case, this field is automatically fed.

    Multi-items.Available in a later version.

    Customer return(Available from version G2). Used to specify if it is a customer return. Used within the framework of the serial number management, this update will generate a specific process upon entry of serial numbers.

    Numbers:

    Lot no.. Lot number assigned to each stock object created from this EI line.

    Reservation no..Reservation number assigned to each stock object created from this EI line.

    Support no.(Available from version G2). Support number assigned to each stock object created from the EI line.

    Dates

    Input. Creation date of the EI. The system uses by default the date and time of the Input Header. This field is mandatory but it can be modified.

    Detention. Detention date.

    SBD.Use-by date (SBD).

    FIFO. The FIFO date is automatically calculated on the basis of the "FIFO selection" of an item specified in its Item Record. This date is mandatory.

    The FIFO date is automatically recalculated if one of the master dates of the item (Input date, Production Date or one of the three calculated dates) is modified.

    WARNING: Therefore the "FIFO date" field must not be modified directly, but rather one of the "master date" fields on which the calculation of the item FIFO date depends.

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

    SbD. Sale-by Date (SbD).

    BBD.Best Before Date (BBD).

    Mvt code. By default, the system specifies in this field the Movement code of the EI Header, but the latter can be modified.

    Origin.The origin enables items to be classified on the basis of a criterion chosen by the user. This is a characteristic of the stock object.

    Input cnt. Type and code of the input container of the line. This is the default input container of the item.

    Stock nature. Stock nature assigned to each stock object created from this EI line.  

    Store. Used to impose an input store to the Input line. Optional entry but if there is an entry, the system checks that the store exists in the Store Table.

    Exclusive store. If the box is checked, the system exclusively addresses inside the requested store. If the search in this store fails, the system does not try to make the link to other stores.

    List

    This screen presents a synthesis of each line.

    Menu Bar

    Functions/Load analysis

    Used to launch the load analysis for the selected EI.

    The load analysis function is dependent on the activity code LA0 and the status of the EI that must be lower than 8 (non-closed EI).

    The system considers the load that remains to be received for the EI, in other words, the sum of the loads specific to:
    - the EI header
    - each EI line not or partly received, and only considering the quantities that remain to be received.

    Further to a load analysis request:
    • a new analysis is created with the following characteristics:
    - Flag to be kept="no"
    - Template (for information):
      ▪ the template associated with the triplet (function, current site, current depositor) for a single-depositor function
      ▪ By default, or for a multi-depositor function, the template associated with the triplet (function, current site, "blank" depositor.
      ▪ By default, the template associated with the triplet (function, "blank" site, "blank" depositor)
      ▪ By default, the template is left blank.
    • The calculation is launched for the analysis
    • The operator accesses the load display screens from which they can also access the information related to the analysis (description and flag "To be kept") and request the printing of the analysis results.

    Functions/Calculation of containers

    Functions/Consumable movements

      

    Used to declare 1 or n input-to-stock movements of consumables within the framework of the EI.

    This entry can take place at any moment, irrespective of the EI status.

    Various data must be entered to complete a consumable input movement:

      • The consumable code: specified in the product record of the consumables
      • The movement code: must belong to the group of the 'CONSUMABLE ' processes and be of 'INPUT' type
      • The quantity:quantity of the input movement

    Since the input movement of the consumable is declared from a known entity, the carrier, transport method, supplier and supplier title information are, if need be, entered with that of the entity.

    For an input movement, such information as customer, customer title, the type of entity and the number of said entity is not accessible.

    Depending on the setup, it is requested to enter an operator code to validate the input movement. The stock is incremented upon validation.

    The movement can no longer be modified after validation. Therefore it is not updated when updates are carried out on the entity with which this movement is associated.

    It is possible to generate 3 reports:

      • In File/Print/Record:
          • Stock of the consumables sorted by consumable or by quantity
          • Screen print for the selected record
      • In File/Print/List:
          • Movements of the consumables sorted by consumable or by date

    Error messages

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

     

    Movement code field error (line or header), mandatory field

    The movement code is a mandatory entry.

    Movement code field error (line or header), record does not exist

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

    Receipt mode field error, mandatory field

    The receipt mode MUST be entered.

    Carrier field error, record does not exist.

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

    Transport method error, record does not exist.

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

    Country field error, record does not exist.

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

    Code field error, record does not exist.

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

    X3 application error, no line entered.

    A line must necessarily be created to update the header of an expected input.

    X3 application error, modification impossible

    The expected input is being received and therefore cannot be modified.

    Item field error, mandatory field

    It is mandatory for the product to be entered.

    Item field error, record does not exist.

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

    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.

    The error messages associated with the consumable movement declaration are the following:

    "Consumable" field error. Mandatory field

    The consumable code is a mandatory entry.

    "Movement code" field error Mandatory field

    The movement code is a mandatory entry.

    "Movement code" field error Movement code of non-consumable type.

    The entered movement code must belong to the group of the 'CONSUMABLE' processes.

    "Movement code" field error. Movement code of output type.

    The entered movement code must necessarily be of 'INPUT' type.

    "Quantity" field error. Mandatory field

    The quantity of the input movement must necessarily be entered.

    Application error. The depositor must be entered for this origin.

    When an input movement is associated with an expected input or a direct input, the depositor must necessarily be entered.

    "Mvt origin no." field error. Reference of the origin not found.

    The number of the Warehousing entity must necessarily be entered and exist for the site.

    "Consumable" field error: Consumbale blocked upon input.

    The consumable must necessarily be authorized for input for an input movement to be completed.

    Tables used

    SEEREFERTTO Refer to documentation Implementation