Can LQ01 be used to transfer inventory into and out of the same storage location?

[Former Member]

We use carts to store inventory in a warehouse. Each cart has a series of warehouse storage bins that hold inventory. LQ01 makes it very easy to select a full cart and it's associated storage bins and move that cart from one storage location to another storage location. However, I am not sure I can use LQ01 to move the cart back to the original storage location at a later time. Example: I have inventory in the following -

Warehouse: '300'

Storage type: 'RES'

Plant: 'FG01'

Source sLoc: 'HOLD'

I want to move to

Warehouse: '300'

Storage type: 'RES'

Plant: 'FG01'

Source sLoc: 'OPEN'

I am using LQ01 to do this and it works just fine. My problem is that I want to move it back. I am unable to determine if I can configure to allow moves in both directions.

[VeselinaPeykova]

With separate storage types and no SU management this is definitely possible (I made a quick test in a sandbox), but with a single one I don't see a standard way to maintain this, because LGNUM, LGTYP and WERKS are key fields in T302A.

[Former Member]

ZQRUNTUNT-001 through UNT-100

[Former Member]

Thank you Veselina,

Unfortunately, I was hoping for a solution where I could use the same sType. The physical area in the warehouse is represented by a single sType. The carts are moved through multiple storage locations in the same area.

Regards,

Barry

[VeselinaPeykova]

If I were to set up the process, I would have done it with 3 storage types - one for the main area (which can have products from both storage locations) and two virtual ones AAA and BBB.

This would mean that if I want to move stock from storage location AAAA to BBBB I would move material from the main area to AAA, perform LQ01, then move the sock back to the main area.

If I want to do the opposite - move the quantity to BBB, then LQ01 and then move the stock to the main area.

We did something similar many years ago (except that we did not combine posting changes and ended up with a custom transaction, but behind the scenes it was doing what I briefly described).