We are running an older version of On-Prem Lawson M3 (10.1.11) on an iSeries. All of our parts in the Item Master are configured as Not Lot Controlled, Lot ctrl method = 0 and Lot numb method = 0. The plan is to turn Lot Control on for all of them, Lot ctrl method = 3 and Lot numb method = 4 or 5. I don't have a problem with the Parts that has no inventory and no planning. I'll just write a SQL Update for them. looking for advise on how to best tackle the Read more...parts with Inventory and/or Planning? Your advice is much appreciated. Thank you. Show less...
Hi Sam, We have a variety of both lot controlled and not lot controlled items. Before moving forward with changing ALL, I trust there has been a solid review of the impacts. When we have moved items to lot controlled, we first have to wipe out the inventory of the items. We created Requisition Order types to do the removal and then one to add it back in. You will need to know what the lots are on hand for the items that you are adding back. Getting that accurate information to add them back in Read more...we have done in small groups as we would be challenged with getting all the lot numbers in all of the locations that were not previously captured. In that version of M3 you also could potentially use CRS800 for a mass change with some parameters fencing it in to reduce risk. We also have some product structures that backflush components and that is to be avoided with a lot controlled item or you will get the dreaded 8888888888 lot numbers. Just some lessons learned from my view point. I am sure there is more to consider. Show less...
Hi Sam, As I am sure you are aware, you need to remove all orders and all inventory from the system to hit that flag and then try to put it all back. Do not get tempted to do this with SQL, that would be fantastically risky and you'd be dealing with gremlins and data corruption for weeks.
You can do a big RO to book out all the inventory and another big one to put it all back. That's not impossibly hard to do with the API tools. The scary part is going to be the Read more...orders, you'd have to close all the lines and re-open new lines. This is also not impossible with API tools, but anything in a partial status will probably be problematic. You can't have anything in a status 44 or 66, and split statuses will need to be separated into different order lines. Each category of order that is affected (CO, PO, DO, RO, MO issue, MO receipt) will have to be considered separately with a different combination of APIs to make sure you are not breaking anything.
Really, the easier, safer solution is to just create new items and make use of replacement item # functionality in MMS020. If done properly you can automatically roll the item statistics from the old item to the new one without losing much from a reporting standpoint. And if you needed to accelerate the phase in of the new item you could try using MMS130 to reclassify the old stock to the new one directly. Show less...
Thank you for your feedback Karen and William. But I am not too familiar with RO's to remove stock and put back in. Can you give me more details on how to do it? Do I need to create an Otp with the right Transaction type? What would that be? And how do I process it to remove and put it back in. Allocate, Pick and issue the stock to the RO? what about putting the stock back in? I'd like to test it first natively with a simple part and then build data files for API's. Sorry, too many Read more...questions. Thank you. Show less...
Hi Sam, the terminology for requisition orders in M3 is essentially what inventory managers or controllers call stock adjustments and stock movements. Where they might be writing off parts that have gone missing or writing 'in' parts that were not accounted for (stock adjustments). Infor's documentation on 'Requisition Order Flow' is a good place to start. The picking step for us is automated (no picking) but your company may want to have a receiving step to do a final validation on what is Read more...being 'written off' - but this could be automated too.
The very first programs related to this is CRS200 (Order Types), MMS100/MWS300 (DO/RO), MWS010 (dispatch policy). Of course there are many other decision factors in other programs, but what Karen is referring to is creating two Requisition Orders (meaning at least two different order types) - to answer your question you will need to pick the correct transaction type 40 and 41.
