Events

This table lists the import file columns for the Event table:


Column	Description	Type	Size
Member	The member name or ID in the database, such as a unit or a product, used for the Detail Budgeting data (e.g., San Diego or Baseball).	Text	255
EmpID	The ID of the employee.	Text	255
EventDate	The date when the event takes place.	Date	mm/dd/yyyy
EmpType	The employee type, which is customized on the Employee Types tab.	Text	255
Title	(Optional) The employee's title.	Text	255
EventType	The event type, which is customized on the Event Types tab.	Text	50
Amount	The amount of the salary, salary change, commission, bonus, etc.	Number	21
Hours	(Optional) The hours worked, if applicable.	Number	9
Percentage	(Optional) The percentage of the employee's time worked for the current member (see Member). For example, 100 or 50 percent.	Number	9
Version	(Optional) The Version dimension member for the data. If the version is mentioned in the section head, then the column is optional. If the Version parameter in the section head is Multiple, then the column is required.	Integer	8
SecondAllocation	(Optional) The allocation ID used for the secondary dimension. This ID determines how data is allocated across one or more of the secondary dimension members.	Integer	8

The Event import file can have multiple records.

If the import file includes multiple events for an employee for the same day, it is important to specify each event separately. Do not merge multiple changes into a single event. This is particularly important when changing the employee type, which determines how certain events are processed. Therefore, to ensure multiple events are processed properly and in accordance with a new employee type, first specify the New Type (description) event and then specify the remaining events, one at a time.

This is a sample text file that could be imported into Detail Budgeting for events.

[Detail Budgeting]
Version=Budget
Columns=Member,EmpID,EventDate,EmpType,Title,EventType,Amount,Hours,Percentage
Administration,0355,3/1/05,FullTimeHourly,Level
S1,Salary,27.64,40,100
Administration,6936,3/1/05,FullTimeSalaried,Level
OI,Salary,565000.17,,100
Assets

Not all global events must be imported. Global events that are applied to each employee are not required to be imported.

Global events that only apply to some employees (but not all) need to be imported (global events where the Apply to each Employee option is not checked).

The basic format of the import file is this:

[Detail Budgeting]
Version=Actual
Columns=Member,EmpID,Version,GlobalEventId
Australia,14,1,2

To find the value to be used for the GlobalEventId column, export the administration tables using the Export command in Detail Budgeting Administrator, search for the event name, and find the ID assigned to it.