Defining Stages for the Movement Type

You can set up specific information for the stages to be used in a movement type. For example, the sequence the stages are processed in, and the document format to be used.

  1. From the Action menu within Movement Types, select MO Stage.
  2. Specify this information:
    Movement Transaction Type and Short Heading
    These fields are automatically populated from the current movement type and cannot be amended.
    Stage
    The required movement stage.
    Sequence
    The movement stage which must have been completed before this stage can be allowed. You can set up parallel stages by defining the same stage twice. However, order confirmation must follow order entry, but it does not have to follow immediately.
    Document Format Code
    The document format to be applied to this stage. For example, the document format that has been set up for a picking list. You can attach a document format to any or all of the stages.
    Transaction Ldg Iface Defn Code
    If required, this field contains the ledger interface to be applied to this movement stage. If this is set up the transaction is automatically posted to the ledger on confirming the stage. You can attach a ledger interface code to any or all of the stages.
    Inventory Ldg Iface Defn Code
    For each transaction stage, you can specify one inventory ledger interface. On a stage that creates both an inventory issue and an inventory receipt, this interface will fire twice, once for the issue and again for the receipt.
    All inventory ledger interfaces must have their credits and debits specified as if they are for a receipt, that is, with debit the inventory accounts and credit the contra accounts. When a ledger interface is processed for an inventory issue, its credits and debits are reversed. For example, on a movement issue transaction, the ledger interface would be set up as follows:
    • Inventory Account - Debit Latest Actual Line Cost
    • Cost of Sale Account - Credit Latest Actual Line Cost.
    Then when a sales order line is issued and the cost is 100.00, the postings would be:
    • Inventory 100.00 credit
    • Cost of Sale 100.00 debit.
    If inventory is to be updated at the stage, and a creation of an issue and/or receipt is specified, you must supply an inventory cost ledger interface definition code in this field.
    Uwaga: Either a Ledger Interface Code (also referred to as a Transactional Ledger Interface Definition) or an Inventory Ledger Interface Definition Code, or both, must be entered against any stage where an issue and/or receipt is created. Either or both can be entered at a stage where a transfer is created, but neither are mandatory.
    Inventory Ledger Interface Definitions must be used in the following circumstances:
    • Actual costing users who need to see cost changes ripple through receipts and issues.
    • Standard costing users if the Inventory Revaluation module is used to revalue current period transactions.
    If inventory is to be updated at the stage, and a movement type is specified, you should supply an Inventory Ledger Interface Definition Code in this field.
    Posting Date Adjustment
    This allows you to adjust the default posting date set up in the Posting Date Source field, by entering a positive or negative figure. For example, if this is set to +10, the posting date is calculated as ten days ahead of the source date.
    Posting Period Adjustment
    This allows you to adjust the default posting period set up in the Posting Period Source field, by entering a positive or negative figure. For example, if this is set to +2, the posting period is calculated as two periods ahead of the source period.
    Direct Print
    Indicates whether or not a document is directly printed on release of this stage. Alternatively, transactions can be selected for printing by using the Control Desk functionality.
    Hold after Completion
    Indicates whether or not the transaction is held after completion of this stage.
    Default Form
    Default form to be used for this stage. This is used when transactions are selected by a Control Desk and passed to an entry function.
    Posting Date Source and Posting Period Source
    The date and period in the movement process to be used for postings. The options are:
    • Order Date/Period - the date/period of the movement order.
    • Order Entry Date/Period- when the movement order was entered on the system, which may be different to the date/period of the movement order.
    • Order Confirmation/Issue Date/Period - when the movement order was confirmed.
    • Current Date/Period - the date/period of the current user login.
    • RN Receipt Date/Period - the date on the receipt note.
    • RN Entry Date/Period - when the receipt note was entered on the system.
    • RN Transfer - when the items received were transferred from a receiving location to an inventory location.
    • Dispatch Confirmation Date/Period - when the dispatch of the items was confirmed.
    • Dispatch Entry Date/Period - when the dispatch of the items was entered on the system.
    • Dispatch Date/Period - the date entered during the dispatch process.
    • Picking Confirmation Date/Period - the date entered during the picking confirmation process.
    • Picking Entry Date/Period - when the item picking was entered on the system.
    • Picking Date/Period - the date entered during the picking process.
    Unit for Date Calculation
    Unit of time for the posting date calculation. Options are: Days, Months, Years, or Not Applicable.
    Optional
    Indicates whether or not this stage is optional. You cannot attach a Ledger Interface Code to an optional stage. Receipt Note Entry/Matching cannot be set up as an optional stage.
    Recalculation
    Specifies whether or not transaction values are recalculated at this stage. Recalculation is normally required if changes have been made to currency rates or value books since the initial entry stage.
    Create Actual Receipt/Issue

    Indicates whether or not a receipt or issue should be created at this stage. Options are:

    • No Creation

      No inventory updates are performed.

    • Create Receipt

      Only one stage can specify a receipt and no issues are allowed. If a receipt is specified for a stage that is not the entry stage, an anticipated receipt is created when the transaction is entered. This anticipated receipt is available for allocation if Examine Projected Free Inventory is set in the Inventory Business Setup.

    • Create Issue

      Only one stage can specify an issue and no receipts are allowed. If an issue is specified for a stage that is not the entry stage, an anticipated issue is created when the transaction is entered. Receipts can then be allocated to this anticipated issue.

    • Create Receipt & Issue

      That is, a transfer. An issue can be specified on only one stage and a receipt can be specified on only one stage. If the movement type generates both a receipt and an issue, an issue can be specified on only one stage and a receipt can be specified on only one stage. The receipt and issue can be specified either on different stages or both on the same stage. If they are specified on different stages, the issue must be specified on a stage that precedes the stage that specifies the receipt.

      Uwaga: Using these settings to create both a receipt and an issue on more than one stage for a movement type can cause corruption of the inventory data and should not be done.
      Uwaga: It is not recommended that inventory is updated at the order entry stage. It is recommended that the movement type is associated with stages after order entry, such as order acknowledgment, picking, dispatch and so on. By having inventory updates at the order entry stage, various parts of the functionality are not allowed to perform, such as costing and allocations, and any data entered cannot be amended.
    Reversals Present
    This shows whether or not ledger interface reversals have been set up for the stage.
  3. Save your changes.