DATABASICS Data structure overview

Summary

DATABASICS’ time and expense management products data structure is made up of different types of data:

• Demographic (Organization)

• Activity (WBS)

• Time (only applicable for Time customers)

• Expense (only applicable for Expense customers)

• Approval (separate tables, can be tied with data in either of the other types)

Organization Structure

DATABASICS Organization Structure is comprised of the Operating Unit, Department, Employee, Function, and Location.   Also associated with Organization are Currency, Employee Types, Holiday, Vendor, Time Code (Pay Code), Time Code Validation Rules, and User Reporting Group elements.

The Operating Unit is the highest level within an organization.  Operating Unit can represent any type of cost center or company.  An Operating Unit is unique across the entire organization.  For example, Operating Unit may correspond to an organization’s "Divisions".   Operating Unit is a required level of the Organization Breakdown.

Operating Unit

Department

Function

Location

The DATABASICS element Location is used to capture specific business sites or if specificity is not required, geographic or political consolidations.  For example, different work/business rules may apply per Location with respect to the length of the workday, weekdays verses weekends, etc.  Each employee is assigned to a default location, which can be changed during Time Entry on a per line basis.

Vendor

DATABASCS’s Vendor can identify users in the application for the purposes of reimbursing Vouchers and Invoices.

Time reported by contractors, or other members of outside organizations. 

Expenses for reimbursement (including by employees) as well as external vendors, e.g. as part of a Vendor Payment solution.

Employee

Employee is the lowest level of the Organization Structure and are assigned to one and only Department.  This element is used to identify the actual users of the DATABASICS system. 

Activity Structure

Time Structure

Time Code (Pay Code),

Time Code Validation Rules,

User Reporting Group

Expense Structure

Approval Structure

Data Dictionary

All fields in the application can be relabeled to meet the customer’s requirements and accommodate for a familiar end-user experience.

The below table highlights common alias facilitated for through labelling in the application for customers.