Import Fixed Price

Field Header Name

Required/Comments

1

A

Project_Org_Code

ALWAYS REQUIRED.  This code uniquely identifies the Organization to which the project belongs for which you are attempting to import fixed price items.  This value must match an existing Project Organization Code value defined in your system.  If the Organization value you supply does not already exist in the database, the entire record will be rejected.

2

B

Project_Code

ALWAYS REQUIRED.  This project code identifies the project to which this Fixed Price entry belongs.   This value must match an existing Project Code value defined in your system.  If the Project value you supply does not already exist in the database, the entire record will be rejected.

The project or task must have a Billing Type of FP (Fixed Price) in order to import fixed price items.

3

C

Task_Name

CONDITIONALLY REQUIRED.  This field is only necessary if you are attempting to create fixed price entries at the task level.   

This value must match an existing Task Name value in your system for the given project.  If the Task Name you are trying to import does not already exist in the database,  the entire record will be rejected.

If a task is not a top-level task (e.g. it is a sub-task), you must include a comma separated list of each task starting at the top level down.  The following is an example of a valid task tree and how you would reflect each task using this import.

Task Tree Access String

The task must have a Billing Type of FP (Fixed Price) in order to import fixed price items.

See the Excel Tips regarding the use of double quotes and more.

4

D

Description

ALWAYS REQUIRED.  Additional description or comments about this fixed price item.

Maximum Length: 128 characters

5

E

Bill_Date

CONDITIONALLY REQUIRED. This field can be used to specify a date with which a fixed price item becomes eligible to be included in a billing post process.

Whether this date must be provided is dependent on the Bill_On_Completion value.

• If Bill_On_Completion is "N" (or blank as it defaults to "N"), this field is required.
• If Bill_On_Completion is "Y", any value supplied in this field will be ignored (and can be left blank).

Basically, you must either specify that this will be billed upon completion or you must provide the date it will be billed.

Recommended date format:   yyyy-MM-dd   

See Allowable Date Formats for more options.

6

F

Bill_On_Completion

CONDITIONALLY REQUIRED. Valid values include Y or N (if not provided, N is the default for a new entry).   If this value is Y, then any value supplied in the Bill_Date field will be ignored.

A value of "Y" indicates that the item's eligibility is linked to the project / task date (Completed or Revised End Date).  The date used when projecting future fixed price item billing eligibility will be the Task's Revised Date unless a Completed date has been populated on the task (in which case the Completed Date will be used).

7

G

Bill_Amount

ALWAYS REQUIRED on ADD. The Bill Amount is a required field when entering a Fixed Price Billing Item.  This amount can be positive or negative. This value is not considered on delete.

This field accepts a numeric value up to 13 positions to the left of the decimal and 2 positions to the right.

8

H

Revenue_Recognition_Method

ALWAYS REQUIRED.  The valued supplied in this field will determine when the revenue for this item should be recognized.  

Note that you cannot import fixed price "schedules", thus there is no option in this field that corresponds to the "Custom Schedule" option available within the user interface.

Allowable values include:

• WHEN_BILLED
• PERCENT_COMPLETE

9

I

Delete

This field can be used to trigger the system to delete a fixed price item.  In order for the delete to happen, you must include the following text string !DELETE! in this field.

You will also need to supply the other required fields in order to identify which items to delete, including:

• Project_Org_Code
• Project_Code
• Task_Name (if this is a task level fixed price item)
• Description
• Bill_Date or Bill_On_Completion (see conditional rules above)
• Revenue_Recognition_Method

The delete will remove one or many values that match the criteria suppled for the above list of fields.  

• Note that any Bill_Amount value suppled when attempting a delete is not consider when identifying matching entries to delete.  
• • For example, if you have three identical fixed price items differentiated only by amount, importing a single delete record with criteria that matched the first of those three entries would result in all three entries being removed.
  • Because you can create identical fixed price item entries (ie uniqueness is not enforced) the system will delete all entries that have matching criteria.
• If the fixed price item has already participated in a billing post process, the deletion will be prevented.
• • Should multiple fixed price items have matching criteria, If any of the matching entries has participated in a billing post process, no matching records will be deleted (you will need to manually delete the desired fixed price entries via the user interface for that particular project).

Field

Description

Type of Import

Select the appropriate import type from the list of available types of imports.

File to Import

Enter (or browse for) the file that you would like to import.

Output Options

Specify the level of detail included in the output.