In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Release Notes for Version 2.3c and SSD 2.3c
    Advanced Inventory Management Version: 2.3c and SSD 2.3c
    MFG/PRO Compatibility for 2.3c: eB, initial release through Service Pack 5
    eB2, initial release through Service Pack 5,
    Service Pack 7 through Service Pack 9
    MFG/PRO Compatibility for SSD 2.3c: eB2.1, Service Pack 2 and Service Pack 3
    Supported languages: US English, Castilian Spanish, Dutch, French, German, Italian, Polish, and Portuguese
    Installation Guide: Advanced Inventory Management item 78-0628C
    User Guide: Advanced Inventory Management item 78-0591B
    Installation
    Installation Guide: Advanced Inventory Management, item 78-0628C, describes how to perform a new installation of AIM2.3c or AIM 2.3c SSD or upgrade an existing 2.0, 2.1b, 2.2a, 2.3a, or 2.3b implementation. A database conversion is required by changes introduced in 2.3a.
    If you are implementing AIM 2.3c SSD, review the information in AIM 2.3c SSD Implementation.
    New Features Overview
    1
    A new Wave/Batch Picking Utility Menu (80.15.22) provides two new programs:
    Batch Picking Crash Recovery (80.15.22.15) described on here.
    Batch Picking Tasks Report (80.15.22.10) described on here.
    2
    You can now pick repetitive items from negative inventory in dedicated locations during a backflush. See Backflushing Items From Dedicated Locations.
    3
    You can now reassign tasks that are hard assigned to a user. See Reassigning Hard Assigned Tasks.
    4
    You can now specify that warehouse staff pick to a kit when batch picking. See Batch Picking to a Kit.
    5
    You can now move items from one box to another to optimize storage based on volume. See Moving Items to Another Box.
    6
    You can now skip tasks. See Skipping Tasks.
    7
    Sales order header comments now display in the radio frequency (RF) device even when RF users select a pre-shipper. If the pre-shipper has multiple orders, the RF displays comments for the first order on the pre-shipper.
    Note: Sales order header comments display only if Print Packing List Comments is set to Yes in Sales Order Maintenance (7.1.1).
    8
    Warehouse staff can pick for a sales order without creating an MFG/PRO pre-shipper in Sales Order Packing List (7.9.13).
    9
    You can now merge the following order types in the same box when batch picking:
    Distribution orders, work orders, and sales orders
    Sales orders on different pre-shippers
    Distribution orders with different destination sites
    10
    The Detail Picking Menu (80.15) is now the Detail/Batch Picking Menu.
    Batch Picking Crash Recovery
    Previously, when the system crashed, all tasks selected by the user in batch picking were either active or open; however, because the tasks were hard assigned to the user, only the person assigned the tasks could view them. Since the tasks were not viewable, you could not assign them to anyone else. Moreover, the system modified tasks performed so that stock already picked was in the user location (cart). The only way to correct this situation was to use a tedious manual process involving Standard Transaction Maintenance (25.13.1), Pre-Shipper/Shipper Workbench (7.9.2), and AIM movement confirmation programs in the AIM Process Menu (80.8).
    Two new batch-picking crash recovery features let you recover, confirm, and view picking tasks that took place when the system crashed or connections were lost:
    Crash Recovery Utility (80.15.22.15).
    Crash recovery features built into batch-picking functionality; see Built-In Recovery.
    Crash Recovery Utility
    You can use a new Crash Recovery Utility to confirm tasks completed by warehouse staff and information processed by the system when a system failure occurs. The utility:
    Lets you view unprocessed tasks for a specific user, site, and warehouse combination or for all users for a warehouse/site combination.
    Lets you confirm tasks completed before the system failure.
    Lets you drop off all or some completed boxes at shipping lanes or a staging area.
    Makes selected, but not picked, tasks available to the user again; see Task Availability.
    To use the utility to confirm tasks and drop off boxes, use the following procedure:
    1
    Enter the user ID of the warehouse staff whose tasks you want to confirm. Optionally, leave blank to show all unconfirmed tasks for the site and warehouse you specify.
    2
    Enter a site and warehouse.
    The utility displays picked, but unconfirmed tasks that were interrupted because the system went offline. The system displays the task number, user ID, destination location, packing container, and the quantity picked/to pick in a read-only frame. See Crash Recovery Utility (80.15.22.15).
    3
    When tasks display, press F1.
    If all tasks are for the same destination, the system displays the Drop All prompt.
    If tasks are for different locations, the system prompts you to enter a location. Go to Step 5.
    Note: The drop-all functionality is the same as that for the RF device. See Dropping All or Some Boxes.
    4
    At the Drop All prompt, specify whether staff drop some boxes to another location or drop all boxes to the same location:
    No: Staff drop some boxes one by one to another location. Go to Step 5.
    Yes: Staff drop all boxes to the same location. Go to Step 6.
    5
    Enter the new location in the To Loc field.
    Note: The container and order that display are read-only fields. The system prompts once for the container and order that display, even when there are multiple tasks for the same box. See Crash Recovery Utility (80.15.22.15), Location Change Prompt.
    6
    Confirm the task completion by specifying Yes at the OK to Confirm prompt.
    The system displays the number of confirmed tasks.
    Crash Recovery Utility (80.15.22.15)
    Start User ID
    Enter the ID for the user whose picking tasks you want to confirm or leave blank to display all unprocessed tasks for users of a site/warehouse combination.
    Site
    Enter the site for the tasks you want to see.
    Warehouse
    Enter the warehouse for the tasks you want to see.
    Drop All
    Specify whether staff drop some boxes to another location or drop all boxes to the same location.
    No: Staff drop some boxes one by one to another location.
    Yes: Staff drop all boxes to the same location.
    Container
    The container ID for the box you want warehouse staff to drop off. You cannot edit this field.
    Order
    The order number for the box. You cannot edit this field.
    To Loc
    Enter the location where warehouse staff drop off boxes.
    OK to Confirm
    Specify whether to confirm the batch-picking tasks that display.
    No: Do not confirm the tasks. The system displays 0 (zero) tasks confirmed.
    Yes: Confirm the tasks. The system displays the number of tasks confirmed and a list of confirmed tasks.
    Crash Recovery Utility (80.15.22.15), Location Change Prompt
    Task Availability
    There may be other picking tasks that warehouse staff selected but failed to process because of a system failure. The recovery utility ensures these tasks have an open status and are unassigned and available to be processed by any user from the RF batch-picking program. Use Warehouse Transaction Inquiry (80.9.1) to view the status of the tasks.
    Built-In Recovery
    Warehouse staff who were batch picking from an RF device can automatically resume picking when they are back online. The system skips the order-selection frame on the RF and redisplays the picking screen that displayed when the system went offline. The recovery functionality ensures that tasks previously selected but not picked are available for picking. Warehouse staff can resume picking and dropping off all or some boxes as usual.
    Batch Picking Tasks Report
    A new Batch Picking Tasks Report (80.15.22.10) displays all open batch-picking tasks. Use the report to determine which tasks warehouse staff have performed and when. You specify the site and warehouse, then enter a range of item numbers or transaction numbers. See Batch Picking Tasks Report (80.15.22.10).
    Batch Picking Tasks Report (80.15.22.10)
    Site
    Enter the site for the open tasks you want to report.
    Warehouse
    Enter the warehouse for the open tasks you want to report.
    Item Number/To
    Enter a range of item numbers with open tasks.
    Transaction/To
    Enter a range of transaction numbers with open tasks.
    The system reports information from transaction history and displays the open tasks for the item or transaction. Open Tasks Reported shows a report with open tasks by transaction.
    Open Tasks Reported
    Backflushing Items From Dedicated Locations
    You can now backflush repetitive items from a dedicated location. Dedicated locations, or home locations, are picking area locations that always store the same item. AIM now includes a new PK algorithm (algorithm 70) that finds stock in a dedicated location, so warehouse staff can now pick items in the dedicated location. The PK algorithm works with a new PICK-RBK transaction type that backflushes repetitive items from a dedicated location. You can modify parameter settings for the new PICK-RBK transaction type in Transaction Type Maintenance (80.7.6).
    To use the new PICK-RBK transaction type, you must set up the algorithm for use by performing the following:
    1
    Use Algorithm Master Maintenance (80.6.5) to optionally modify the description of the new pick-by-dedicated location algorithm.
    2
    Use Transaction Type Maintenance (80.7.6) to review the transaction and Whse Master List Maintenance (80.1.5) to ensure that the PICK-RBK transaction is linked to the item you want staff to pick from the dedicated location.
    3
    Use Algorithm Assignment Maintenance (80.6.9) to link the algorithm sequence to the PICK-RBK transaction. This ensures that AIM uses the correct algorithm when it processes inventory from the dedicated location.
    4
    In Location Maintenance (80.3.13.1), specify the physical location for the dedicated location in the header and set the Dedicated field of the AIM Location Data frame to Yes. This ensures the location is for only one item or product. See Location Maintenance (80.3.13.1), AIM Location Data Frame.
    Location Maintenance (80.3.13.1), AIM Location Data Frame
    Picking from Negative Inventory during a Backflush
    Warehouse staff do not always have the time to update the system with the last transfer. During a backflush, this can result in a negative inventory from a system point of view. Warehouse staff can now pick components during a repetitive backflush from a dedicated location even when the inventory is negative. AIM lets warehouse staff pick from negative inventory for transaction type PICK-RPS when the inventory status code associated with the location has Overissue set to Yes in Inventory Status Code Maintenance (1.1.1). Warehouse staff can now continue to receive work orders and continue with shipping when inventory is negative. You can check the status of the inventory using Inventory Detail Inquiry (80.9.13).
    Reassigning Hard Assigned Tasks
    In AIM, tasks are hard assigned to the user; that is, by default all tasks for the selected order/pre-shipper/customer combination are assigned to the user only and viewable by the user only. You can now restrict the number of tasks assigned to a user and resort tasks by editing the whbpklx2.p sorting procedure. The sorting procedure is the default procedure in the Batch Picking Task Sort field in the Local Exit Routine Control File (80.24.23).
    You can edit whbpklx2.p to change the following default task-sorting order:
    Travel sequence
    Alphabetical order of location
    Task priority (descending, highest priority first)
    Additionally, since the whbpklx2.p program receives the current user ID parameter, you can use the sorting procedure to retrieve all tasks assigned to a user. Once retrieved, you can resort the tasks and remove task assignments based on any logic. For example, you can resort tasks by weight rather than travel location so that pickers can place heavy items on the bottom of a pallet. You can add a look-up window to the whbpklx2.p program so that warehouse staff can resort the tasks manually before starting to pick.
    Batch Picking to a Kit
    You can now pick to a kit in addition to picking to a box when batch picking. A kit is a set of items that are picked for shipment. No real assembly takes place. The configured item is not itself a physical entity—it only exists as a logical superset of its components. The configuration defines the content of a kit, and a shipment contains the end items that comprise the kit. You set up kits as configured items in MFG/PRO. See Chapter 9 of User Guide: Volume 2A Distribution.
    To pick to a kit, specify a kit as a reference by setting the Container/Reference field in the Batch Picking Control File (80.15.24) to Reference. When you specify a kit as a reference, the system uses the reference field of the inventory record as the placeholder for a kit number. All items placed in the same kit have the same reference number.
    Batch Picking Control File (80.15.24)
    Moving Items to Another Box
    Warehouse staff can now press F7 on the RF device to move contents from one box to another box during picking. This helps staff balance the content of different boxes based on the volume of the different items. Once staff press F7, the system prompts to enter a new container ID. See RF Move Box Prompt.
    RF Move Box Prompt
    Skipping Tasks
    Users can now press F5 on the RF device to skip a task and move it to the end of the task queue. This is useful, for example, should a warehouse aisle become blocked.
    Note: Some UNIX terminals, LINUX terminals, and RF devices do not map the F5 key. Typically, terminal users can use the emulation software’s key mapping tool; however, users may require the Progress protermcap file to map the F5 key. For RF devices, key mapping may depend on hardware vendors.
    Fixes
    1
    In the RF batch-picking program, the Destination Reference field is now updated with the box number when batch picking for distribution orders.
    2
    If you press F3 in the Order Selection frame of the RF, the batch picking program no longer crashes.
    3
    Batch picking now works when you activate the PRO/PLUS Supplier Performance (5.15) module.
    4
    Warehouse staff can receive a pallet in one location with two identical internal routings (IR) without creating a new task.
    5
    AIM now automatically creates multiple references for pallets when staff receive serialized items on multiple pallets using one of the following receipt programs:
    ReceiptsUnplanned (3.9)
    Purchase Order Receipts (5.13.1)
    Work Order Receipt (16.11)
    Work Order Receipt Backflush (16.12)
    Work Order Operation Backflush (16.19)
    6
    AIM now works correctly with reserved locations introduced in MFG/PRO eB2. A reserved location is an eB2 feature that lets you reserve stock that is in a location for a particular customer. AIM now:
    Provides a PK algorithm (algorithm 103) to pick in the reserved locations
    Provides algorithms that reject reserved locations if staff do not pick for a ship-to code with a reserved location
    You can modify parameter settings for the algorithms in Algorithm Master Maintenance (80.6.5).
    7
    With distributed orders, when you transfer items with an expiration date, the receiving site now includes the expiration date for the item.
    When an item with an expiration date was transferred with distributed requirements planning (DRP) to another site, the receiving site excluded the expiration date and left the date blank or recalculated it. Expiration dates are important, especially for warehouses that store food, so receiving sites in AIM now have the same expiration date as the sending site.
    8
    AIM triggers in DRP now work correctly.
    When a receipt location changes from an AIM location to a non-AIM location, the trigger to generate references is no longer set. Since warehouse staff stock goods during a receipt in either AIM or non-AIM warehouses, the trigger is not set until after the user enters the location.
    9
    Repick and cross-docking tasks are now added to any open pre-shipper.
    Shortage clearance algorithms are used when receiving stock that is immediately required to fill short orders. The inventory is moved from receipt to dispatch, being stored in between. This type of movement is also known as cross-docking. A repick is new, typically shortened picking that staff perform, for instance, when inventory is missing and they want to fulfill the order quantity by picking the item in another location.
    Previously, when you specified that the system perform a detail allocation during shortage clearance by setting Shortage Action to option 2, Inventory Transfer & Detail Allocation, in Transaction Type Maintenance (80.7.6), the system created a new pre-shipper instead of looking for an open pre-shipper. So, when staff repicked or picked for cross-docking, two or more shipper documents existed. Now the system looks for any open pre-shipper and adds lines to it. This only works if the pre-shipper was not converted to a shipper; if converted, the system adds the lines on a new pre-shipper.
    10
    Warehouse staff can now use shortage clearance algorithms with distribution orders.
    AIM 2.3c SSD Implementation
    This section describes assumptions, limitations, and guidelines when implementing AIM 2.3c SSD.
    Assumptions
    The following are assumed when implementing AIM 2.3c SSD:
    Settings in AIM control programs apply to all domains in a database.
    AIM can be used with multiple domains, but no cross-domain features are supported. You can use AIM functions only within a primary site within the current domain.
    Site-independent settings defined in AIM in the functions listed in Programs with General Settings apply to all domains within a database.
    Programs with General Settings
    Function
    Menu
    Description
    whermt.p
    80.2.13
    External Routing Maintenance
    whummt.p
    80.5.1
    Alternate UM Maintenance
    whppugmt.p
    80.5.5
    UM-Group Maintenance
    whppugen.p
    80.5.9
    UM Conversion Generation
    whaltymt.p
    80.6.1
    Algorithm Type Maintenance
    whalmmt.p
    80.6.5
    Algorithm Master Maintenance
    whtrttmt.p
    80.7.6
    Transaction Type Maintenance
    whlmtkmt.p
    80.11.1
    Task Maintenance
    whlmatmt.p
    80.11.3
    Alternate Task Maintenance
    whlmttmt.p
    80.11.5
    Task Times Maintenance
    whlmtamt.p
    80.11.7
    Task Assignment Maintenance
    whlmusmt.p
    80.11.13
    User Maintenance
    whsyugmt.p
    80.11.15
    Group Maintenance
    whlmcamt.p
    80.11.17
    Calendar Maintenance
    whsyugmt.p
    80.19.1
    User Group Maintenance
    whcodemt.p
    80.24.21.1
    Generalized Codes Maintenance
    Limitations
    AIM 2.3c SSD does not work with Enhanced Controls. Enhanced Controls tracks changes that were made for every record by using a unique key value. Enhanced Controls adds the unique key to all MFG/PRO tables. For AIM 2.3c SSD, the key is not added to AIM tables and the Enhanced Controls functionality does not apply.
    Guidelines
    When implementing AIM 2.3c SSD, you should ensure that:
    Order numbers are unique across domains in the database; the same order number does not exist in two domains. You can do this by using a unique order prefix for each domain in the various programs that manage order numbering such as Sales Order Control (7.1.24).
    Item, customer, and supplier codes are either unique across domains or if the same numbers exist in more than one domain, they point to identical information. So, you can have a physical item, customer, or supplier with the same code in more than one domain or a with a different code in more than one domain; however, you cannot have the same code in more than one domain for the item, customer, or supplier if the code represents a different physical item or a different customer or supplier.