My Stuff
Comments
-
I have a similar custom field called 'Qty Open', I have multiple Saved Searches that use this field in criteria. I just double checked and it works. Transaction Column Field Label: Qty Open Store Value = F Default Value: {quantity} - NVL({quantityshiprecv},0) Formula = T Display Type = Hidden
-
Create a hidden field for Sales Orders, call the field 'Quantity Unavailable'. Uncheck 'Store Value', set to 'Formula', and enter your formula in the field. The formula should be something like this [INDENT]Case when {quantity} - {item.quantityavailable} < 0 then 0 else {quantity} - {item.quantityavailable} end[/INDENT]…
-
This is possible with Advanced PDF/HTML layout. We just had our NS Reseller build out a full BOM and Work Order form. [ATTACH=CONFIG]n365098[/ATTACH]
-
This is possible with Advanced PDF/HTML layout. We just had our NS Reseller build out a full BOM and Work Order form. [ATTACH=CONFIG]temp_608_1434559107128_600[/ATTACH]
-
My experience tells me that if you can inactivate them, it's much easier, cleaner and safer. Deleting should only be done when you want to remove (almost) any traces that it ever existed. A good example of record to delete is a test sales order used to debug a script or workflow.
-
You could do it with a saved search, script, or export. If I was to pick the quickest it would be a saved search in this format: Criteria: Transaction Type: sales order Related transaction type: quote Formula numeric: case when {field} = {theothertransaction.field} then 1 else 0 end ...
-
A beforesubmit or aftersubmit user event script would be your best bet. function inactivated(type) { if (type != 'delete') { var inactive = nlapiGetFieldValue('isinactive'); if (inactive == 'T') { custom code } } }
-
We had this problem and it took a while for NS to clean it up. Issue Number 201546 Type Defect Severity S2 - Issue Status Closed - Released Release Target Case 1789638 Defect: 201546 Billed Sales Order still shows Quantity Committed
-
You could create a copy (standalone) invoice and remove the items from it. Then set its status to closed. The original invoice would get payments applied to it but the copy would get sent to the customer. With creative scripting you could get this to work, fully automated.
-
You could script it so that when a receipt is created, the corresponding bill is created. Based on your comments, it sounds like someone has to review the bill for accuracy, so then the script would set the status of the Bill field 'Approval Status' to 'Pending Approval'. With a workflow or saved search, the right person…
-
Go to the SuiteScript Records Browser and choose the record type. Section headings for each record are : [LIST] [*]Fields [*]Tabs [*]Sublists [*]Search Joins [*]Search Filters [*]Search Columns [*]Transform Types [/LIST] Available search fields for scripts are shown in the 'Search Filters' section. I believe that these are…
-
It looks like {assemblyitem} is a valid field on the record, but is not exposed to searches. If that's the case, then add a custom field and set its value as a formula {assemblyitem}. Make sure you uncheck "store value" I haven't tested it but I think that will work.
-
Yeah maybe that's why. Did you try changing it to 'store value'?
-
Yes, read this: https://system.netsuite.com/help/helpcenter/en_US/Output/Help/Accounting/GeneralAccounting/UsingCurrencyExchangeRateIntegrationFeature.html?NS_VER=2013.2.0 and this: http://corporate.morningstar.com/US/asp/subject.aspx?xmlfile=6694.xml
-
You can get this kind of value thru scripting, as long as the raw data are available in NS. I use scripting to calculate all kinds of historical and forecasted values, and place those values in custom fields.
-
Script is the best way to do this. Would be pretty short script, depending on how it's set up. I would do it like this: when the customer is selected, run a saved search and store in array. Then as line items are added, pull pricing from that array. This would give the best user performance.
-
Try an Inventory Adjustment, and apply it to the account for your shop supplies.
-
Pieces A and B could be non-inventory. Or you could create a new location (at supplier) that lets you manage inventory of those pieces.
-
Another way to fix it is to turn off bins for the item, make inventory adjustment, then turn bins back on.
-
this should work make adjustment (qty reduction for inv and bins) turn off bins make offsetting adjustment adjustment (qty increase for inv) turn on bins
-
What about Kits? Those are available online I believe.
-
try creating a search, with a result formula CASE statement, something like (in pseudo code) CASE WHEN type = cheque THEN entity line name WHEN type = journal THEN entity name ELSE '' END See this thread for CASE examples https://usergroup.netsuite.com/users/showthread.php?t=5889&highlight=ways+formuals
-
A very simple script would do it. Client side you could do it on pageinit.
-
Has the invoice been paid? If not, I would delete the invoice too, and then when you recreate the fulfillment and invoice, you can overwrite the new invoice number with the old invoice number (if you have that feature enabled on the invoice record).
-
If it's from a closed Accounting Period, you would have to reopen the period first.
-
Setup>Accounting Preferences>Order Management>Transfer Orders>Use Item Cost as Transfer Cost Do you have it checked or unchecked?
-
I've verified that the Fulfillment was created from a Transfer Order. According to NS support, this may be due to an accounting setting 'Use Item Cost as Transfer Cost' Setup>Accounting Preferences>Order Management>Transfer Orders>Use Item Cost as Transfer Cost The help for this field is a little confusing (and misworded)…
-
We use FIFO.
-
OK thank you pfung for the response. I am now assuming this is a defect on my NS instance since my fulfillment posted as follows - Inventory Asset CR - Income Account DR Support Case #: 1525403