NetAsset – Inventory Reclass Cost Resync
Overview
In some environments, inventory reclass entries can become outdated when post-transaction costing updates occur. This often happens when an inventory reclass is generated from an Item Fulfillment, but the GL impact of that fulfillment changes later due to how costing is configured in NetSuite.
This can cause a mismatch between:
The original transaction’s cost (which has changed), and
The reclass entry, which still reflects the old cost.
To address this, NetAsset can be configured to automatically resync inventory reclass entries with the latest cost values. This eliminates the need for manual review and adjustment, ensuring accuracy in cost reporting.
Key Assumptions
Inventory reclasses are generated based on source transactions (e.g., Item Fulfillments).
NetSuite costing configuration allows for post-transaction cost updates.
The automation script will only update reclass entries under specific conditions (see Limitations/Things to Be Aware Of).
Prerequisites
NetAsset is installed and properly configured in your NetSuite environment.
You have the necessary permissions to create and schedule Map/Reduce script deployments.
An existing Inventory Reclass Rule is in place to define which transactions should be monitored for cost changes.
Step-by-Step Process
1. Create a NetAsset – Automation MR Deployment
Navigate to Customization > Scripting > Script Deployments.
Select New Deployment for the NetAsset automation Map/Reduce script.
Assign a deployment title (e.g., "Inventory Reclass Cost Resync").
Set the status to Scheduled.
2. Schedule the Deployment
From the deployment record, go to the Scheduling subtab.
Set the frequency according to how often costing updates occur in your environment (e.g., daily, weekly).
Ensure the schedule allows for timely updates without creating unnecessary processing load.
Toggle to the Parameters subtab and set the "Resync Automation Rule" to Inventory Reclass.
Save the record.
How It Works
Once scheduled, the script will:
Review inventory reclass entries at each interval.
Compare the stored cost values with the latest GL cost data from the source transactions.
Update reclass entries with the correct cost values if applicable.
Limitations/Things to Be Aware Of
The automated resync only applies to reclass entries that:
Do not already have an asset tagged, and/or
Are in an open accounting period.
If either condition is not met, the reclass entry remains unchanged.
Scheduling frequency should balance processing efficiency with the need for up-to-date cost information.
Troubleshooting
Issue | Possible Cause | Resolution |
---|---|---|
Reclass entry did not update | Asset is already tagged or period is closed | Review entry conditions; update manually if needed |
Script not running | Deployment not scheduled or inactive | Verify deployment status and schedule |
Costs still mismatched after resync | Cost changes occurred after the last script run | Run script manually or adjust schedule for more frequent runs |