Fixes
• The warehouse task creation functions now process correctly and generate shortage tasks (SHRT-WO) for the movement of inventory from receiving locations to production locations. Previously, the system did not create the shortage tasks.
• Purchase Order Receipts (5.13.1) now correctly creates the discrete work order shortage task (SHRT-WO) task when the following conditions exist:
• You partially receive a PO.
• There is not enough inventory available for the component during a work order release.
• You set Shortage Action to 3 in Transaction Type Maintenance (4.7.1).
• Inventory is detailed allocated at the destination location after a task confirmation.
Previously, when these conditions existed, the system displayed an error that informed you that the short action changes did not allow the SHRT-WO transaction to exist and the system did not make changes.
• Warehouse Transaction Inquiry (4.9.1) now correctly displays the current User ID for all open tasks (PICK-DO) of the same distribution order, similar to sales orders, when you confirm the task using the RF Next Task (1.1) option, and set the Flavor to type C and the Multi-bin Pick Flavor C Sort to 0 in Warehouse Maintenance (4.1.1).
• Work Order Receipt Backflush (16.12) no longer creates the RCT-WO task when you set:
• Selective Inspection to Yes and the Sample Percent to 100 in Item-Warehouse Maintenance (4.11)
• Clear Shortages to Yes in Internal Routing Maintenance (4.2.5)
Previously, in this scenario, the system created the RCT-WO transaction along with the INSP-WO transaction.
• For a repetitive work order, the system now correctly deletes the allocation at the destination location when staff move the item from the source location to the destination location when they confirm the PICK-RPS task.
• Logistic UM Pallet Create/Transfer (4.17.17) no longer displays an error informing you that a unit of measure conversion does not exist and now correctly generates pallets when you define the UM conversion for an item in Unit of Measure Maintenance (1.13).
• Inventory Detail Inquiry (4.9.13) no longer displays a blank value for the alternate UM after you receive inventory at the destination location.
• The RF BP Pick SO/DO (3.1) and RF BP Pick All (3.2) options no longer make the item, lot, and reference number blank in the pre-shipper when:
• You change the lot/reference while confirming.
• The system locks the schedule order in the pre-shipper because it is accessed by Required Ship Schedule Maint (7.5.3) and you press CTRL-C to cancel the task.
• You continue confirming the task after the lock is released without quiting the task.
Previously, in this scenario, the system set the pre-shipper item, lot, and reference number to a blank value.
• Work Order Receipt Backflush (6.12) no longer displays an error informing you that the reference is already in use when the reference being received exists in inventory for a different item and you set the Reference Uniqueness Level to L (references are unique within each location) in Warehouse Management Control (4.24). Previously, in this scenario, the system displayed an error.
• Pre-Shipper/Shipper Print (7.9.4) now displays the correct authorization number and pegged quantity when schedules are created for a different date and you confirm the task in Movement Confirmation Workbench (4.8.7) with a quantity of 0 (zero) and the Comp option set to Yes. Previously, in this scenario, the system created an incorrect authorization number and pegged quantity.
• The RF Location Audit (1.4) option no longer displays the first item record (that is, the record of the first lot number) when staff select the second record to update and there are multiple records of the same item with the same reference but different lot numbers.
• DO Warehouse Data Maintenance (4.13.6) now displays the receiving warehouse and Wave Selection (4.15.3) lets you select the DO when the system creates a requisition in Intersite Request Maintenance (12.15.1) and the requisition is linked to a DO in Distribution Order Maintenance (12.17.14).
• Distribution Order Maintenance (12.17.14) and Distribution Order Processing (12.17.21) now correctly display and update shipping locations. As part of this correction, Label Master Maintenance (36.4.17.1) now includes a new Ship Location field that is attached to Label Detail Maintenance (36.4.17.5).
• The system no longer displays the quantity on hand of an item for the on-the-fly transfer task (OTF-TR) that the system displays in the Expected quantity field and now correctly displays the quantity staff enter when they transfer an item from one location to another using the RF Transfer (1.3) option.
• DO Pre-Shipper/Shipper Maintenance (12.19.3) no longer displays the Progress error: sr_wkfl exists with Domain xxx Session ID xxx, sr_lineid Lot/Serial xxx, Ref <blank> —where xxx is the ID or number—when the following conditions exist:
• Staff confirm warehouse tasks that have the same destination site.
• The reference is removed during the pick using RF pick options.
• You set the To Reference Option to 1 in Internal Routing Maintenance (4.2.5).
• The RF Next Task (1.1) and RF Select Task (1.2) options now correctly display frames with warning messages that warn users to get or take stock from locations when they confirm an inter-warehouse transaction. Previously, the warning message remained on the RF screen after pressing the space bar and the frame was distorted.
• The Next Task (1.1) option and the following programs now let RF users switch tasks for stage out or stage in locations when you specify a location for the StageOut/StageIn field for a single warehouse location in Warehouse Location Maintenance (4.3.13) and set Allow Task Switching to Yes in Work Location Group Maintenance (4.3.9). Previously, users could not switch the task.
• RF Select Task (1.2)
• RF PreShip Sel Task (1.7)
• RF Order Sel Task (1.4)
• You can now enter decimal values in the Sample Qty field in Item-Warehouse Maintenance (4.4.11) and the following programs:
|
Multi-Level Item Inquiry (4.4.6)
|
Item-Warehouse Inquiry (4.4.12)
|
|
Multi-Level Item Maintenance (4.4.5)
|
Item Inquiry (4.4.8)
|
|
Item-Site Inquiry (4.4.10)
|
Item Maintenance (4.4.7)
|
|
Item-Site Maintenance (4.4.9)
|
Item-Warehouse Maintenance (4.4.11
|
|
Supplier Item Inspection Maint (4.4.13)
|
Supplier Item Inspection Report (4.4.15)
|
|
Sample Inspection Report (4.19.3)
|
Sample Inspection Maintenance (4.19.1)
|
|
Sample Inspection Workbench (4.19.4)
|
Inspection History Maintenance (4.19.17)
|
As part of the resolution:
• The format of the existing fields were changed from integer to decimal in the database schema for the Sample Qty field, and the previous field of integer data type was renamed to a QAD reserved field.
• New utility programs let you store the existing value of Sample Qty from integer to decimal form:
• InspH_cv93.p
• PartWhseM_cv93.p
• pt_mstr_cv93.p
• pti_det_cv93.p
• VendPartM_cv93.p
• For EE, a conversion program lets you move the field value from the previous field to a newly created field. The conversion program runs automatically through the QAD conversion/upgrade process.
• The Algo Nbr displays separately as an integer in Sample Inspection Report (4.19.3).
• The system no longer assigns an incorrect algorithm number (value of 10) when staff perform a PO receipt using Purchase Order Receipts (5.13.1) with inspections set for multiple pallets.
• The system no longer sets the ABS ID and Shipper ID fields as blank on the warehousing task in DO Pre-shipper/Shipper Maintenance (12.19.3) when a single pre-shipper line exists for the distribution order line and the corresponding warehousing task exists. Previously, both fields were blank under these conditions and when users added a new line or created a pre-shipper/shipper in the program.
• The RF Pallet Explosion (3.6) option no longer displays the Progress error, ** Invalid character in numeric input s. (76),when the system explodes the second pallet of the same SO or DO pre-shipper line with these conditions:
• Explode second pallet after generating an SO/DO shipper using Wave Replenishment (4.15.6).
• Change the Qty Ordered field value of the SO/DO.
• Use Wave Replenishment after you change the Qty Ordered value.
• The QAD Enterprise software no longer overrides QAD Warehousing software and the system now uses the correct default location when:
• You set the Inspect Flag to Yes in either Item-Site Planning Maintenance (1.4.17) or Item Master Maintenance (1.4.1).
• You create a purchase order in Purchase Order Maintenance (5.7).
Previously, with these conditions, the system did not use the correct default location for QAD Warehousing and instead, used the location available in the Inspection Location field in Purchasing Control (5.24).
• The RF Container Build (3.3) and RF Pallet Explode options no longer let users explode an already exploded item reference. When they try, the system displays an error message informing users that the items are already contained and prohibits further processing. In addition, when you release another wave for the same ship-from/to using Wave Replenishment the system completes the processing and generates a pre-shipper. Previously, users could explode the item reference, but the system would not complete processing.
Performance issues were resolved when you release a work order or use Wave Release (4.15.8) and the system is using the QAD Warehousing location find (LF) algorithm 3.
• The system now lets RF users switch tasks when they enter a stage-in location during RF Next Task (1.1) processing. Previously, the system displayed an error that indicated no tasks were available. The correction also applies to the following RF programs:
• Select Task (1.2)
• PreShip Sel Task (1.7)
• Task confirmation options (4.8.x programs)
• The RF BP Pick All (3.2) option no longer prompts users to enter a value in the Container field while confirming WO or RPS pick tasks when you set the Container/Reference field to Container in Batch Picking Control (4.15.24). Previously, the system prompted for the container even though the RF tasks were related to work orders, not SOs or DOs.
• The system no longer displays an incorrect error message in either the RF BP Pick SO/DO (3.1) or RF BP Pick All (3.2) option when staff scan lot/serial and references. Previously, the error displayed in the two RF options even when staff scanned valid lot/serial or references and the following were set as required in Batch Picking Control (4.15.24):
• References
• Scan references
• Lot/serial
• Scan lot/serial
• Repetitive Picklist Calculation (18.22.3.1) now correctly considers the warehouse picking logic when:
• Warehouse master list is being used in Item Master maintenance (.4.1) with algorithm 36.
• Item-Site Maintenance (4.4.9) is used at the site level.
Put Away/Loc Find Simulation (4.6.13) now displays locations considering their available capacity and rules as specified in the putaway (PA) algorithms 2 and 3 while simulating inventory receipts when staff leave the RF Lot/Serial and Reference fields blank. Previously, in this scenario, the system displayed only one location for the entire simulated inventory receipt and did not consider available capacity.
• Wave Replenishment (4.15.6) no longer has performance issues when you replenish or release a wave and the wave release consists of many open and closed pre-shippers with many lines for the same ship-to. Previously, the system checked all pre-shipper lines and when many closed pre-shippers for the ship-to existed, there was no filtering of closed pre-shippers while open pre-shippers were searched, leading to a performance issue.
• The RF Next Task (1.2) option and the following RF programs now display an error informing you that lot/serial numbers are required or that a quantity of -1 or 1 should be entered for the lot/serial-controlled item when staff enter a blank value in the Lot/Serial field.
• Select Task (1.2)
• PreShip Sel Task (1.7)
• Order Sel Task (1.14)
Previously, the system did not display an error and confirmed the task.
• The following RF programs now correctly transfer alternate units of measure to the destination locations:
• Transfer - Single Item (3.4.1)
• Transfer - Multi Item (3.4.2)
• Transfer With Lot/Serial Change (3.4.3)
• Batchload Transfer with Lot/Serial (3.4.4)
Previously, the alternate units of measure did not transfer because the system did not assign the alternate UM of the source location to the alternate UM of the destination location.
• The RF system no longer has navigation problem between menus. Previously, in an RF menu option when users scrolled using the cursor, arrows, or buttons instead of typing the menu option number, the system displayed previous menu options and not the menu options from which the current program that just completed processing was invoked.
Wave Selection (4.15.3) now includes the same selection criteria to add orders to the wave as the initial selection criteria. Previously, when you added orders, the reference choice was missing as well as the time.
• Put Away/Loc Find Simulation (4.6.13) now displays the correct destination location when the alternate UM is blank or when the alternate UM is not blank and the displayed locations are not the same as the actual warehouse transaction’s To Location for putaway algorithm 61. Previously, the system did not consider the capacity and algorithm when displaying destination locations for the warehousing transaction PA/LF simulation.
• The system no longer displays an error informing you that there are no pre-shippers for a wave when you enter the Wave Pre-Shipper Workbench (4.15.14) after containerization of a pallet using the RF Pallet Explosion (3.6) option. Previously, in this scenario, the error displayed.
Distributed Order Receipt (12.15.20) and the RF Receipts (1.8) option no longer display an error informing you that the quantity available in the site location for lot/serial is 0 (zero) when you receive an item with a logistics UM that is different than the base UM in Item-Warehouse Maintenance (4.4.11).
• The RF Select Task (1.2) option and the following programs no longer create duplicate transactions from an intermediate location to a destination location when there are more than two routing sequences in Internal Routing Maintenance (4.2.5) and you confirm the full task from the stage-out location to the intermediate location. Also, the same programs now correctly update inventory in Inventory Detail Inquiry (4.8.17) when there are more than two routing sequences in Internal Routing Maintenance and a partial task is confirmed.
• Movement Conf. By Transaction (4.8.1)
• Movement Conf. By Location (4.8.2)
• Movement Conf. By Order (4.8.3)
• Movement Conf. Workbench (4.8.4)
• Movement Conf. Processor (4.8.5)
• Movement Conf. Inquiry Format (4.8.6)
• RF Next Task (1.1)
• Sales Order Shipper Maintenance (7.9.8) now correctly defaults the Multi Entry field to No in Item-Warehouse Maintenance (4.4.11) and does not generate a reference when you define the UM conversion in Unit of Measure Maintenance (1.13) for the item and the system uses the alternate UM as the logistics UM in Item-Warehouse Maintenance. Previously, in this scenario, the system defaulted Multi Entry to Yes and generated new references.
• The system now displays the correct destination location in Put Away/Loc Find Simulation (4.6.13) and Warehouse Transaction Inquiry (4.9.1). Previously, the system displayed the wrong destination location because it did not sort locations first by popularity code and then by location code.
• Inventory Detail Inquiry (4.9.13) no longer displays a blank value for the alternate UM after staff receive inventory at the destination location for a distribution order when existing inventory moves into the pallets.
• Purchase Order Receipt (5.13.1) now updates the consignment quantity to the location detail when you specify the warehouse as the receipt location, and Inventory Detail Inquiry now displays the correct alternate UM when staff use the RF Kanban Scan (1.5) option to move inventory and you define the logistics UM in Item-Warehouse Maintenance for the part, site, and warehouse.
• Movement Conf. Processor By Transaction no longer increases the inventory, making it double in quantity. Previously, the program confirmed the cycle count task, created the recount task, and then confirmed the recount task—so that the inventory doubled.
• Replenishment Request (4.16.13) and the RF Kanban Scan option now correctly consider the internal routing sequence to generate replenish tasks between two warehouses. Previously, only external routing was considered.
• Available Kit Quantity to Ship (7.1.8) and Picklist/Pre-Shipper – Automatic (7.9.1) now pick the correct quantity of component items for a kit item when:
• The quantity available for the component item is less than the required quantity.
• You use pallets for components.
• You set Allow Split to No in any of the Warehousing programs that have this field: Hold Maintenance (4.3.23.1), Alternate Unit of Measure Maint (4.5.1), Storage location Group Maint (4.3.1), and so on.
• The system no longer sets the ABS ID and Shipper ID fields as blank for warehousing tasks in DO Pre-shipper/Shipper Maintenance (12.19.3) when a single pre-shipper line exists for the DO order line and the corresponding warehousing tasks exist.
• The RF Location Audit (1.4) option no longer causes inventory to go below 0 (zero) when there is an active task being confirmed by one user, and another user simultaneously audits a location and reduces the location’s quantity on hand for the same inventory task being confirmed by first user.
• The system no longer displays an error informing you that the reference is already in use when you perform a multi-entry in PO Shipper Maintenance (5.13.14) and set the Reference Uniqueness Level to L (references are unique within each location) in Warehouse Management Control (4.24).