NetAsset - Mass Build Ups

Overview

The Build Up feature in NetAsset allows users to add transaction costs — such as vendor bills and journal entries — to existing assets that have already been created. This is commonly used when costs are incurred against an asset over time and must be capitalized after initial creation. NetAsset supports mass Build Up operations, meaning multiple transactions can be mapped to multiple assets and submitted as a single batch job.

This article explains how mass Build Up works, how to pre-tag transactions via CSV import to streamline the process, and what Global Settings govern the feature's behavior.

Key Assumptions

  • The assets receiving the Build Up exist in NetAsset and are in an eligible status: Pending, Ready to Capitalize, Capitalized, In-Service, Fully Depreciated, or On Hold.
  • The transactions to be built up are coded to the appropriate clearing or Construction In Progress (CIP) account configured on the relevant Asset Type.
  • Users have the necessary NetSuite role permissions to access the Build Up page and perform CSV imports on transaction records.

Step-by-Step Process

Option A: Manual Assignment on the Build Up Page

  1. Navigate to NetAsset > Update or Modify Assets > Build Up from Clearing (or Build Up from CIP, as applicable).
  2. Use the Transaction Filters section to narrow results by Subsidiary, Vendor, Accounting Period, Date Range, Project, Transaction Type, Asset Type, or other available criteria.
  3. Click Filter to populate the Transactions sublist with eligible transaction lines.
  4. For each transaction line, select the target asset in the Asset To Build Up column. Multiple lines may be assigned to different assets in the same session.
  5. Check the Select checkbox for each line to include in the batch, or use the Mark All button to select all displayed lines.
  6. Click Build Up Asset to submit the batch. The system initiates an asynchronous Map/Reduce job to process all selected build ups.
  7. The page redirects to a landing page displaying the job status. Refresh periodically until the status advances from PENDING to PROCESSING to COMPLETE.

Option B: Pre-Tagging Transactions via CSV Import (Recommended for High Volume)

For large-volume scenarios — for example, mapping 1,000 vendor bills across 100 assets — manually assigning each line in the Build Up page is time-consuming. The recommended approach is to pre-populate the NetAsset Asset To Build Up field (custcol_fa_build_up_asset) directly on the transaction lines using a NetSuite CSV import, then use the Build Up page's filter to locate and submit those pre-tagged lines.

  1. Prepare a CSV file with the transaction line identifiers and the corresponding NetAsset asset internal IDs. The relevant transaction line field to populate is NetAsset Asset To Build Up (custcol_fa_build_up_asset).
  2. Perform a CSV import in NetSuite to update the applicable transaction records (e.g., Vendor Bills, Journals) with the appropriate asset IDs in the NetAsset Asset To Build Up field on each line. Navigate to Setup > Import/Export > Import CSV Records to complete this step.
  3. Once the import is complete, navigate to NetAsset > Update or Modify Assets  > Build Up from Clearing (or Build Up from CIP).
  4. In the Transaction Filters section, check the Asset To Build Up Pre-Determined checkbox. This filters the sublist to display only transaction lines where the NetAsset Asset To Build Up field has already been populated. The asset assignments are pre-read from the field and auto-mapped in the sublist.
  5. Review the pre-populated assignments in the sublist. Select all applicable lines using Mark All or individually check each line.
  6. Click Build Up Asset to submit the batch job.
  7. Monitor the landing page status until the job reaches COMPLETE.

Considerations

  • There is no native CSV upload mechanism within the Build Up page itself. The CSV import approach described in Option B operates through NetSuite's standard Import/Export functionality, stamping the custcol_fa_build_up_asset field on transaction lines prior to using the Build Up page.
  • The Build Up page processes submissions asynchronously via a Map/Reduce job. Large batches may take additional time to complete. The status can be monitored on the landing page after submission.
  • When accessing Build Up from an individual asset record, the Asset To Build Up column is pre-populated and hidden. The page automatically restricts displayed transactions to those relevant to that asset.

Limitations/Callouts

  • Assets with a status of Disposed, Split, Merged, Expensed, or Ready to Expense are not eligible for Build Up. Attempting to build up such an asset will display an error on the Build Up page.
Was this article helpful?

Knowledge Center