Cancelling a demand on inventory

[View:/cfs-file/__key/communityserver-discussions-components-files/12/WH20-WH25.docx:320:240]I am trying to cancel 2 demand records on an inventoried item, but running into some difficulty. If there is a true demand, then why can I not see them in WH20/25?

I have attached screenshots.

Thanks!

Find more posts tagged with

Infor Lawson Supply Chain Group - Discussion

Comments

jon-athey

WH20 shows demand that has not been picked up by WH130, meaning no shipment has been created for the demand. WH25 shows demand that has gone to backorder status (or unallocated status if you have batch allocation). Most likely the demand has been picked up for shipment and you should be able to drill on the req lines to find the shipments and enter these in WH32.2 to kill the lines. If you still can't find them you may have orphaned demand and will have to use a quickpaint screen (IC99.2) to correct the database (recommend you open a ticket with Infor if you're going to use a quickpaint screen).

0911060553270289.pdf

unknown

I have a similar but a little different situation. The IC238 report is showing stock on hand in certain bins, when all other inventory screens indicate that the stock is not there. I have already placed a ticket and Infor is doing some research. However, I was wondering if you have come across any documentation that lists the cause(s) of orphaned records?

unknown

Thank you Jon. I had not thought about WH32.2. I do see the items listed. What is the difference between Void/Kill and delete?

wstevens

Void/Kill will cancel the shipment and the demand. Delete will cancel the shipment/shipment line but not the demand and the item will go to backorder. It can then be re-allocated with WH110 or canceled on WH25.

jon-athey

If you delete the shipment line you'll be able to see the demand in WH20. It's like reverse WH130. You can then change the allocation and any unallocated quantity will show in WH25 where it can be cancelled. Lot of steps- easier to just void/kill the quantity in WH32.2 and be done with it.

jon-athey

Issac, that's a good question. Could be caused by the system or a process crashing or just a hiccup. I don't think anyone really knows and I've not seen any documentation on it.

unknown

Thanks!

Copyright © 2025 Infor. All rights reserved.