Importing the Excel File for Bulk Creating BP Records

Each Excel file (.xlsx or .xlsm) that you import must not exceed 100,000 rows of record and line item data, including header and blank rows. Use this import process to create thousands of records across projects/shells. This process runs as a scheduled high-priority background job, and the system processes it based on other jobs in the queue. Do not use this import process to update existing records.

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

• Main Form worksheet: Shell Number and Record Sequence No.
• Line Items worksheet: Required fields such as Ref No., Cost Code, and CBS Code

After you create the Excel file for bulk creating BP records across projects/shells (see Creating the Excel File for Bulk Creating BP Records), 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, select Master Log - Business Processes, and then select the specific BP type where you want to import the BP records.

   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 and Warranty
   • Generic Cost BPs, including 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, including 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, including Line item with CBS Code - Create SOV of General Spends and Payment Applications
   • Change Commit BPs, including Line item with CBS Code - Update SOV of General Spends and Payment Applications
   • General Spends, including Invoices
3. From the toolbar, select Actions, and then select Import.
4. In the Import Records drawer, drag and drop the saved Excel file, and select Import.
   To avoid data format validation issues, the system uses the signed-in user's preferences instead of the auto-creation user's preferences.
   The system creates BP records by using the Creation Form of the workflow selected in the BP Setup for each project/shell instead of the Integration Form.
   The required fields in the downloaded template file are determined by the Integration Validation Form.
5. To review status of the imported data, do any of the following:
   • 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.

File Validations

When the import starts, the system checks the following items:

• The Excel file matches the column structure defined in the Integration tab for the Main Form or Line Items worksheets.
• The Shell Number and Record Sequence No. columns in the Main Form worksheet are present and are not removed, renamed, reordered, or duplicated.
• The Shell Number, Record Sequence No., and Line No. columns in the Line Items worksheets are present and are not removed, renamed, reordered, or duplicated.
• The Main Form worksheet does not contain duplicate rows with the same Shell Number and Record Sequence No..
• The Record Sequence No. value is an integer.

Data Validations

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

• The BP, Integration settings, and default workflow are set up in the specified project/shell.
• The Shell Number in the Main Form worksheet is valid.
• The project/shell numbers specified in the Line Items worksheets exist in the Main Form worksheet.
• The project/shell numbers in the Line Items worksheets are valid.
• The project/shell numbers do not have Inactive, View-only, or On-hold status.
• The required fields are specified.
• The data element (DE) values are valid.
• The form validation rules are satisfied.
• Dynamic data set behavior DEs are updated through imported data, and the behavior element is read-only based on the master value.
• If provided, the BP Picker value meets the configured query conditions.