My Stuff
Comments
-
Lot Number is a column you can add to SOs. Just customize your form and add it if it is not there.
-
What are you looking for, a report? I think you could probably do that. Note that while you can currently allocate stock to orders in whatever priority you chose, this is a manual process, there is no way to automate it. So while you could build a search that displays the priority or oders, you will need to take manual…
-
Right, Order Item logic can be very complicated, especially if you use auto-calculated reorder point and/or preferred stock levels, and if you use the fancier options like seasonal change, etc. The problem is that these calculations are sort of done specifically for the Order Item screen. The "quantity to order" is not…
-
The downside of different item records is you lose historical precision. Becomes harder to see the item's popularity, values at a glance, etc. You also have to name them all differently. It wouldn't be terrible to use different item records, but Price Levels would work prefectly well here, so I'd go with that.
-
If the user selected his lanmguage during Registration, you could use a script to assign him a certain Price Level based on country. Again, this requires the usage of many Price Levels, but it's just about the only way to proceed. Web Store prices are governed by currency and Price Levels. It would be difficult to do…
-
Right, you want to make sure the Receipt especially has the correct value for 2 reasons - A) this is from where COGS will be taken from, and B) otherwise you will accumulate value in "Inventory Received Not Billed"
-
You want the sales price to vary based on the location it is sold from? Your best bet would be to create Price Levels for every location. That should work very well. You can then complement that with a small script that automatically sets the price level based on the location to avoid user error.
-
I don't have a script like that handy, but it's pretty easy to code. On a scale of 1 to 10 of complexity, this is probably a 1 (well, for me anyway ;)) For Customer Price levels... a script could, or could not, overwrite the customer's price level. Either way can be coded, it's up to you.
-
Yes there is :) Setup->Accounting->Accounting Preferences, Order Management tab, "Fulfill Based on Commitment", select "Limit to Committed"
-
a. If not, is it possible that a script could handle this function? [INDENT]Certainly you could write a script for the Item Receipt Transaction Form that would make these up for you, but i have heard that the Items Serial Numbers sublist is not scriptable (please correct me if i'm wrong), so i'm not sure how you would find…
-
I recommend following-up with NS Support daily until they solve your problem. This looks like a backend bug I've seen before, and only NS Support can fix it.
-
I have not seen this problem on any of my clients' accounts.
-
You might want to review this post by Evan Goldberg: Inventory changing on it's own Right. Basically, then receive PO's next week and date the receipts a week before the inventory worksheet It will have NO effect on today's inventory values.
-
Olivier, This sounds very interesting. I could not find any info about this new Assembly Cost calculation in the sneak peek documents. Could you please let me know where I can find out more about this? Thanks. They talked about it during Partner 2008.2 Training. I don't have a Beta yet so I haven't tested it out. It's…
-
Hi Mark, You could indeed use a script to drilldown into all the sub components of a given assembly, figure out the total member cost, and then update the item's cost. We have already created a script for other customers that does exactly that, minus the auto-updating of the item's cost field - that last part is a piece of…
-
You could use Unit of Measures instead of kits. Your purchasing UOM is a unit of 1 and you sell using a UOM of 100. Alternatively, you can use the "Minimum Quantity" field and set that to 100. I would actually say that, from what I understand of your problem, using Kits would not be the recommended way to do things anyway.
-
On Sales Orders, there is a column called "Commit", from which you can select "Do Not Commit".
-
You could probably set a small script to automatically set the "Commit" column to "Do Not Commit", since you are correct that this is not a system setting anywhere right now.
-
It is impossible to edit an existing item to change its Costing Method. The Help lists the correct procedure.
-
You have to recreate the item. So, no, you cannot change an existing item in that way. Inactivate the old one and create a new item record.
-
Ahh I see. Yeah, that's not supported by Netsuite. Again, you could code it up with a Suitelet and stuff. You could "fake" an interface where you see many lines for many POs. On save, behind the scenes, the code would still need to create each individual IR. But from a user interface perspective, you could get it to look…
-
Netsuite's approach is that you'll always want to actually go in and tick in the items being received - you'll never want to blind receive everything. I can think of a couple of ways to solve the problem by usign configuration only, but none of them are especially good. If you really wanted to blind receive, I would go…
-
Not exactly answering your question, but more of a general FYI - COGS recalculations are performed overnight, not right away. So when you edit or create something like an inventory adjustment, the numbers you see right away are garbage. The real numbers will be calculated overnight. So don't run any COGS reports right…
-
They will need View rights to every transaction you want them to see on the History tab - SOs, POs, Invoices, Bills, etc.
-
I double checked, and turns out this is NOT possible - I was thinking of Member Quantity (the qty of an item that goes into the creation of the kit)
-
The delayed COGS recalculation only happens when you modify inventory-impacting transactions (Inventory Adjustments being most common) in the PAST. The reason being, if it's in the past, then it's burried under a bunch of transactions, so that means Netsuite has to go and recalculate the COGS on all of those transactions.…
-
Hmm, I just tried this on one of our demo accounts. I created a PO for a Serialized item, received it, then deleted the Receipt. The serial number I had given the item correctly disappeared from the Item's Serial Numbers tab. So I am not sure why it did not do that for you. I advise you to open a Case with Netsuite…
-
It is possible to make a Saved Search to show member items quantities, as long as you do not use sub-kits.
-
What is "call off"? Is that like cancelling your order?
-
Well, I would say redesign your roles to limit transaction access. Is that what you are talking about?