How to create a PO linked to multiple vendors and ...
# ask-stanley-ai
p
How to create a PO linked to multiple vendors and how does this approach work - approach is to create a "Fake" vendor and assign it as the default for all your items. Then, run a map/reduce script every 15 minutes that looks at the Zip/Item and updates the vendor on the PO appropriately. This method would require a script to determine the closest geography to a customer destination, or a record for controlling the assignment based on zip codes.
c
AI generated answer (using internal Slack threads):
To create a Purchase Order (PO) linked to multiple vendors, you can use a workaround approach by creating a "Fake" vendor and assigning it as the default for all your items. Then, you can run a map/reduce script every 15 minutes that looks at the Zip/Item and updates the vendor on the PO appropriately. Here's a high-level overview of how this approach works: 1. Create a "Fake" Vendor: This vendor will be assigned as the default for all your items that you want to manage with this method. This is necessary because NetSuite only supports a single "default" vendor for each item. 2. Run a Map/Reduce Script: This script should be scheduled to run every 15 minutes. The script should look at the Zip/Item and update the vendor on the PO appropriately. This means that the script will determine which vendor is geographically closest to the customer destination and assign that vendor to the PO. This approach would require a script to determine the closest geography to a customer destination, or a record for controlling the assignment based on zip codes. This means that you would need to maintain a record of zip codes and their corresponding vendors. Please note that this approach might require significant scripting and maintenance work. It's also important to note that this is a workaround and might not be suitable for all use cases or business models. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.897978067
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.837024748
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.836510301
Please provide your feedback on this answer.