NetSuite环境下无WMS及第三方插件时，实现待打印拣货单自动邮件提醒的需求问询

Hey there, I’ve tackled exactly this kind of problem before—refreshing the pick list print page manually is such a tedious waste of time. The good news is you can build this entirely with NetSuite’s native tools: Saved Searches and SuiteScript 2.x. Here’s a step-by-step breakdown tailored to your needs:

Step 1: Create a Saved Search for Unprinted Pick Lists #

First, we need a way to reliably identify new pick lists that haven’t been printed yet. Create a saved search with these settings:

• Record Type: Pick List
• Filters:
  • Pick Status = Not Printed
    (We’ll add dynamic time-based filtering in the script to catch only new entries since the last run)
• Results: Include fields like Internal ID, Transaction Number, Created From (related sales order), and any other details your warehouse team needs in the alert.

Save this search and note its internal ID—you’ll need it for the script later.

Step 2: Write a Scheduled SuiteScript #

We’ll use a Scheduled Script to run the saved search on a regular interval, check for new pick lists, and send an email alert if there are any. Here’s a working, production-ready code example:

/**
 * @NApiVersion 2.x
 * @NScriptType ScheduledScript
 */
define(['N/search', 'N/email', 'N/runtime'], function(search, email, runtime) {
    function execute(context) {
        // Grab the last time the script ran (stored as a custom script parameter)
        const lastRunTimestamp = runtime.getCurrentScript().getParameter({name: 'custscript_pl_last_run'}) || new Date(0);
        
        // Load our saved pick list search
        const unprintedPickSearch = search.load({
            id: 'customsearch_new_unprinted_picklists' // Replace with your saved search ID
        });
        
        // Add a filter to only get pick lists created after the last script run
        unprintedPickSearch.filters.push(search.createFilter({
            name: 'createddate',
            operator: search.Operator.AFTER,
            values: lastRunTimestamp
        }));
        
        // Run the search and retrieve results (limit to 1000 to avoid performance issues)
        const searchResults = unprintedPickSearch.run().getRange({start: 0, end: 1000});
        
        if (searchResults.length > 0) {
            // Build the email body with clear, actionable pick list details
            let emailBody = '🚨 New unprinted pick lists are ready for processing:\n\n';
            searchResults.forEach(result => {
                const pickId = result.getValue({name: 'internalid'});
                const pickNumber = result.getValue({name: 'tranid'});
                const salesOrder = result.getText({name: 'createdfrom'});
                
                emailBody += `• Pick List #${pickNumber}\n`;
                emailBody += `  Related Sales Order: ${salesOrder}\n`;
                emailBody += `  Direct NetSuite Link: https://your-account.netsuite.com/app/accounting/transactions/picklist.nl?id=${pickId}\n\n`;
            });
            
            // Send the alert email to your warehouse team
            email.send({
                author: -5, // Uses the system admin as the sender (adjust if needed)
                recipients: 'warehouse-team@yourcompany.com', // Replace with your team's email
                subject: 'NetSuite Alert: New Pick Lists Ready to Print',
                body: emailBody
            });
            
            // Update the last run timestamp to avoid duplicate alerts
            runtime.getCurrentScript().setParameter({
                name: 'custscript_pl_last_run',
                value: new Date().toISOString()
            });
        }
    }
    
    return {
        execute: execute
    };
});

Step 3: Set Up Script Parameters and Deployment #

1. Add a Custom Script Parameter: When creating the script record, add a parameter named custscript_pl_last_run (match the name in your code) with type Date/Time. This tracks the script’s last run time to prevent duplicate alerts.
2. Deploy the Script: Assign a role with sufficient permissions—needs access to pick lists, saved searches, and email sending. Set the execution schedule: start with every 15 minutes (adjust based on your order volume; avoid overly frequent runs to protect NetSuite performance).
3. Test in Sandbox First: Run the script manually with test pick lists to confirm it sends emails correctly and doesn’t trigger duplicates before deploying to production.

Key Tips for Smooth Operation #

• Avoid Duplicate Alerts: The lastRunTimestamp filter ensures we only alert on pick lists created since the last script run—no more spam for the same entries.
• Permission Checks: Double-check that the deployment role has Send Email, View Pick Lists, and Run Saved Searches permissions to prevent script failures.
• Customize the Email: Tweak the email body to include extra fields your team cares about, like item counts, warehouse location, or priority status.

This setup is 100% native to NetSuite—no WMS or third-party plugins required. It’ll free up your team from mindless page refreshes and let them act on new pick lists as soon as they’re ready!

内容的提问来源于stack exchange，提问作者Joe Hall