Dear Experts, We have a substantial number of item...
# general
s
Dear Experts, We have a substantial number of item demand plans in our NetSuite, totaling over 310. Currently, I'm attempting to upload plans for new items, but I've encountered an error stating "Invalid item reference key xxxxx-x for subsidiary 29." I've received advice suggesting that I delete all existing item plans before uploading the new ones. If this is indeed the recommended course of action, could you please provide guidance on the most efficient method to delete all existing plans simultaneously? Thank you for your assistance.
m
I’m not sure why you would need to delete demand plans. The error is expressing an item subsidiary conflict. Check item xxxxxx-x and make sure it is available to the subsidiary with ID 29 Also make sure that item has not been inactivated
You can also use our free mass delete record tool if you want to delete them https://www.mavencloud.tech/mavencloudtools
s
@MGBC Thank you for your prompt response, I have tried all the possibilities and finally I have end up with this NetSuite answer.
m
I see. Yes maybe export a list of existing demand plans and update them then reimport instead of trying to create new
Or try to delete using inline edit of a saved search. I don’t remember if demand plans support inline editing but if it does you can mass delete them via saved search as well
r
I strongly recommend utilizing the internal ID of the items. This eliminates any challenges of having to utilize a concatenated version of the item name and description if that configuration is on or any typos. We haven't had a single issue on item imports utilizing item IDs and the end users do multiple re-uploads a month. I would recommend against deleting the records as you lose historical plan vs actual reporting. For your upload utilize the existing internal ID of the demand plan record and internal ID of the item. Run the upload as an update.
s
Hi @Rich Keller, Thank you for your valuable information. I will continue to follow your points. If you could review the attached screen, I have followed the method you mentioned earlier. However, the issue persists, particularly with the Subsidiary Internal ID, which remains unchanged. In this case, I am encountering the error message "Invalid item reference key 4664 for subsidiary 46
Later, I discovered that the issue arises from insufficient availability of items in the specific location. Is there a way to keep the location open? I'm uncertain about future allocations for planning purposes.