Book Image

NetSuite ERP for Administrators

By : Anthony Bickof
Book Image

NetSuite ERP for Administrators

By: Anthony Bickof

Overview of this book

NetSuite ERP is a complete, scalable cloud ERP solution targeted at fast-growing, mid-sized businesses and large enterprises. It's the smartly executed combination of financial management operations and built-in business intelligence, which enables companies to make data-driven and well-informed decisions. This book will help administrators become expert enough to be seen as the NetSuite leader at their company and to be able to advise department heads on specific processes, and strategic decisions. We start with an overview of ERP and NetSuite ERP, before going on to explain the built-in features to show the breadth of NetSuite ERP's product and its ease of use. We then discuss business aspects, focusing on the most important processes in NetSuite. Then you'll understand the implementation aspects that are generic enough to cover all the features. The focus then shifts to specific skills that you will need to administer for any system, such as roles, permissions, customization, and data imports. Moving on, you'll learn how to centralize the creation of search templates and give users the tools to pivot the data and expose it to the user in useful ways, such as on the dashboard. The book ends with checklists providing actionable steps that you as an administrator can take to do your job and support the application through new releases and troubleshooting problems.
Table of Contents (21 chapters)
Title Page
Copyright and Credits
Dedication
Contributors
Packt Upsell
Preface
Index

Employee and transaction fields use case


In this use case, we will add a new field to sales orders to display the name of the solution architect who helped close this deal.

Go to a sales order and click the Customize button. We are faced with a few choices for transaction fields. We will select transaction body field, as the solution architect worked on the entire deal (unlike transaction column field, which would be used if different architects worked on different items sold in the same transaction):

  1. Name the new field by entering Solution Architect into the Label field.
  2. Enter _hmsolarc into the ID field.
  3. There is no need for the name of the solution architect be typed onto each transaction. We will set the Type to list in order to select from a list of values instead.
  1. The List/ Record becomes available once the type is changed to list. We can add a list of solution architects by clicking the plus sign next to the list/record field, however, this would require us to maintain this separate list...