Defining Values for the Movement Type

Movement Type Values Setup enables you to define the values used in the movement type.

  1. From the Action menu within Movement Types, select MO Value.
  2. Specify this information:
    Movement Transaction Type and Short Heading
    These fields display the current movement type, and cannot be amended.
    Value Label
    The value label to be applied, as defined in Value Labels (VLB).
    Value Label Value Type

    Depending on the value label selected, this field may automatically be completed, or you may have to select the type of the value label. Options are:

    • Without Units - a number without a unit of measure attached to it. For example, a percentage.
    • With Units - a number with a unit of measure attached to it. For example, a quantity.
    • Corresponds to Base Currency - a number that is the base currency.
    • Corresponds to Transaction Currency - a number that is the transaction currency.
    • Corresponds to Reporting or 2nd Base Currency - a number that is the reporting or 2nd base currency.
    Formula Code
    The formula to be used for the value, for example VAT, which has been set up using the Formula Designer user tool. If you do not enter a formula the value must be entered at run-time instead of being calculated. For example, a quantity does not normally use a formula.
    Uwaga: When setting up formulae, the number of decimal places used can be specified and this number is used when entering values into the value label. Care must be taken when selecting the correct number of decimal places to be used. Problems may occur if a formula returns more decimal places than the currency is expecting. If in doubt, use the default currency option when setting up the decimal places in the formula.
    Calculation Sequence

    If a formula code is specified, this field indicates the sequence in which the formula is calculated. For example, 1, 2, 3 and so on. If you close and re-enter the form, entries are reordered by this sequence. You can use parallel sequence numbers. That is, more than one value can have the same sequence number. The calculation sequence '0' is intended for values that are entered by the user and do not have a formula attached to them. '0' cannot be used if a formula is attached to the value.

    A value must be calculated before it can be used in a formula. If a value is referenced in a formula before it is calculated, an error results when a transaction is entered for this Movement Type. Therefore, its sequence number must be lower than the sequence number of the value with the formula that it uses. For example, you may have three values: Quantity, Unit Price and Net. Quantity is entered by the user; Unit Price has a formula to use a Price Book; and Net has the formula Quantity '*' multiply Unit Price. In this example, the sequence would be as follows:

    Value Label Calculation Sequence
    Quantity 0
    Unit Price 1
    Net 2
    Control Value Required

    Indicates whether the value has a control total created for it, and if so, the stage when it is applied. Options are:

    • No Total
    • Receipt Entry
    • Movement Order Entry
    • Movement Order Entry and Receipt Entry
    Movement Quantity
    Indicates whether or not the value holds the movement quantity.
    2nd Receipt Note Qty
    This field can be used to set up the ability to record the receipt of goods in two quantities. Only a value label of the type with units can have this flag set. This cannot be the same value label as that defined as the purchase quantity. This quantity cannot be used to update inventory and so on, only the purchase quantity can do this and remains the driving quantity.
    Base Date for Currency Rate

    The date when this stage is reached to be used for the currency conversion rate. You can only select from the stages defined for the transaction type.

    Uwaga: The Recalculation field in Movement Types > Action > MO Stage must be checked in order for this recalculation to be carried out.

    Options are:

    • Order Entry - date when the movement order line was entered on the system is used.
    • Order Confirmation - date when the movement order line was confirmed is used. If the line has not been confirmed, the order entry date is used.
    • Picking - date when the movement order line was picked is used. If the values are recalculated at this stage, the date of the current pick line is used. If the movement order line was not completely picked in one go, the first date when the order line was picked is used. If the line has not been completely picked, the order entry date is used.
    • Picking Confirmation - date when the movement order line was pick confirmed is used. If the values are recalculated at this stage, the date of the current pick line is used. If the movement order line was not completely pick confirmed in one go, the first date when the movement order line was pick confirmed is used. If the line has not been completely pick confirmed, the picking date is used.
    • Dispatch - date when the movement order line was dispatched is used. If the values are recalculated at this stage, the date of the current dispatch line is used. If the movement order line was not completely dispatched in one go, the first date when the movement order line was dispatched, is used. If the line has not been completely dispatched, the order entry date is used.
    • Dispatch Confirmation - date when the movement order line was dispatch confirmed is used. If the values are recalculated at this stage, the date of the current dispatch line is used. If the movement order line was not completely dispatch confirmed in one go, the first date when the movement order line was dispatch confirmed is used. If the line has not been completely dispatch confirmed, the dispatch date is used.
    • Receipt Entry/Matching - date when the receipt note was entered or matched is used. If the values are being recalculated at this stage, the date of the current receipt note line is used. If the line has not been completely received, the order entry date is used.
    • Receipt Transfer - date when the items were transferred from a receiving location to an inventory location is used. If the values are being recalculated at this stage, the date of the current receipt note line is used. If the line has not been completely received, the dispatch date is used.
    • Not Used - Order entry date is used.
    Rate Required

    Indicates whether the conversion rate should be entered which overrides the rate looked up on the currency tables. Options are:

    • No - never entered.
    • Yes - must be entered.
    • Optional - may be entered. The rate defined in the currency tables is displayed but can be overridden.
    Uwaga: If different rates are defined for different account ranges, the rate defined for the supplier's account is used.
    Split Analysis
    Indicates whether or not the user can split a transaction line by this value as well as by the quantity or not.

    This option can only be selected for one value, which is normally the net or gross value. If this option is not set, then the lines can only be split by quantity.

    Holds Unit Price
    Indicates whether or not the value holds the unit price.
    Uwaga: If unit conversions are carried out, the value in this field is converted. For example, if a case costs GBP 10, and can be bought or sold in barrels where there are 15 cases in a barrel, then a transaction for one barrel has a unit price of GBP 150.
    Running Total Required
    Stage when a running total is required. This allows display during entry of, for example, the value of the movement order entered so far. These totals can be incorporated into formulae to calculate further values based on movement order totals. Options are:
    • No Total
    • Receipt Entry
    • Movement Order Entry
    • Movement Order and Receipt Entry
  3. Save your changes.