Olivier Gagnon NC Red Ribbon

Ah, yes, I see. Well, you should be able to achieve traceability via some saved searches. Basically, the Assembly Build transaction has all the info you need. Doing a transaction search, you should be able to create a search to tell you the SN of the top-level assembly, as well as the consumed SN of the sub-assemblies.…

Sorry, that was hard to follow. What is the problem exactly? Is it that Serial Number do not allow a quantity other than 1?

Technically speaking, it's the Department on the Assembly Build Transaction, which may in fact be different than the department on the Assembly item itself. In any case, it's how it is, the 'why' doesn't matter much. You can file an Enhancement Request (there might be one already, since it makes sense). Plan B would be to…

Mhm... I think this fits the same mold as we've seen for all other scrap production. You build normally, and then "declare" how much scrap there is and then bring it inot existance using an Inventory Adjustment. Build 10 pounds Sell 7 pounds 1 pound is lost, use Inv Adjust to destroy it 2 pounds are transformed into scrap.…

Well, when you destroy the 2 pounds of cheese via inv adjustment, or that one pound of loss, you can hit COGS via the Adjustment. And, when generating the trim, you could even *undo* the COGS hit from the cheese destruction, so that the COGS then comes from the sale of the trim (both trim and cheese would use the same COGS…

Hmm. Good one. What about making an Item Group composed of the cheese and the rim? I actually have no idea how NS would react to that. I think it would make you do 2 separate Work Orders/Assembly Builds, as the group would basically "explode" into 2 lines on the order. Would that work? Plan B, the only thing I can really…

That would require a script, yes. You can get a Scheduled Script that runs at whatever frequency (monthly?), identifies any item whose quantity is smaller than your threshold, and automatically adjusts it out. Pretty straightforward.

There is no "replace" mechanism. A CSV update is probably the fastest way, though for 15 items doing it manually is feasible too.

Right... ok, let me go over the accounting slowly with you - Let's say cheese costs 10$ to make. The rim is costs 2$ to make. The cheese thus has an Inventory Asset (and subsequent COGS) of 12$. Now... you basically cut off the rim from the cheese and sell it seperatly, right. So you sell the cheese 15$, and you want an…

Hi, Please check out the documentation under Items and Inventory Management : Inventory Management : Transferring Inventory : Entering a Transfer Order, and specifically for the Transfer price of items you can read this section: Items and Inventory Management : Inventory Management : Transferring Inventory : Transfer Order…

Make them use reports and searches showing inventory levels rather than opening the item?

I would never, ever do this. If it was that easy, NS would offer the ability to do it. My guess is your accounting will be left in a dangerously unstable condition. I don't have any smoking gun proof, this is based on nothing but intuition, but I would not do that.

One simple solution, especially when talking about schematics, is to create a Custom Item Field of type Document.

Most scripts are not form-dependant though. Only client-side scripts attached to forms work that way, and that is only one of several ways to deploy scripts.

Yeah, Inventory Item is the easiest way to go. You can disable the script for just 1 item by editing the code and introducing an if() statment that check for that

Yeah, bins will do that. We often see this. Try calling NS Support. Often this can't be fixed using the tools at your disposal, NS Support has to get involved.

I don't know the answer to that, sorry. Never tried.

/****************************************************************************** * Type: ON SAVE * Name: onSave * Sets field istaxable to true for inventory item * *************************************************************************/ function onSave() { nlapiSetFieldValue('istaxable', 'T' , true); // alert("Set field…

Depends on your settings. Under Setup->Accounting->Accounting Preferences->Order Management, you have the "Fulfill Based on Commitment" dropdown. If this is set to "Limit to Committed", you would HAVE to manually allocate lines before being able to fulfill. For the other 2 settings, you wouldn't. Then again, the other 2…

var DO_NOT_COMMIT_VALUE = 3; orderrec.nlapiSetLineItemValue('item','commitinventory',x,DO_NOT_COMMIT_VALUE);

You may find helpful the training videos Netsuite hosts on the SuiteAnswers page. To access these, go to the Support and click on the SuiteAnswers link. Then, run a search on "Standard cost". You can then filter to see only videos, and review those, or you can of course review any and all of the material returned. This…

If your assemblies are 1 level deep (i.e. you do not have assemblies that have other assemblies as members), then you can pull this information from an Item Search, just use the Member Item, Member Quantity and a join on Member Item... to pull costing information.

Items are that used in Drop Ship do not cause Inventory Asset impacts, if that helps.

Aside from the Enhancement Request, something could be achieved with customization. You would enter the Adjustment into Custom Records, and when those are approved, a script would transform the custom record into a real Inventory Adjustment. There would be some loss of functionality though - it would be very difficult for…

There is an option on Assemblies to allow Purchasing of that assembly. When you BUILD the Serialized Assembly, you must specify the serial number of all components that are serialized themselves, then specify a serial number for the finished assembly. If you purchase the Assembly directly, you must give it a serial number,…

Er... I do not believe you can add custom columns to an Inventory Adjustment...

Sorry Chris, you're going to have to recreate your items :( You can sill keep the same part number, just rename all your old items to [whatever]-old. This will free up the [whatever] part and you can name your new items with the original name.

Trust me, you can't just flip it.

Mhm. So basically, it's a variable-component Assembly. Netsuite does not support these. I would envision a Non-Inventory item with Item Options that the customer buys, and then a script that, behind the scenes, uses Inventory Adjustments to "consume" the actual inventoried parts that make up the book.

What do you intend by "custom order"? And by options, are you talking about the Netsuite line item Option concept?