You’re offline. This is a read only version of the page.
145
Trying to figure out how to set it up so that different target license plate id is generated when doing SO/TO picking so that picking LP ID and target LP ID is one to one relationship.
All items belong to tracking dimension group with batch as primary stocking.
Example:
LP 001 (batch 011) and LP 002 (batch 012) are being picked for the same work (SO or TO).
Right now, the target license plate ID would be the same (combined into one) when different LP are picked at the same work. So, it only generate 1 record @ license plate label table since there is one target license plate. How do I get new target LP ID generated for every single picking LP so that I can have every picking LP record @ license plate label table?
Or how do I get different record created via unique batch number in LP plate label table even if the target LP ID is the same so that every unique batch number can be printed out as label even though LP ID for different batch maybe the same since that's really the end goal?
*This post is locked for comments
Hi, Guy:
Yes, by using "full", a new work can be created but operationally, it gets messy since WMS worker prints out the pick list with original work ID printed on it and the "full" will split the work and create new work ID afterwards on the fly which creates confusion for WMS workers since they only see the original work ID on the pick list. Going from stage to bay would also need the new work ID (after the split) to complete pick from stage and put to bay. I can make it work but difficult sell to end users. Thanks.
Hi usafrancis,
Have you thought about using the 'Full' function on the mobile device? After you pick the first Batch onto the first LP, when asked to pick the second Batch, hit the 'Full' button. AX will create a new Work header for the Batch you have picked, and ask you to complete the Put. You can then pick the second batch on its own LP.
That one should be possible, and shouldn't be to complex of a customization
Correction. Create separate record in LP label table per unique TLP/Batch combination is the true requirement after I think through it.
Thanks. How about creating separating records in license plate label table per unique batch number? Right now, it creates one record per one TLP at LP label table.
Breaking it into separate work headers is the only way you can achieve this requirement as of today. It is not possible to have more than one Target LP for one work header
A little more background info. Reservation hierarchy for item is batch reservation (already reserve batch numbers @ SO/TO). To simply the test, LP number vs batch number is one to one (in real data, one LP may contain multiple batches). Both batches (LPs) are in the same location "storage". When work is created, there are 2 picks @ the same work from storage location and want to be able to separate TLP generation for each LP picked.
Tried the workbreak route but does not break my TLP in the same work unless they are broken into separate work. There must be a way to break TLP in the same work and that's what I am trying to find.
I'd look more into calling the nesting function after each LP scan.
And repeat the pick step (with LP info cleared, obviously) to scan the next LP
@Ivan: this means you can execute only one pick for a Location (isn't that right) ?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (