Currently the Product status field in Product - sites task is pulled from the Product record and not editable in the Product - sites task. Would like to be able to activate/deactivate individual products by site.
by: Lynne A. | over a year ago | Distribution
Comments
I like this idea but with over 30 sites and 16000 product records it could become cumbersome. I would suggest a two stage process where the product could be left as active on the product record but inactive on individual sites. If set as inactive on the product record all sites would become inactive.
We need the feature where the product is left as active, but the Product Site is able to be deactivated. We have many cases where the product is still active and sold out of our primary location and no longer sold out of our other warehouse. Sales finds it confusing when they look at stock by site and see the warehouse show up, but with zero stock. They assume we just need to replenish that warehouse, not that we no longer carry it there.
Two things we reportedly need to manage at Product-site level to cover hips of Client business processes:
1. Product-Site-Supplier (specially when creating Back 2 back PO from a SO, it only takes the highest supplier in priority rank defined at product level, where we need this at Product-site level. Add to this, supplier UOM, QC control, etc. to be defined at Product-site level).
Example: If a Client has 3 or more sites where each site can be potentially the supplier of other sites when B2B is "source of delivery" on SO lines, then we need to define their relationships/priority at Product-site level and this information has to be populated on SO line, then to generate PO or POs for related Suppliers.
If this is not possible for any reason, the other solution can be at least having a "Pop-up" windows at the time of hitting "Back 2 back" button in a SO with the list of all potential B2B suppliers defined at Product (or ideally Product-site level) so that user can have an option to chose which supplier they want to create the B2B PO for.
2. Product-Site-Customer (the same as Supplier requirement at Product-site level, we need to be able to define this crossing to manage UOM as an example for a specific customer at Product-site level or Pricing requirements).