Robert Nedelkow-Oracle · Oracle NetSuite Community Manager · Admin

Hi Steven, the Support case indicates the problem was resolved. Please re-open the case if you continue to experience this issue.

Both IP Addresses 167.216.129.171 and 167.216.129.170 are no longer listed in the CBL. 167.216.129.170 was removed at 2014-12-06 22:42 GMT and 167.216.129.171 was removed at 2014-12-06 20:19 GMT.

Support has confirmed FedEx rates are being calculated successfully now. If you continue to experience this problem, please contact Support and reference Defect 319458.

Support has filed the following Defect: 319458 FedEx Shipping Item > Enter Sales Order > Compute Shipping Cost > Cannot Compute Shipping Cost > Error Cannot calculate cost for the selected Realtime rate. The rate for this service is not available for the specific source and destination address.

FedEx WebService is currently experiencing an issue with calculated shipping cost. No eta is available at this time. Please visit fedex.com for shipping calculations as we investigate this further.

FedEx reports this issue has been resolved.

This may be a caching issue. Try clearing cache and re-loading the page.

I use Chrome 39.0.2171.71 m almost exclusively and haven't seen this before. Have you tried clearing cache, close and restart Chrome?

System Operations should be back to normal. More information will be posted on status.netsuite.com as it becomes available.

Some accounts are affected and Support has filed Defect 316528 to track this.

Defect 316502 is being investigated with highest severity and Support will provide an eta once it becomes available.

We have filed Defect 316502: Create/Edit Purchase Order > Ship To Address is deleted after saving. Please contact Support to have your case attached if you experience this issue.

We are currently experiencing a technical problem affecting SuiteAnswers and our case management system. Some accounts may also be affected. Please visit status.netsuite.com for updates. Note that you may not be able to browse SuiteAnswers or submit cases until this is resolved.

status.netsuite.com was updated during this time: [ATTACH=CONFIG]n316110[/ATTACH]

Chris, please update your case and Support will update the related defect.

Defect 315656 was filed for Customers > Sales > Fulfill Orders > Click on List > An unexpected error. Please submit a Support case to determine of your issue is related. The alternate solution is to use this URL:…

All System Operations are back to normal now. Please try logging in.

This should be doable but existing 10 digit PO's may remain the same length. A couple of SuiteAnswers worth taking a look at: Answer ID 9821 and 38158. You can access SuiteAnswers under the Support tab of your NetSuite account.

Fix eta is 4:30 EST for Defects 315602 and 315701.

Hi Charlotte, this forum is not role dependent. Once your application is approved, you should be able to log in using this page: https://usergroup.netsuite.com/users/. Does this happen in all browsers?

Some customers experienced intermittent issues saving some records. Our monitoring detected the issue and addressed the problem. Please see status.netsuite.com for details.

All Systems Operations should be back to normal now.

This issue should now be resolved.

Some accounts continue to experience this issue after clearing cache. QA is investigating with highest priority.

The fix should be complete now. Please try clearing cache and processing an order to confirm.

This should be resolved now and status.netsuite.com has been updated.

We are tracking this in Defect 316092 Slow Performance in NetSuite. Some accounts are affected and more information will be posted on the status.netsuite.com page as it becomes available.Please contact Support to have your case attached and you will be notified once it has been resolved.

The fix is currently being rolled out. An update will be provided once completed.

Defect 315701 was filed for Fulfill/Edit/Approve Sales Order > Unexpected Error. For anyone still experiencing this issue, please have your case attached. 

Hi Paul, there could be several reasons why the field doesn't show up. i.e. The custom field must be displayed on the preferred form in order for the field to be available on the mass update. See SuiteAnswers Answer Id: 12283 for details.