|
21591
|
Lawson Requisitions
|
Add Control to restrict Requisition UOM to Transaction Default UOM multiple for I type Items
|
While both RQ10 and RQC currently default the Item UOM from the Source Location Transaction Default UOM, the user is able to override this UOM with any UOM valid for the item. This allows the user to request a quantity which is not valid for shipping (e.g. user requests 5 EA when stockroom will only ship in Boxes of 6). This is especially difficult when the shipment is from our external warehouse where the line can not be voided as part of the shipping feedback (see separate Warehouse enhancement request)
|
Currently we do not ship the line in question (delete all allocations/backorders to close req line) and notify the user to reenter in the correct UOM. Requesters have been notified of policies, but this still occurs.
|
Create a control flag to optionally prevent users from releasing a requisition for an inventory item with a UOM which is not a multiple of source location Transaction Default UOM - e.g. If valid UOMs for item are EA, BX (of 10) and CA (of 100) and source location Transaction Default UOM is BX, Do not allow release of requisition with UOM of EA. Do allow release if UOM is BX or CA (CA UOM conversion factor is divided evenly by BX UOM conversion factor). Ideally have hierarchy of control flags (e.g. flag on Req Loc(RQ01) overrides flag on Location (IC02) which overrides flag on IC Company (IC01). If only one flag possible - should be set at IC Location level
|
|
21588
|
Lawson Warehouse
|
Add ability to overship or void remaining line quantity, or entire shipment through WH520 interface
|
WH520 shipment feedback should have same functionality as manual feedback (WH32) We need the ability for shipment confirmations coming from our external warehouse (via Wh520 - Location set up on WH02 as external warehouse) to void any remaining line quantity (kill any backorder / close requisition line), or Overship a specific line, or optionally void or backorder an entire shipment (simlar to backorder/void functionality on WH32). The need to void may come from a requester calling to indicate they no longer want an item, or entered the wrong quantity, or in cases where an item is out of stock and not being replenished (e.g. during product changeover). The need to overship an item may result from a requester requesting a non-shippable qty (e.g. request 5 EA instead of minimum ship qty of BX of 6), or due to inventory discrepancies which result in a partial allocation. Due to volume, and frequency of WH110 and WH130 jobs, it is currently difficult to catch and void backorders before they are reallocated and placed on a new shipment.
|
Zero/under Ship line on a shipment through WH520 (I believe if all lines set to zero will not process) Once WH520 job has processed, and before next WH110 job run, cancel backorder amounts in WH25/Wh25.2 to prevent reallocation by WH110 and new shipment creation. For shipment lines below minimum qyt, line must also be zero shipped and backorder cancelled manually
|
Add a flag to WH520 Record Type 1 (Header) which would Void (V) or Backorder (B) the entire shipment - should have same functionality as "Void" / "Backorder" Action on WH32 Add a flag to WH520 Record Type 2 (Line): - "V" would Void any remaining quantity (e.g. Open QTY minus In-Process qty) - should have same functionality as Line FC of Void on WH32. - "O" would allow overshipment of shipment line - should have same functionality as Line FC of Overship on WH32, but allow a shipment qty greater than allocated qty (e.g. requested 5, allocated 5, shipped 6)
|
|
16974
|
Lawson Procurement - Purchase Order
|
Add Deliver To field to PO01.2 Audit Rules options
|
When running an audit on changes to a PO on PO66, we are not able to view changes made to the Delivery To field. Searching the audit settings on (PO01) PO01.2 does not list the Deliver To field as an audtiable field. Would like this field added as an option in PO01.2 Audit Rules.
|
|
Add DELIVER TO (PLS-DELIVER-TO) field to PO01.2 Audit Rules.
|
