Dynamics SL
The DATABASICS Time & Expense Reporting system integrates to Dynamics SL to support labor and expense accounting.
Each SL entry module specific outbound from DATABASICS is outlined in separate sub-sections, as follows:
Journal Entry - labor and expense accounting details
Vouchers and Adjustments - reimbursable expense accounting, vendor payables
Project Charge Entry - labor and expense project accounting details
Inbound Data to DATABASICS
In a bi-directional integration Demographic (Organization) and Project (WBS) data typically originates in SL and is imported to DATABASICS to support valid data in the outbound flows.
Organization Structure
In an SL integration the DATABASICS Organization structure typically consists of one or more of the following:
Company
Subaccount
Labor Class - supporting billing if included
Vendor ID - supporting reimbursement through Vouchers and Adjustment if included
Cost Rates - supporting project cost accounting solution if included
Employee
The Employee typically has one or more of the following properties:
Employee ID
Employee First and Last Name
Home Company
Home Subaccount
Default Labor Class
Employee Type - supporting entry validation (e.g. OT) if included
Email address
Manager ID - supporting approval requirements if included
Hire Date
Termination Date
Work Breakdown Structure
In an SL integration the DATABASICS Work Break Down Structure typically consists of one or more of the following:
Project
Task
Bill Rate - supporting billing if included
The Project and Task typically has one or more of the following properties, supporting customer’s specific requirements:
Contract Type
Owning Company
Default Subaccount
Default GL Account
Resource Assignment
Manager ID - supporting approval requirements if included
Start Date
End Date
Inbound Integration methods
Data flow inbound to DATABASICS is managed using the DATABASICS Import / Export utility.
In an SL integration data can be read directly from SL or the customer can provide flat files with data, according to agreed specifications.
The loads will validate to make sure all the required fields are provided in order for the employee to be active in DATABASICS.
Direct Data Pull from SL
We can use the DATABASICS import / export utility to read data directly from SL. Using the direct pull solution provides the organization and project data, and refreshes the data in DATABASICS for new records and existing records without the need for an intermediary step.
This approach includes installing the import utility inside the customer firewall and linking the utility back to DATBASICS for delivery of the specified data.
A agreed specification will outline what data to import from where. Example employee profile specification with mapping between systems:
| DATABASICS Data field |
|
pjemploy.em_id02 | EMPLY_ID | Primary key |
pjemploy.emp_name | N_FIRST | First and last is the same field in SL split to separate fields in DATABASICS |
pjemploy.emp_name | N_LAST |
|
pjemploy.cpnyid | OPT_CODE | Home Company |
pjemploy.gl_subacct | DEPT_CODE | Home Subaccount |
pjemppjt.labor_class_cd | FUNCTCODE | Default Labor Class |
pjemploy.emID03 | EMAIL1 | Used for login and notifications |
The utility allows the customer to specify the frequency of each scheduled load and also gives the ability to refresh data manually.
Data Push to DATABASICS
Flat files can be imported into DATABASICS from a dedicated SFTP site: more information here
Files must be provided according to agreed specifications, loads can be scheduled according to requirement (e.g. weekly, daily, hourly), or manually triggered on an as needed basis.
2021 DATABASICS, Inc