- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I attended a lab at K26 that included an activity for receiving assets on the mobile device. I remember pinging a colleague during the lab excited to see that you could specify the aisle/space on the receiving screen, a new(er) feature in the HAM plugin that we had overlooked. I talked to the speaker to confirm this was OOTB in HAM 15.x but I am not seeing it. I've tried HAM 15.0.1 on Yokohama, Zurich and Australia and it's not showing up.
Is anyone else aware of this and know what I'm missing? It's been a few weeks now so of course I'm going crazy thinking I confused the put-away tasks, but I could have sworn it was on the regular receiving action for a PO Line Item (thus not requiring yet another step for the receiving team to first receive it, then go back to do a put-away).
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
From the schema, you see the task types in which the table is referenced; hence, it has to be a pick-up or put-away task, regardless of app or browser.
The reason I'm asking is after updating to v15, no aisle/space was not visible to some people at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Ryan S,
I just checked the schema on a Zurich instance, and the table is there and referenced in various other tables.
A UI policy "Show/Hide Aisle/space based on State/Substate" on alm_asset is hiding the field, in case the status is not equal to 6 = in stock or 11 = build and the field is only included on the workspace view of the asset.
For assets in stock, the field is shown together with the stockroom:
I'm on version 13 of the HAMP plugin. Would you mind verifying if it is the same with version 15?
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I checked on a Zurich instance running HAM 15 and it's the same. This doesn't address the issue of mobile receiving though. I see no mobile ui policies doing the same, and when receiving the assets wouldn't be in stock yet anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
From the schema, you see the task types in which the table is referenced; hence, it has to be a pick-up or put-away task, regardless of app or browser.
The reason I'm asking is after updating to v15, no aisle/space was not visible to some people at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Oh duh! I glanced right over that part thought it was included. Thank you!