To perform operations on Netsuite records and objects, it is crucial to understand search functionality provided by Netsuite. Netsuite offers basic and advanced search objects on various record types, and their operations are practically the same.

The search results are either an array if there are more than 1 record returned, or an object if there is only 1 record in its result set. As a programmer, the result set must be examined whether it's an array or an object before performing an operation on them.

There seems to be a number of RHEL packages that support far east Asian language support like Korean, Japanese or Chinese. None of the package description explains how to install them, and configure to work with different languages so here is one method I found working.

1. Before you can install Linux packages on your system, you'll have to login as a 'root' user either by 'su' or 'login' command.

2. Install required Linux packages.

SimpleSAMLphp is an open-source application that implements SAML 2.0 and Shibboleth 1.3 Single Sign-On (SSO). Third party applications that require SSO integration with SAML 2.0 or Shibboleth 1.3 may use SimpleSAMLphp to simplify integration process. SimpleSAMLphp offers an administrative interface to convert SAML meta data, and also provides a link to test and integrate with other Identity Providers and Service Providers. SimpleSAMLphp also offers a programming APIs which makes it easier for 3rd party applications to implement Single Sign On.

Netsuite allows an administrator to add custom fields and custom records via GUI. Custom fields are business specific attributes defined by the company to tailor Netsuite. When a custom field is created in Netsuite, the administrator will assign an ID of the custom field and this ID becomes internal ID of the custom field. To show internal ID on Netsuite GUI, it must be turned on by going to Home -> Set Preferences -> General -> Defaults, and checking "Show Internal IDs" checkbox.

I've had a hell of time today trying to figure out vmware server 2 network bridging problem. The server I've setup more than 2 years ago have been running flawlessly with more than a few reboots over the course of 2 years, and never had network problem in the Guest Operating system running Centos 5.

Netsuite allows you to create a Custom Record to store table of data collected from an external form. For example, you may create an email opt-in form on your external website, and submit the form to Netsuite. The submitted data will be processed by a Suitelet, and stored as a Custom Record in Netsuite. The form must be able to process concurrent users, and hence Suitelet is favored over SuiteTalk (Web Service).

Our business require that we retrieve Quantum View data from UPS, and create or edit ItemFulfillment records with PackageList and Packages. As described in the earlier articles, we've created a UPS developer access key and setup required Quantum View subscriptions for later retrieval of Quantum View events.

Follow the web installation procedure, and if you run into the following errors you'll have to install required php extensions for your Linux version. For Centos 6, here is the steps you can follow to install php-dom and php-mcrypt.

PHP extension "dom" must be loaded.

# yum install php-xml

PHP extension "mcrypt" must be loaded.

UPS Quantum View is one of the most comprehensive reporting APIs available on UPS XML, and yet it's one of the least used API. It provides complete reporting of every shipping activity your organization is engage in. It is a comprehensive suite of services that give you details about your UPS shipments. It can be used to update your ERP with tracking numbers, scheduled and actual delivery dates, and exceptions. The catch is that you'll have to use PackageReferenceNumbers to correlate the package with your sales order number.

I have been tasked to integrate UPS Online Tools with NetSuite ERP using PHP programming language. The job requires retrieving Quantum View reports from UPS on a daily basis, and update NetSuite Sales Orders with retrieved tracking information. By browsing UPS Developer Kit, I am going to be using at least Quantum View API, and Tracking API to do the trick.