MSCM locations

Another user, who no longer works at our facility, setup all of our RQ01 locations in IC02, for MSCM. I understood that IC02 setup is for receiving locations such as inventory stock room, etc.

Would you not setup the RQ01 locations in MSCM as requesting locations, and not add them to IC02?

Can anyone clarify is this was done incorrectly, or am I misunderstanding MSCM setup requirements?

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

kim-gonzalez

When you create an IC81 Cart Par Location an IC02 record is automatically created and some RQ01 data may be updated as well (location name, from company and location). You will notice there is also a set of IC12 records created for the par location as well.

jon-athey

As said the IC02 records are auto created so I wouldn't worry about them but when I build a new par in IC81 I make sure I update the RQ01 record (also auto created) with the buyer, process level and I'll enter a default issue account.

unknown

Thank you, V and Jon. I know that creating an IC81 par location does create the RQ01 (which as you say, Jon, needs the additional information), and I forgot the IC81 also creates the IC02. So thank you for that reminder. My understanding was - requesting locations (RQ01) that are not IC81 setups, but are created for requesters to use on RQC, should not be in IC02. When a requisition becomes a PO, the deliveru ticket prints the source record information from RQ01 for delivery. My assumption is that MSCM/RAD would work off of Lawson the same way....the requisition, to a PO, would have the receipt/delivery ticket pull the delivery information from RQ01 - thus I would not setup these non IC81 locations in IC02. Is that making sense?

Vicky

jon-athey

That is correct, you don't need an IC02 record for the standard (non-par) RQ01 records. And delivery information is pulled from the requesting location in the PO line source (PO44). We're not using RAD but I would assume it would be the same.

Copyright © 2025 Infor. All rights reserved.