Ginsu Report - Row Fields
If your Projector installation is making use of User Defined Fields those data elements will be available for use in this report type. Client, Engagement, Project and Resource level based user defined fields will be found in each corresponding Field Category. For example, if you have defined a resource-level user defined field called Utilization Target you will find it in the Resource Fields called Resource Utilization Target.
When reporting on stoplight UDFs (Project Health fields), we display a string of characters representing the health. For example,if you looked at the health for the six months, you would be returned a six character string. If there is no health status for a given time period, no character is returned. For example a four character string would be returned if the first two months had no data. Finally, the character returned is based on the first day of a time bucket. For month, it would be the first day of the month. For week, Â it would be the first day of the week. 'Today' represents the day the report was run. Use Actuals Through Date has no effect on stoplight UDF reporting.
Based on the number of Client levels defined in your installation you will have available fields under the Client Fields for each named level. For example, if your installation has two Client levels, Division and Department, you will have Division Name and Department Name as available fields.
Field | Field Category | Description |
---|---|---|
Billing Status | Invoice Fields | On an issued invoice, on a draft invoice, or unbilled. |
Booked Candidates | Role Fields | List of candidates on unnamed booked roles |
Booked End Date | Role Fields | The last date on which there are booked hours for this role |
Booked Start Date | Role Fields | The first date on which there are booked hours for this role |
Client | Client Fields | Â |
Cost Baseline Name | Budget Fields | Name of the current active cost baseline |
Cost Card Chargeable (Y/N) | Cost Fields | Yes if the cost card's client amount is greater than zero. |
Cost Card Description | Cost Fields | Â |
Cost Center Mapping (Expense) | Accounting Fields | The accounting system's cost center to which expense will be routed. |
Cost Center Mapping (Revenue) | Accounting Fields | The accounting system's cost center to which revenue will be routed. |
Cost Contract Amount in Engagement Currency | Contract Line Item Fields | Cost contract amount. |
Cost Contract Amount in Reporting Currency | Contract Line Item Fields | Cost contract amount. FX'd to currency set on the parameters tab. |
Cost Contract Terms | Engagement Fields | Engagement cost contract terms: T&M, Fixed Price, or Not to Exceed |
Engagement | Engagement Fields | Â |
Engagement Billable (Yes/No) | Engagement Fields | Yes if the engagement is a billable type |
Engagement Billing Address Attention | Engagement Fields | Â |
Engagement Billing Address City | Engagement Fields | Â |
Engagement Billing Address Company Name | Engagement Fields | Â |
Engagement Billing Address Country | Engagement Fields | Â |
Engagement Billing Address Line 1 | Engagement Fields | Â |
Engagement Billing Address Line 2 | Engagement Fields | Â |
Engagement Billing Address State/Province | Engagement Fields | Â |
Engagement Billing Address Zip/PostalCode | Engagement Fields | Â |
Engagement Code | Engagement Fields | Â |
Engagement Company | Engagement Fields | The name of the company associated with the engagement's cost center |
Engagement Cost Center* | Engagement Fields | You will not find this exact line in your report. Instead, for each Cost Center Level defined in the Cost Center Editor you will have a choice. So for example if you have levels called Business Unit and Group then there will be one line called Engagement Business Unit and another called Engagement Group. |
Engagement Currency | Engagement Fields | Billing currency of the engagement |
Engagement Manager | Engagement Fields | Â |
Engagement Manager Display Name | Engagement Fields | Â |
Engagement Manager Email Address | Engagement Fields | Â |
Engagement Name | Engagement Fields | Â |
Engagement Productive | Engagement Fields | Â |
Engagement Stage | Engagement Fields | Name of the engagement stage |
Engagement Type | Engagement Fields | Â |
Expense Document Name | Expense Document Fields | Name of the expense report or vendor invoice |
Expense Document Number | Expense Document Fields | Identifying number associated with the expense report or vendor invoice |
Expense Document Type | Expense Document Fields | Expense Report, Vendor Invoice, or Soft Cost |
Expense Location | Cost Fields | Location in which the expense was incurred |
Expense Type | Cost Fields | Â |
For Reporting Only (Y/N) | Other Fields | Yes only if the cost card was imported as a for reporting only cost card |
Holdback Revenue (Y/N) | Engagement Fields | Yes if the revenue is from a holdback |
Hours Status | Hours Fields | Approved, unapproved, booked, or requested change. This is a deprecated report field. It is only available in old, saved reports. It has been supplanted by Approval Workflow Status. |
Hours Type | Hours Fields | Indicates if hours are associated with a project, holiday, or time off. |
Invoice Date | Invoice Fields | Â |
Invoice Number | Invoice Fields | Invoice or credit memo number |
Invoice Paid (Y/N) | Invoice Fields | Yes if the invoice has been marked as paid |
Pass-through Cost Flag (Y/N) | Cost Fields | Yes if the cost is a pass-through cost. |
Project | Project Fields | Â |
Project Code | Project Fields | Â |
Project Description | Project Fields | Limited to 255 characters to support Excel 2003. Please use the Report Web Services if you require the full description. |
Project End Date | Project Fields | The latest date for which time or cost can be incurred for this project |
Project Likelihood % | Project Fields | Â |
Project Location | Project Fields | Â |
Project Manager | Project Fields | Â |
Project Manager Display Name | Project Fields | Â |
Project Manager Email Address | Project Fields | Â |
Project Name | Project Fields | Â |
Project Stage | Project Fields | Name of the project stage |
Project Start Date | Project Fields | The earliest date for which time or cost can be incurred for this project |
Project Task Code | Project Fields | This field has been deprecated. Please use Project Task Type instead. |
Project Task Type | Project Fields | Â |
Purchase Order Number | Invoice Fields | Populated if time or costs reported on are presently on an invoice, unbilled time or cost will report a blank PO number. |
Resource | Resource Fields | Â |
Resource Billable (Yes/No) | Resource Fields | Yes = resource is usually billable |
Resource Company | Resource Fields | The name of the company associated with the resource's cost center |
Resource Cost Center* | Resource Fields | You will not find this exact line in your report. Instead, for each Cost Center Level defined in the Cost Center Editor you will have a choice. So for example if you have levels called Business Unit and Group then there will be one line called Resource Business Unit and another called Resource Group. |
Resource Department | Resource Fields | Â |
Resource Display Name | Resource Fields | Â |
Resource Email Address | Resource Fields | Â |
Resource Employee ID | Resource Fields | Â |
Resource First Name | Resource Fields | Â |
Resource Last Name | Resource Fields | Â |
Resource Location | Resource Fields | Â |
Resource Middle Name | Resource Fields | Â |
Resource Mobile Phone | Resource Fields | Â |
Resource Office Phone | Resource Fields | Â |
Resource Other Contact Information | Resource Fields | Â |
Resource Pay Category | Resource Fields | Salaried without overtime, salaried with overtime, or hourly. |
Resource Temporary Worker (Yes/No) | Resource Fields | Yes = contractor. This flag has been replaced by Resource Type. If you have not already you should thinking about migrating your installation to use this instead. |
Resource Title | Resource Fields | Â |
Resource Type | Resource Fields | Resource Types are used for categorizing resources and also for determining their internal cost (RDC) based on the work they have done. For example, salaried workers don't cost more if they work overtime, but hourly workers do. |
Revenue Recognition Method | Engagement Fields | Percent Complete or Revenue Schedule. Applies only to fixed price engagements. |
Role | Role Fields | Â |
Role Billing Department | Role Fields | Department of the title used for setting the billing rate of this role |
Role Billing Title | Role Fields | Title used for setting the billing rate of this role |
Role End Date | Role Fields | End date of role |
Role Start Date | Role Fields | Start date of role |
Skill | Skill Fields | For each skill defined in the Skill Editor a corresponding Skill Field is available |
Standard Rate Type | Project Fields | Â |
Standard Rate Type Code | Project Fields | Â |
Standard Task Type | Project Fields | Â |
Standard Task Type Code | Project Fields | Â |
Task Name | Task Fields | Name of the task |
Time Baseline Name | Budget Fields | Name of the current active time baseline |
Time Card Chargeable (Y/N) | Time Fields | Yes if the time card's billing adjusted revenue is greater than zero. |
Time Card Marked Non-Chargeable (Y/N) | Time Fields | This field is deprecated. It will always return zero. |
Time Contract Amount | Engagement Fields | Engagement time contract amount |
Time Contract Amount | Engagement Fields | Engagement time contract amount |
Time Contract Amount Less Holdback | Engagement Fields | Time contract amount minus the time holdback amount |
Time Contract Amount Less Holdback | Engagement Fields | Time contract amount minus the time holdback amount |
Time Contract Terms | Engagement Fields | Engagement time contract terms: T&M, Fixed Price, or Not to Exceed |
Time Holdback Amount | Engagement Fields | Engagement time holdback amount |
Time Holdback Amount | Engagement Fields | Engagement time holdback amount |
Time Holdback Percent | Engagement Fields | Time holdback as a percentage of the time contract amount |
Timeoff Reason | Time Off Fields | Time off reason |
Units Name | Unit Fields | The name of the unit of measure |
Vendor Name | Vendor Fields | Â |
Vendor Number | Vendor Fields | Â |
WBS Code | Task Fields | Work breakdown structure code(e.g., 4.1.2) |
Work Location | Hours Fields | Location where the work was performed |