Package Location Mapping Follow
Package Location Mapping can be used by an admin-level user to add or remove packaging information at a location level.
- This page displays a category selection field, a supplier selection field and a search bar, as well as a table containing the following:
- Category - the CATEGORY > GROUP of this product.
- You will only be able to select sections you have the rights to in the location you are using to access Location Mapping.
- Product - the name of the product.
- Supplier - the supplier that provides this particular pack size.
- Pack-Size - the pack-size of this item.
- Locations - a tickbox field showing any locations the user has access to.
- Category - the CATEGORY > GROUP of this product.
Please note: This page will only display the locations the user viewing it has access to. If you'd like to allocate packaging across locations you do not have access to, you may need to contact the STO Support Team.
- You can navigate the page as is, using paging (<<previous and next>> buttons at the bottom of each page) or use the Category selection / Supplier selection / Search bar to narrow your field.
- Tick an empty box to add the corresponding package information at that location.
- Un-tick a box to remove the corresponding package information from that location.
- Bold ticks cannot be changed from this menu, as those items are currently active somewhere.
- Hover over bold ticks using your mouse cursor to reveal where those items are active.
- Before those items can be removed (unticked) from package location mapping, they will need to be removed from wherever they are active.
- In this way, location mapping can be used as a method of archiving.
- Allocating a package will automatically allocate the associated supplier and product header if they were not already active in that location.
- Removing a package will NOT automatically remove the associated supplier and product header from that location.
- Changes made are immediately auto-saved. Multiple changes in quick succession may result in a brief loading time.
Comments
0 comments
Article is closed for comments.