Integrated Data

Deltek Costpoint Cloud

What this page covers: A complete reference mapping every Deltek Costpoint field to its Mosaic equivalent. Use this guide when configuring your integration, verifying synced data, or troubleshooting discrepancies.

Integration typeCloud (ODBC)
Setup complexityModerate
PrerequisiteCostpoint Cloud Integration Setup

How Data Flows

Costpoint Cloud (ODBC) → Mosaic Sync Engine (field mapping + configurable sources) → Mosaic (7 synced data types)

The Costpoint integration uses a read-only ODBC connection to query two Costpoint schemas:

  • Transaction Schema — Project Master, Employee, Organization, Project Labor Category rate data.
  • Time & Expense Transaction Schema — Timesheet line and cell data.

Integrated Data Types

The integration syncs 7 data categories from Costpoint into Mosaic:

Data TypeDescription
Employees (Members)Member records (name, email)
ClientsClients sourced from the Customer table or the top of the Project hierarchy (configurable)
ProjectsProject records (number, name, dates, fee, billable, profit center)
PhasesPhase / subphase breakdowns (supports up to 10 hierarchy levels)
Departments (Organizations)Costpoint Organizations synced as Mosaic Departments
Time EntriesTimesheet entries (hours, project, phase, billability, approval status, hourly rate)
Bill Rates (Rate Groups & Rates)Project Labor Category rates with start/end dates and effective member rate windows

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 ODBC user role.

Not Synced

Data TypeDescription
Employee TitleCostpoint employee job titles are not currently synced
Phase Budgeted HoursThe Task Value (budgeted hours) on a Phase is not synced
Inactive ProjectsProjects, Phases, and Organizations where ACTIVE_FL is not Y are excluded
Sub-OrganizationsOnly top-level Organizations (ORG_TOP_FL = 'Y') are synced

Reading the Field Mapping Tables

Symbol legend for technical tables

The Technical Reference tabs below use a shorthand notation for ODBC table/column references. Read this legend before reviewing the mappings.

SymbolMeaningExample
.ODBC table / column referenceEMPL.FIRST_NAME = the FIRST_NAME column on the EMPL table
Values combined into a composite valueCUST_IDCUST_LONG_NAME = concatenated into the displayed client name
&Composite key parts separated by &EMPL_ID&TS_SCHEDULE_CD&YR_NO_CD&LINE_NO&HRS_DT = composite Time Entry ID
>Fallback priority — use the first available valueTS_LINE.SHORT_LINE_TEXT > TS_CELL.SHORT_CELL_TEXT = use line text first
orConfigurable — an integration setting selects whichEMPL.EMPL_ID or PROJ.PROJ_ID = depends on Client Mapping Source setting

Detailed Field Mappings

Jump to a section: Employees | Clients | Projects | Phases | Departments (Organizations) | Time Entries | Bill Rates (Rate Groups)


Employees

What Syncs to MosaicWhere It Comes From in Costpoint
Employee IDThe unique employee identifier
First NameThe employee's first name
Middle NameThe employee's middle name
Last NameThe employee's last name
EmailThe employee's email address
Modified DateWhen the employee record was last modified

Clients

What Syncs to MosaicWhere It Comes From in Costpoint
Client IDThe unique client identifier — sourced from the Customer record or top-of-hierarchy Project
Client NumberSame identifier used as the client business number
Client NameComposite display name combining the ID and the client's long name
Modified DateWhen the client record was last modified

Configurable: Client Mapping Source

Your integration settings determine how Clients are sourced:

  • Customer (customerId, default) — Clients are read from the Costpoint CUST (Customer) table.
  • Project Number (clientNumber) — Clients are read from Level 1 entries in the Project Master, where each top-level Project ID is treated as a Client.

Projects

What Syncs to MosaicWhere It Comes From in Costpoint
Project IDThe unique project identifier
Project NumberThe Level 2 project segment identifier (trimmed)
Project NameThe project name from the Project Master
ClientThe client linked to the project (varies by Client Mapping Source)
Start DateThe project start date
End DateThe project end date
FeeThe project's funded cost amount
BillableWhether the project is flagged as billable
Profit CenterComposite of the project's Organization ID and name
Billing TypeAlways synced as Role (Costpoint Project Labor Categories are role-based)
Rate GroupThe Project's rate group — either the project itself or its Level 1 parent (configurable)
Modified DateWhen the project record was last modified

Phases

