Importing the Excel File for Bulk Creating BP Records

Each Excel file (.xlsx or .xlsm) for import must not exceed 100,000 rows of record and line-item data, including the header and blank rows. It is recommended to use Excel import to create thousands of records in bulk across projects. It is a scheduled high-priority background job and the job can be processed based on other background jobs in queue. Ensure you do not use this import process to update existing records. A maximum of 100,000 rows (including headers and blank rows) can be included in the imported file.

For General Spends BP, import General Spends records using a predefined General Spends Import Template. Ensure the following fields are completed for each record:

  • Main Form Worksheet: Shell Number and Record Sequence No. in the Main Form worksheet
  • Line Item tab worksheet: Required fields like Ref No., Cost Code, and CBS Code

After Creating the Excel File for Bulk Creating BP Records across projects/shells, import the Excel file to add the new BP records in Unifier as follows:

  1. Select the Home ("") tab, and switch to User mode.
  2. In the left Navigator:
    1. Select Master Log - Business Processes.
    2. Select the specific business process where the BP records are to be imported. For example, select the Warranty business process.

      The Allow Bulk Creation permission, although visible for all BPs, is supported for only:

      • Simple BPs such as Action items, Project Note, and Field Observations
      • Generic Line Item BPs such as Daily Reports, Warranty
      • Generic Cost BPs (Line item with CBS Code, Line item with Fund Code, Line item with CBS and Fund Code, and Line item with CBS and WBS Code)
      • Transfer Cost BPs ( Line item with CBS Code, Line item with Fund Code, Line item with CBS and Fund Code, and Line item with CBS and WBS Code)
      • Base Commit (Line item with CBS Code - Create SOV of General Spends and Payment Applications)
      • Change Commit BPs (Line item with CBS Code - Update SOV of General Spends and Payment Applications)
      • General Spends (Invoices)
  3. In the right pane:
    1. From the toolbar, select Actions, and then select Import.
    2. In the Import Records drawer, drag and drop the saved Excel file, and select Import.
    • To avoid data format validation issues, the logged-in user's preferences are used instead of the auto-creation user's preferences.
    • Business process (BP) records will be created using the Creation Form of the workflow selected in the BP Setup of each project/shell instead of the Integration Form.
    • Required fields in the downloaded template file are determined by the Integration Validation Form.
  4. To review status of the imported data, perform any of the following actions:
    • In the displayed message, select View Import History.
    • From the toolbar, select Actions, and then select View Import History.
    • In the email notification you receive, select the link.
    • RAP
    • Autocreate
    • Cashflow commit
    • Roll up to SOV Sheet
    • Roll up to Cost Sheet
    • Validate remaining balance if formula defined in SOV sheet.

File Validations

When the import is initiated, the file is checked for the following:

  • If the Excel file has the same column structure as defined in the Integration tab in Main Form or Line Item worksheets
  • If the Shell Number and Record Sequence No. columns have been removed, renamed, reordered, or duplicated in the Main Form tab
  • If the Shell Number, Record Sequence No., and Line No. columns have been removed, renamed, reordered, or duplicated in the Line Item tabs
  • Duplicate rows in the Main Form tab with the same Shell Number and Record Sequence No.
  • If the Record Sequence No. is a non-integer or a random string

Data Validations

When the import is initiated, the data is checked for the following:

  • If the Business Process, Integration settings, or default workflow are not set up in the specified project/shell
  • If the Shell Number is not valid in the Main Form tab.
  • If the project/shell numbers specified in the Line Item tabs do not exist in the Main Form tab
  • If the project/shell numbers are not valid in the Line Item tabs
  • If project/shell numbers with Inactive, View-only, or On-hold statuses are specified
  • If required fields have been specified
  • If invalid values have been specified for data elements
  • If form validation rules are satisfied
  • If dynamic data set behavior data elements are updated via import data and behavior element is read-only based on master value
  • If provided, the BP Picker value meets the configured query conditions