The logic described below is implemented in two separate modules - NetSuiteInventory and NetSuiteInventoryMultiManagement.

NetSuiteInventoryMultiManagement extends NetSuiteInventory. NetSuiteInventoryMultiManagement is not compatible with NetSuiteInventorySingleManagement!

The inventory Import process is the only workflow that works outside the workflows defined Import process page. Because Inventory is not an Entity/Record in NetSuite it can't be used the same way. Because the Inventory module (RocketWeb_NetSuiteInventory) is a separate module, we need to start with the cron execution first. The netsuite:cron command gets a plugin \RocketWeb\NetSuiteInventory\Plugin\NetSuiteCronPlugin::afterProcessMode() which actually runs the Stock processor! Once the process() is called in the plugin, the rest of the execution happens similar to the other workflows.

Execution

As mentioned, the \RocketWeb\NetSuiteInventory\Model\Process\Import\Stock::process() is the entry point of all workflows. The Stock module has its own validations (isEnabled() and isFeatureEnabled()). Once those are passed, we fetch the current NetSuite server time. The server time is then used to compare (\RocketWeb\NetSuiteInventory\Model\Config\StockConfig.php::shouldRun()) if Stock Update should be executed or not.

Process Saved Searches

As mentioned before, Inventory is not an Entity or Record in NetSuite. It is part of Item data. Since we don't want to pull all Item data to receive Inventory, we implemented a lighter and faster solution. It's using NetSuite SavedSearch which allows flexibility & filtration of data on the NetSuite side so Inventory logic can be easily changed if needed. The output of those SavedSearches is predefined. In code (\RocketWeb\NetSuiteInventory\Model\NetSuiteInventoryRepository::processInventoryUpdates()) we fetch the Custom SavedSearch IDs and run each of them in a foreach loop.

Fetch SavedSearch

Inside the loop, we fetch the SavedSearch data (\ RocketWeb\NetSuiteInventoryMultiManagement\Model\NetSuiteInventoryRepository\StockDataTransformation:processSavedSearch()). The SavedSearch response is then transformed to the proper format (\RocketWeb\NetSuiteInventoryMultiManagement\Model\NetSuiteInventoryRepository\StockDataTransformation::transformNetSuiteSearchResponse()). The implementation is different from the same step in Inventory Single Management (2024.2 Single Management) due to the filtering stock data by location (\RocketWeb\NetSuiteInventoryMultiManagement\Model\NetSuiteInventoryRepository\StockDataTransformation::prepareMultiInventoryUpdate()).

Save Updated Stock

Once all the data from all SavedSearches are prepared, the stock data is saved per Source in \RocketWeb\NetSuiteInventoryMultiManagement\Model\MultiStockRepository::saveInventoryData().

Browser not supported