What Syncs to MosaicWhere It Comes From in Costpoint
Phase IDThe unique phase identifier
Phase NumberThe level-specific project segment ID (Level 3 → L3 segment, Level 4 → L4 segment, etc.)
Phase NameThe phase name from the Project Master
ParentThe parent project or parent phase (one level up in the hierarchy)
ProjectThe Level 2 project this phase rolls up to
Start DateThe phase start date
End DateThe phase end date
FeeThe phase's funded cost amount
BillableWhether the phase is flagged as billable
Profit CenterComposite of the phase's Organization ID and name
Modified DateWhen the phase record was last modified

Hierarchy support

Costpoint Project Master supports up to 10 hierarchy levels:

LevelMosaic Role
1Client (top-level)
2Project
3Phase
4–10Nested sub-phases

Departments (Organizations)

What Syncs to MosaicWhere It Comes From in Costpoint
Department IDThe Organization identifier
Department NameThe Organization display name

Time Entries

What Syncs to MosaicWhere It Comes From in Costpoint
Time Entry IDA composite of employee, timesheet schedule, year, line number, and hours date
DateThe day the hours were logged
EmployeeThe employee who logged the time
ProjectThe Level 2 project derived from the timesheet line's UDT02 (project assignment)
PhaseThe deeper-level phase the time was logged against (null if the assignment is at the project level)
HoursThe hours entered on the timesheet cell
DescriptionThe timesheet line description, falling back to the cell description
BillableWhether the timesheet cell is flagged as billable
Approval StatusThe timesheet cell status — Not Submitted, Submitted, Approved, or Rejected
Hourly RateThe matching Project Labor Category rate (if a rate row exists for the employee's labor category and project root)

Approval Status Mapping

Costpoint Status (S_CELL_STATUS_CD)Mosaic Status
M / O (Open)Not Submitted
S (Submitted)Submitted
A (Approved)Approved
R (Rejected)Rejected
P (Processed)Approved

Time Entry Filtering

All timesheet cells are fetched regardless of approval status. Your Mosaic Solutions team can configure downstream filtering so that only Approved status flows into Mosaic.


Bill Rates (Rate Groups)

What Syncs to MosaicWhere It Comes From in Costpoint
Rate GroupThe rate table associated with a project (or its top-level parent, configurable)
RoleThe Project Labor Category — displayed as [Code]: [Description]
Rate AmountThe billing rate amount
Start DateThe effective start date of the rate
End DateThe effective end date of the rate
Member Role WindowEffective date range for a member's labor category assignment

Configurable: Rate Table Mapping

  • Project-based (default) — Each Project gets its own Rate Group keyed to the PROJ.PROJ_ID.
  • Client-based — Multiple Projects share a Rate Group keyed to the Level 1 ancestor of the Project ID.

Configurable Fields at a Glance

SettingAffectsOptions
clientMappingSourceClient sourcecustomerId (default, reads CUST) or clientNumber (Level 1 PROJ rows as clients)
rateTableMappingProject's Rate Group keyprojectBased (default, one Rate Group per Project) or clientBased (Level 1 grouping)
ClientImportAsImport shapeOptional — can convert a Costpoint "client" entity to a Mosaic Project

Troubleshooting & FAQ

Why aren't time entries showing up for a particular project?

Time Entries link to Projects via the UDT02 field on the timesheet line. The Mosaic Project ID is derived from the first two segments of TS_LINE.UDT02_ID. If a timesheet line has a UDT02 value that doesn't match a Project at Level 2 in Mosaic, the time entry will be skipped.

Why isn't an Organization showing up as a Department?

Mosaic only syncs top-level Organizations (ORG_TOP_FL = 'Y'). Sub-organizations under a top-level organization are not surfaced as separate Departments.

Why is my Project missing or showing as inactive?

Projects, Phases, and Organizations are filtered to active records only (ACTIVE_FL = 'Y'). If a Project is reactivated in Costpoint, it will sync into Mosaic on the next run.

Why doesn't Employee Title sync?

Employee Title is not currently part of the standard Costpoint integration. If you need Title to sync, contact your Mosaic Solutions team — this is a customization scoped under your contracted implementation rate.

Why don't Phase Budgeted Hours sync?

The Task Value (budgeted hours) on a Phase is not currently part of the standard integration. Your CSM can scope this as a customization.

Can Mosaic sync only Approved Time Entries?

By default, all Time Entry statuses are fetched and stamped with their Costpoint approval status. Your Mosaic Solutions team can configure downstream filtering so that only Approved entries are surfaced in your Mosaic environment.

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 Costpoint documentation referenced in this guide:

TopicLink
Costpoint Online HelpCostpoint Help
Deltek Help & LearningDeltek Help

Related Documentation