Skip to Content
avatar image
Former Member

RF Queue Management - Assign Areas and Activities to Queues

I am configuring within the RF Queue Management within Mobile Data Entry. In particular, I am assigning areas and activities to queues. I am configuring for "preparation for stock removal" transaction type "A". We have several types of stock removals (pick TO for deliveries, pick TO for production orders and goods receipt reversals).

My issue is when I assign a source storage type/picking area to each type of stock removal; the only way to distinguish between the three is the destination storage type, however this is not being considered in the settings for stock removals. I have the following example in my system:

Wse/Screen/Typ /Src.St.Ty/Src.PickA/Dest.St.Typ/Dest.Pick.A/Door (door is blank in all cases) => Queue

MEM / 2 / A / 001 / 50 / 100 / *** => Production

MEM / 2 / A / 001 / 50 / 902 / *** => Rec_Rvrsal

MEM / 2 / A / 001 / 50 / 916 / *** => DOM_15

When I perform a pick for a delivery; the queue being determined = 'production' (it should be DOM_15 based on the destination storage type 916). When I delete the queue assignment for production from the configuration settings noted above, the queue determined is "rec_rvrsal'. I believe it's because I have the same source storage types/picking areas and it's just finding the first one set in configuration.

I see the warnings when I configure these settings that for stock removal, destination storage type/picking area are not relevant.

So, my question, is there a way to determine different queues for stock removals when the source storage type and source picking areas are the same, but the destination storage types are unique? If not, how have other's gotten around this issue?

Thank you & regards,

Sandra Miner

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Sep 30, 2008 at 08:06 AM

    In the strategy how have u mapped this requirement? because functionally speaking u are instructing system that for stock removal put the destination storage type as 902 which is interim storage type for GR.

    So how system can allow picking from 902.

    MEM / 2 / A / 001 / 50 / 902 / *** => Rec_Rvrsal

    Next you are saying that do picking from 100 storage type which is meant for production supply

    MEM / 2 / A / 001 / 50 / 100 / *** => Production

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 30, 2008 at 01:17 PM

    Thank you for your response - I can see where I need to clarify my message to you.

    The queue I am trying to determine when we use the destination storage type 902 is Rec_Rvrsal. This is going to be utilized when we have a goods receipt reversal (e.g. 102 movement type). This is not for a pick from 902. The source storage type for this stock removal is 001, which can also be a source storage type for a production order or a delivery. Does this make sense? All of the movement types involved in these transactions are defined as stock removal (e.g. 102, 601 and 319).

    I hope this helps to clarify my issue.

    Regards,

    Sandra Miner

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 02, 2013 at 10:13 PM

    Hello Sandy,

    I am aware you will probably never see the answer, but for the sake of others having the same issue with queue management I'll answer what solved this problem for me.

    In the image below, you can see two examples, first one isn't working for me,
    the one where i use storage type 002 as source, and 001 and 100 as destination.

    I used *** for picking area.

    Second example that is working for me is where i use storage type 006 as source,
    and again 001 and 100 as two different possible destinations. This time without *** as picking area.

    If you don't use picking areas, just don't define it like i did for 006 storage type. If you use picking areas, you will have to define a record for every picking area in destination if you want to get this to work. It might be a lot of records to maintain but the point is it'll get you where you want to go...

    It does seem a bit odd that destination storage type itself with wildcard *** picking area isn't enough for system to see it as another record but in my WM configuration it works like that!

    IMG:

    Cheers.


    pastedImage_2.png (88.9 kB)
    Add comment
    10|10000 characters needed characters exceeded

    • Moderator message:

      Please do not reopen old questions

      Before you ask a question to the owner of the discussion, please check the user before adding a reply to him. If you click his name, then you are taken to his profile where you can see when he was last logged in. This can give you an impression if you can expect an answer from him.

      you can actually find this info:

      Last Logged In:Aug 17, 2010 1:51 AM