Now, we NetSuite...

Build Difficulty: 💗💗 This one is for when you like to get only the posting lines that are created or approved within the x amount of days as specified.  These will be in the GL accounts and you should not be seeing any sales order, purchase orders, and requisitions.  Also, you should not see any unapproved transactions. TRANSACTION search CRITERIA ( Type is Journal OR Main Line = F ) AND (( System Notes : Field = Posting Period AND System Notes : New Vale is not empty AND System Notes : within 5 days ago and 1 days ago ) OR ( Posting = T AND Date is within 5 days ago and 1 days ago )) RESULTS Internal ID Document ID Date Period Account : Number Type Amount Word of Wisdom In this example the x day is set to 5, obviously you may interchange this as you wish. When posting period is not empty it would imply posting is true. Journals do not have the notion of main lines.  In fact, if you try to look for main line in journals you will see return of null value (this is also a ...

Build Difficulty: 💗 This one is for when you would like to find out the last successful login of a full licensed user.  If a full licensed user have not login for a while, you can probably take them out to repurpose it for another user.  This also helps so you do not have to purchase additional user subscriptions. EMPLOYEE search CRITERIA Login Audit Trail : Status = Success Role : Center Type != Employee Center RESULTS Name (Group) Login Audit Trail : Date (Maximum) Role (Count) Word of Wisdom The performance of this can get slow when you get a larger set of data, in particular, large amount of users with frequent usage (in such case, you might want to consider filtering the audit dates).  Note that this search accounted for how many full licensed roles the user currently have.  It is when the administrator removes all full licensed roles then the provision is released back.

Build Difficulty: 💗 This one is for when you would like to find out the last successful login of an employee center licensed user (also refer here as an employee user).  If an employee user have not login for a while, you can probably take them out to repurpose it for another user.  This also helps so you do not have to purchase additional user subscriptions. EMPLOYEE search CRITERIA Login Audit Trail : Status = Success Role : Center Type = Employee Center RESULTS Name (Group) Login Audit Trail : Date (Maximum) Role (Count) Word of Wisdom The performance of this can get slow when you get a larger set of data, in particular, large amount of users with frequent usage (in such case, you might want to consider filtering the audit dates).  Note that this search accounted for how many employee licensed roles the user currently have.  It is when the administrator removes all those roles then the provision is released back.

P2P (Procure to Pay) is the blueprint of how a company conduct the entire supply chain process.  This is a business process that describes the mechanism and the obligation of the company in order to complete the transaction.  This touches the Account Payable portion of the business which impacts expense.  Aside from the sales process, this is another area where you can expect the company generate a lot of its data in NetSuite.  The design of P2P process in NetSuite look like this... Purchase Order For a lot of companies, it starts out with a Purchase Order (to get to a new PO you can global search 'Enter Purchase Order').  A Purchase Order record is a non-posing transaction in NetSuite and there are a few key data points that you will need.  The subsidiary is the first key entry as you can have more than one company doing business through NetSuite.  The vendor you are getting the supply from will be required.  Of course, there is the items that yo...

Search can get bored, but when you found something meaningful, it gets exciting.  Data is growing in your NetSuite by the day, it will be useful only if you can extract out of it and put them in a way that is useful.  NetSuite provides many ways to consume data, and one powerful tool is called the Saved Search. In case you haven't notice, when you look at transaction record in NetSuite (it can be Sales Order, Item Fulfillment, Return Authorization, Purchase Order, Invoice, etc) you should see that there is a notion of a header level then a sub list (line) level data point.  This is important when you are creating saved searches, or any search.  A tip in creating saved searches is to keep a record type open in a new tab so you can reference the data point as you are setting it up. My prefer way of starting out a new saved search is global search 'new saved search'.  I usually tell users that one of the ways you can think of saved search is that you are working wi...