|
Movement Type Values Setup enables you to define the values used in the Movement Type. From the Action menu within Movement Types Setup, select MO Value. The form contains the following fields:
Movement Type Code and Short HeadingThese fields are automatically populated from the current Movement Type Setup, and cannot be amended. Value LabelThe value label to be applied, as defined in Value Labels Setup (VLS). Value Label Value TypeDepending on the Value Label selected, this field may automatically be completed, or you may have to select the type of the value label. See Introducing the Multi-Currency Functionality for more information regarding the currency options. 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 CodeThe formula to be used for the value, for example VAT, which has been set up using the Formula Designer (FUD) user tool. See Formula Designer Help for more information. 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. Note: 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 SequenceIf a Formula Code is specified, this field indicates the sequence in which the formula is calculated. For example, 1, 2, 3 etc. 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 Net. 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
- Goods Receipt Note
- Movement Order Entry
- Movement Order Entry and Goods Receipt Entry.
|
Movement Quantity Indicates whether or not the value holds the movement quantity. 2nd Goods Receipt Note Qty This field can be used to set up the ability to record the receipt of goods in two quantities. See Receiving Goods in Two Quantities for more information. 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 etc., only the purchase quantity can do this and remains the driving quantity. Base Date/Period for Currency Rate The date or period when this stage is reached, is used for the currency conversion rate. The Currency Codes Setup specifies whether a date or period is used. You can only select from the stages defined for the transaction type. Note: The Recalculation field in Movement Types Setup >> Action >> MO Stage must be checked in order for this recalculation to be carried out. See the section Defining Stages for the Movement Type earlier in this topic for information about this field. Options are:
- Order Entry - date or period when the order line was entered on the system is used.
- Order Confirmation - date or period when the order line was confirmed is used. If the line has not been confirmed, the Order Entry Date or Period is used.
- Picking - date or period when the order line was picked is used. If the values are recalculated at this stage, the date or period of the current pick line is used. If the order line was not completely picked in one go, the first date or period when the order line was picked is used. If the line has not been completely picked, the Order Entry Date or Period is used.
- Picking Confirmation - date or period when the order line was pick confirmed is used. If the values are recalculated at this stage, the date or period of the current pick line is used. If the order line was not completely pick confirmed in one go, the first date or period when the order line was pick confirmed is used. If the line has not been completely pick confirmed, the Picking Date or Period is used.
- Dispatch - date or period when the order line was dispatched is used. If the values are recalculated at this stage, the date or period of the current dispatch line is used. If the order line was not completely dispatched in one go, the first date or period when the order line was is used. If the line has not been completely dispatched, the Order Entry Date or Period is used.
- Dispatch Confirmation - date or period when the order line was dispatch confirmed is used. If the values are recalculated at this stage, the date or period of the current dispatch line is used. If the order line was not completely dispatch confirmed in one go, the first date or period when the order line was dispatch confirmed is used. If the line has not been completely dispatch confirmed, the Dispatch Date or Period is used.
- Goods Receipt Entry/Matching - date or period when the goods receipt note was entered or matched is used. If the values are being recalculated at this stage, the date or period of the current GRN line is used. If the order line was not completely GRN'd or matched in one go, the first date or period when the order line was GRN's or matched is used. If the line has not been completely received, the Order Entry Date or Period is used.
- GRN Inspection Date/Period - date or period when the goods were inspected is used. If the values are being recalculated at this stage, the date or period of the current GRN line is used. If the order line was not completely inspected in one go, the first date or period when the order line was inspected is used. If the line has not been completely received, the Dispatch Date or Period is used.
- Not Used - Order Entry Date or Period 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.
|
Note: If different rates are defined for different account ranges, the rate defined for the supplier's account is used. Split AnalysisIndicates whether or not the user can split a transaction line by a value or quantity. If this is not set lines cannot be split. Only one option can be selected, which is normally Quantity, to split the line for entry of multiple analysis codes. Holds Unit PriceIndicates whether or not the value holds the unit price. Running Total RequiredStage when a running total is required. This allows display during entry of, for example, the value of the order entered so far. These totals can be incorporated into formulae to calculate further values based on order totals. Options are:
Only registered users can write comments. Please login or register. |