If you choose a partial import of estimates, the system scans the import file and only imports those records that are within the Import From and Import Through dates specified in the Report Conditioning window. The from and through dates are validated against the period (YYYYMM) of the import file.
If you choose the Monthly, Partial, and Accumulate options, only the following estimate types will be imported:
(1) Standard Hours
(2) Hours
(3) Prime
(8) EQP
(9) Units
The numbers in parentheses represent the estimate type codes entered in the import file. All other estimate types will not be imported, assuming the estimate already exists and you are adding to the estimate using the Accumulate option. If there is no existing estimate, any estimate type will be imported.
If the estimate type in the import file is different than the original estimate type, the estimate type in the database will be changed to the estimate type in the import file. The Processing Report displays the message: The estimate type has been changed from 'x' to 'y'.
If the estimate type being imported is Standard Hours, the original estimate must be in standard hours. If the original estimate type is something other than standard hours, the record(s) will be rejected and an error message will be displayed: Estimate Type cannot be changed to/from Standard Hours.
If the estimate type being imported is Hours, Standard Hours or EQP, the resource must be a labor resource or it is ignored and the following message is logged: Estimate Type 'X' cannot be used for Non-Labor Resource 'X'.
If the estimate type being imported is Units, the resource must be a non-labor resource or it is ignored and the following message is logged: Estimate Type 'X' cannot be used for Labor Resource 'X'.
If you choose the Complete option, the imported estimate will replace completely the estimate currently in the database.
If you choose the Partial option, the imported data is restricted to the dates you specify in the Import From and Import Through fields. You can also choose to replace the old values with the new values (Update), or add the new values to the old values (Accumulate).
When you are doing a partial import, you must use the Duplicate Values field to choose replacement of the old values with the new values (Update), or addition of the new values to the old values (Accumulate).
MPM considers records as duplicates if they have the same values for the following fields:
Period
WBS ID
Resource Code
Resource Department
XREF-EST
Overtime
If the import file contains a rate table override value, the override value will be ignored upon import. If the estimate already exists, the rate table saved with the original estimate will be used. If the estimate does not exist, a new estimate will be created using the default rate table in Project Maintenance.
The process for handling changes in burden templates is as follows:
If the import file contains a burden template override value, the override value will be ignored upon import. The estimate will not price against this burden template.
Upon importing of partial estimates, MPM will compare the burdening structure of the saved estimate to what the current burden template (the default template or the overridden burden template) contains. If there is a difference, the entire estimate will be repriced to the new burden structure.
The only time that this situation would exist is if the burden structure has been changed and reprice has not been run. The Processing Report displays the message: The entire estimate has been repriced to the current burden template structure.
If an estimate start date in the import file does not match that of the estimate in the database, the system will display the following message on the Processing Report: Estimate Start date of Import is different than the Estimate Start date of existing Estimate. Estimate Start Date is not updated.
The table that follows outlines the actions MPM takes based on the relationship between the import completion date and the existing estimate completion date.
IF the import completion date is: |
THEN MPM performs the following functions: |
Earlier than the existing estimate completion date |
Updates any existing values contained in the import file (based on the Import From and Through dates). Deletes any value that was in the original estimate later than the completion date contained in the import file. Changes the existing estimate complete date to the imported completion date. |
Later than the existing estimate completion date |
Updates any existing values contained in the import file (based on the Import From and Through dates). Adds new values (if any) from the import file into the existing estimate (based on the Import From and Through dates). Changes the existing estimate complete date to the imported completion date. |
The same as the existing estimate completion date |
Updates any existing values contained in the import file (based on the Import From and Through dates). |
If the monthly value being imported is not within the estimate start/complete dates, it is not imported and the following message is displayed: Month/year outside of Estimate Start/Complete timeframe.
Upon import the system will validate the element of cost (EOC) and class of cost (COC) on the existing estimate to those of the global files. If the EOC or COC on the resource code has changed (in the global files) the import will unroll all the values of the old estimate and reroll the entire estimate (including the new values from the import) to the new EOC/COC.