Par Location and Requesting Location Duplication

Hi,

We are trying to figure out what the implications are if we were to create a par location with the same name as a requesting location (5 character name).

Example:

We have our requesting location name 12345 for MOR. Currently the par location name is CORE1. If we were to change the par location name to 12345, what issues would arise by creating a par location name that is the same as a requesting location name?

Let me know if anyone needs additional info.
Thanks
John

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

unknown

Does it let you do this in test? Par locs create rq01 records. I would expect it to give you a "location already exists" type of error.

kim-gonzalez

When we change an IC81 par location name it automatically updates the RQ01 and IC02 names to match the new IC81 name

unknown

We use a different naming for our par locations. It's alpha numeric. A01P1 is one of ours.
A= building designator
01= 1st floor
P1= par location #1

We list the room # or cabinet # in the RQL_NAME.

unknown

Thanks for hte responses. We saw the same thing VMcNamar. When we created the IC81 location, it auto updated the RQ01 location name to the new info from IC81.

If we do this, will this affect the ordering process? Also, we are mapping this location into Epic's Optime. Will that affect any charging processes?

Thanks again!
John

unknown

Hi,

I have one more question. Let's say we have 1,000 items to load, but we only get 900 of them loaded (for whatever reason, we missed the last 100), will those missing 100 items still be available for ordering under the par location?

Thanks
John

kim-gonzalez

Orders process fine for us, but I cannot speak to Epic. You can only see the items loaded in IC81 on the handheld and in IC83. The other 100 items will not be visible. You could still order the items in RQ10 or RQC.

[Updated on 6/12/2015 11:42 AM]

Copyright © 2025 Infor. All rights reserved.