Integrated Data
Deltek Vision Cloud
What this page covers: A complete reference mapping every Deltek Vision Cloud field to its Mosaic equivalent. Use this guide when configuring your integration, verifying synced data, or troubleshooting discrepancies.
| Integration type | Cloud (Stored Procedures + API) |
| Stored procedures required? | Yes — for Time Entries and Profit Centers |
| Setup complexity | Moderate |
| Configurable fields | 10+ fields support alternative sources |
| Prerequisite | Vision Cloud Integration Setup |
How Data Flows
Vision Cloud (Stored Procs + API) → Mosaic Sync Engine (field mapping + configurable sources) → Mosaic (8 synced data types)
Unlike the On-Prem version, the Cloud integration uses stored procedures and the Vision API to access data. Stored procedures are required for Time Entries and Profit Centers. See Adding Stored Procedures to Vision for setup instructions.
Integrated Data Types
The integration syncs 8 data categories from Vision Cloud into Mosaic:
| # | Data Type | Description |
|---|---|---|
| 1 | Clients | Client records |
| 2 | Employees | Staff records with names, emails, and status |
| 3 | Projects | Project records including profit centers and billing configuration |
| 4 | Phases | WBS2/WBS3 phase breakdowns under projects (includes Profit Centers via stored procedure) |
| 5 | Time Entries | Posted and unposted time with hours, rates, and billability (requires stored procedure) |
| 6 | Work Categories (Labor Codes) | Labor codes used for time categorization |
| 7 | Bill Rates | Billing rate tables (by category, labor code, or employee) |
| 8 | Roles | Employee roles (BillingCategory source only) |
This list may expand as new features are added. If new features require additional permissions, your Customer Success Manager will reach out to request that they be added to the role you have assigned to the Mosaic user.
Reading the Field Mapping Tables
Symbol legend for technical tables
The Technical Reference tabs below use a shorthand notation for API/database sources. Read this legend before reviewing the mappings.
| Symbol | Meaning | Example |
|---|---|---|
. | API table field reference | PR.WBS1 = the WBS1 field from the Project (PR) table |
• | Values combined into one composite value | PR.WBS1 • PR.WBS2 = concatenated into a composite key |
x | Values multiplied together | BT.Mult1 x BT.Mult2 = product of both multipliers |
> | Fallback priority — use the first available value | PR.EndDate > PR.ActCompletionDate = use EndDate; if null, use ActCompletionDate |
/ | One of these, depending on billing method | Category / LaborCode / Employee = varies by billing method |
or | Configurable — an integration setting selects which | PR.WBS2 or PR.WBS3 = your configuration chooses one |
, | Multiple fields used together per configuration | PR.Fee, PR.ConsultFee = set of options selected by config |
Detailed Field Mappings
Jump to a section: Clients | Employees | Projects | Phases | Time Entries | Work Categories (Labor Codes) | Bill Rates | Roles
Clients
Vision UI location: Info Center → Clients → General
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Client ID | The unique client identifier used internally by Mosaic |
| Client Number | The client's business number (same source as Client ID) |
| Client Name | The client display name |
| Client Description | The client code/description |
| Created Date | When the client record was created |
| Modified Date | When the client record was last modified |
Employees
Vision UI location: Info Center → Employees
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Employee ID | The unique employee identifier |
| First Name | The employee's first name |
| Middle Name | The employee's middle name |
| Last Name | The employee's last name |
| The employee's email address | |
| Is Archived | Derived from the employee's status — Inactive or Terminated = archived |
| Billing Category | The employee's billing category (used as Default Role) |
| Job Cost Rate | The employee's job cost rate (Optional — used as Default Cost Rate) |
| Organization | The employee's organizational unit (from Configuration → Codes → Organization) |
| Created Date | When the employee record was created |
| Modified Date | When the employee record was last modified |
Important: Terminated Employees
Employees marked as "Terminated" in Vision will not automatically be linked in Mosaic. Their spent time and budgets will not sync, which can cause discrepancies in project budget calculations.
Workaround:
- In Vision, temporarily re-activate the terminated employee
- Run a sync in Mosaic to link the employee and their historical data
- Re-terminate the employee in Vision
- Verify that budget data in Mosaic now reflects the correct totals
Projects
Vision UI location: Info Center → Projects (fee data from Budget & Revenue → Compensation)
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Project Name | The project short name or long name from the Projects Info Center (configurable) |
| Project Number | The WBS1 project number |
| Client | The primary client linked to the project |
| Company Name | The organization name on the project, falling back to the client address record |
| Billable Status | The project's charge type — Regular = Billable; Hold/Proposal = Not Billable |
| Budget Status | The project status value (configurable mapping) |
| Is Archived | Derived from the project status (configurable) |
| Start Date | The project start date (configurable) |
| End Date | The project end date, falling back to actual or estimated completion date (configurable) |
| Fee | The project fee amount — multiple fee sources available (configurable) |
| Project Manager | The employee assigned as project manager |
| Billing Type / Rate Group | The labor billing method and associated rate table (configurable) |
| Rate Multiplier | The combined product of up to three billing multipliers |
| Profit Center | The project's organizational unit and its name |
| Currency | The project currency (visible on 1st project level only) |
| Created Date | When the project record was created |
| Modified Date | When the project record was last modified |
Phases
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Phase Name | The phase name or long name (configurable) |
| Phase Number | The WBS2 or WBS3 phase number |
| Phase ID | A composite of WBS1 + WBS2 + WBS3 identifiers |
| Parent | The parent project or parent phase |
| Project | The parent project's WBS1 number |
| Client | The client linked to the phase's project |
| Billable Status | The phase's charge type — Regular = Billable; Hold/Proposal = Not Billable |
| Budget Status | The phase status value (configurable mapping) |
| Is Archived | Derived from the phase status (configurable) |
| Start Date | The phase start date (configurable) |
| End Date | The phase end date, falling back to actual or estimated completion date (configurable) |
| Fee | The phase fee amount — multiple fee sources available (configurable) |
| Rate Multiplier | The combined product of up to three billing multipliers |
| Billing Type / Rate Group | The labor billing method and associated rate table |
| Profit Center | The phase's organizational unit or long name (configurable) — available via stored procedure |
Time Entries
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Date | The transaction date of the time entry |
| Employee | The employee who logged the time |
| Project | The project the time was logged against |
| Phase | The phase (WBS2/WBS3) the time was logged against |
| Work Category | The labor code used for the time entry |
| Hours | The sum of regular and overtime hours |
| Description | The time entry comment |
| Hourly Rate | Calculated from the billing extension or the sum of rate amounts divided by hours (configurable) |
| Billable | Determined by the charge type — Regular = Billable; Hold/Proposal = Not Billable |
Time Entry Sources
To synchronize Time Entries from Vision Cloud to Mosaic, a stored procedure is required. See Adding Stored Procedures to Vision for installation instructions.
By default, Mosaic syncs both unposted and posted time entries (Combined Time). This is configurable — your Solutions Engineer can set it to sync posted time only during setup.
Work Categories (Labor Codes)
Note: Labor Codes are sourced from Configuration → Planning → Generic Resources → Labor Codes. This is only visible if the Planning module is installed.
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Activity ID | The labor code used as the internal identifier |
| Activity Code | The labor code used as the display code (same source as Activity ID) |
| Activity Name / Title | The label/description for the labor code |
Bill Rates
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Rate ID | A composite identifier built from the rate table number, rate entry, and the entity (category, labor code, or employee) |
| Rate Amount | The billing rate amount from the rate table |
| Rate Description | The rate table name combined with the category or resource description (configurable) |
| Is Cost Rate | Whether this rate table is flagged as a cost rate (configurable) |
Roles
Roles in the Cloud integration are sourced from BillingCategory only (compared to 5 options in On-Prem).
| What Syncs to Mosaic | Where It Comes From in Vision |
|---|---|
| Role ID | The billing category identifier |
| Role Name | The billing category description |
Configurable Fields at a Glance
The following fields can be configured to pull from alternative sources in Vision. Refer to your integration settings to see which source is active.
| Entity | Field | Available Sources |
|---|---|---|
| Project / Phase | Name | PR.Name or PR.LongName |
| Project / Phase | Start Date | PR.StartDate (configurable) |
| Project / Phase | End Date | PR.EndDate > PR.ActCompletionDate > PR.EstCompletionDate |
| Project | Fee | PR.Fee, PR.ConsultFee, PR.FeeDirLab, PR.ReimbAllowExp, PR.ReimbAllowCons |
| Phase | Fee | PR.Fee, PR.ConsultFee, PR.FeeDirLab |
| Project / Phase | Budget Status | Configurable status mapping from PR.Status |
| Project / Phase | Is Archived | Configurable mapping from PR.Status |
| Project / Phase | Billing Type | BT.LabMeth, BT.RateTable, BT.ORTable |
| Phase | Phase Number | PR.WBS2 or PR.WBS3 |
| Phase | Profit Center | PR.Org • Organization.Name or PR.LongName |
| Time Entry | Hourly Rate | LD.BillExt / hours or (LD.RegAmt • LD.OvtAmt) / hours |
| Rate | Is Cost Rate | BillingRateTableRate.TableNo (configurable) |
| Rate | Rate Description | BillingRateTableRate.TableName • description (configurable) |
Cloud vs. On-Prem: Key Differences
Compare Cloud and On-Prem capabilities
The Cloud version has some differences compared to On-Prem:
| Feature | Cloud | On-Prem |
|---|---|---|
| Database access method | Stored procedures + API | Direct DB queries |
| Stored procedures required? | Yes (Time Entries, Profit Centers) | No |
| Role sources | 1 (BillingCategory only) | 5 options |
| Work Plans | No | Yes |
| Employee profit center mapping | No | Yes (EMCompany.Org) |
| Overhead multiplier on time entry rates | No | Yes (CFGOHMain.OHRate) |
| Cost rate from time entries | No | Yes (LD.Rate) |
Troubleshooting & FAQ
Why are some employee records or budgets missing?
Terminated employees are not automatically linked in Mosaic. See the Terminated Employees workaround above.
Can I rename field labels in Mosaic to match my Vision custom labels?
No. Custom field name changes in Mosaic to match Vision labeling is not supported as a standard integration feature.
Where does Mosaic pull WBS Fee data from?
Fee data is sourced from the Projects Info Center or Billing Terms Section only. WBS Fee information from other locations is not supported.
What about Employee Profit Center?
Employee Profit Center is not available in the Cloud API. This is an On-Prem-only feature.
What about Cost Rate from Time Entries?
Cost Rate extraction from Time Entries (LD.Rate) is a Hosted/On-Prem-only feature and is not available in the Cloud integration.
Why do Time Entries require a stored procedure?
The Vision Cloud API does not expose time entry data directly. The stored procedure bridges this gap by making time data accessible to the integration. See Adding Stored Procedures to Vision for installation instructions.
I need a data source or field that isn't listed here.
Any integration not listed in this documentation is considered a customization and is charged at an hourly rate. For more information, see Integration Requests.
Deltek Documentation Links
A consolidated reference of all Deltek Vision documentation referenced in this guide:
| Topic | Link |
|---|---|
| Projects Table Reference | UT_TF_Projects |
| Fee Methods | Fee Method Selection |
| Fee Options | Fee Options Form |
| Charge Types | Project Charge Types |
| Billing Terms | Billing Terms Setup |
| Data Dictionary | Vision Data Dictionary |
| EMMain Table | Employee Master Table |
| Clendor Table | Client/Vendor Table |
| Labor Detail Report | Labor Detail |
| Labor Methods | Labor Billing Method |
| Rate Tables | Rate Tables Overview |
| How Vision Determines Billing Rates | Billing Rate Determination |
| Adding Stored Procedures | Stored Procedures Guide |
Related Documentation
Updated about 1 month ago