JC Import Work Centre Plans

You can import a work centre plan using the Work Centre Plan Maintenance form.

Options Reference

Each option and field on the form is described below. Mandatory options and fields are highlighted in red.

Description

Enter the name of the new work centre plan.

Load From File

Click this button to open the Load Plan from .csv form to enter details for importing a file.

Load Plan from .csv Form

Options Reference

Each option and field on the form is described below. Mandatory options and fields are highlighted in red.

Source File

Enter the name of the file with details to import, including the path to the file. Click the Browse button to find the file.

Employee and User settings in file

Select this option to include employee or type and user or team settings in the file.

If you:

Select this option, the file format includes seven lines per level set up as detailed below.
Don't select this option, the file format has one line per level, and each level has these options selected:
- All employees.
- Edit Completion Permissions All Users.

Auto create Work Centres

Select this option to create work centres if they do not exist in the current company.

If you:

Select this option, the work centre codes are automatically created when a work centre code is found in the file that does not exist in the current company. The values created are:
- Company - The current company.
- Code - The code supplied in the file.
- Description - This is automatically created if no Alternate Description is specified. If an Alternate Description is specified, this is imported into the work centre plan, and the work centre description is created.
Don't select this option, on encountering a work centre code in the file that does not exist in the current company, the work centre code is considered to be invalid, and an error message displays.
When the error message dialog box is closed, the import process is aborted and any processing is rolled back, returning Greentree Desktop to the state it was before the import began, including deleting the work centres that were auto-created by this process.

Assign all Employees

Select this option to give all employees access to work centre branches by default on import. This option is not enabled if the Employee and User Settings in file option is selected.

If you select this option, it assigns all employees to all work centre branches on import. If not selected, then no employees ar assigned to the work centre branches.

Click this button to start the import process.

Cancel

Click is button to close the Load Plan form and not start the import process.

File Formats

Only two file formats are accepted by the import process:

Work centre plan with all employees made available and all users allowed permission to complete each level, and
Work centre plan with specific settings for available employees and user permissions per level.

The file must be a .csv file.

Employee and User settings in file is not selected

The file format comprises only lines that define the work centre plan level structure. The line number for each line imported (when the Employee and User settings in file is selected) must be 1 for each line processed.

It must be in this format:

1,<Work Centre which defines the branch level>,<Alternate Description>,<Parent Work Centre>,isPostingLevel,isAllActivities,Activity Group,Default % Complete

Field Parameters Definition

Employee and User settings in file is not selected

Line	Item	Description		Required/Default
1	WC	Work Centre, if Parent Work Centre is populated. Create this work centre as a child of the parent identified above. If Parent Work Centre is not populated, create a parent level work centre only.		Mandatory
1	Alternate Description	Description for the level on the work centre plan. If this is null, the work centre's description is used on the plan.		Mandatory You can enter: Null String, up to 50 characters Cannot include, (comma)
1	Parent WC	Valid work centre or blank.		Optional
1	isPostingLevel	Specifies whether this level is a posting level.		Mandatory True or False (or case variations of these; for example, True, true)
1	isAllActivities	Specifies whether this level uses all JC activity codes. If isPostingLevel is False, ignore.		Mandatory True or False (or case variations of these; for example, True, true)
1	Activity Group	The activity group for this level. If isPostingLevel is false or isAllActivities is true, ignore.		Mandatory Valid JC activity group
1	Default % Complete	If not specified, then set to None.		Optional You can enter: Budget vs Actual - Cost Budget vs Actual - Hours Budget vs Actual - Sell Elapsed Time None
These lines must all be present if employee and user settings in the file are selected. They must not be present if Employee and User settings in file is not selected. Line 1 of the import file uses exactly the same parameters as defined above.
Line	Item		Description	Required/Default
2	Employee Codes		List of employee codes separated by commas.	Can be $ALL (or $all or $All). Can be empty (blank means none).
3	Employee Types		List of employee types separated by commas. If line 2 is $ALL, ignore this line (since all employees is selected for this level). If line 2 is a list of employee codes, and line 3 is $ALL all employees are required. If line 2 and line 3 are both blank, no employees are required.	Can be $ALL (or $all or $All). Can be blank.
4	Completion Permission Users who can complete this level		List of user names separated by commas.	Can be $ALL (or $all or $All). Can be blank.
5	Completion Permission Users who can complete sub-levels of this level		List of user names separated by commas. Of the users listed in line 4, these are the users who can complete the sub-levels. If any of the users in this list are not in line 4, ignore them (since you can't give sub-level permission to someone who does not have current level permission).	Can be $ALL (or $all or $All) only if line 4 is $ALL. Can be empty (no users of line 4 have permission to close sub-levels).
6	Completion Permission Teams who can complete this level.		List of team names separated by commas.	Can be $ALL (or $all or $All). Can be blank.
7	Completion Permission Teams who can complete sub-levels of this level		List of team names separated by commas. Of the teams listed in line 6, these are the teams who can complete the sub-levels. If any of the teams in this list are not in line 4, ignore them (since you can't give sub-level permission to a team that does not have current level permission).	Can be $ALL (or $all or $All). Can be empty (no teams of line 6 have permission to close sub-levels).
	How do we handle conflicts of User settings in Lines 4-7? If the process encounters a value of $ALL in any of lines 4-7, it treats the selection criteria in each of the rows as its own separate criteria which process regardless of what may be present in any other row. Example 1 4,Craig Clark,Cameron Cook 5,Craig Clark 6,ALL 7,ALL Users Clark and Cook can complete this level. User Clark can complete the sub-levels. All teams can complete this level. All teams can complete the sub levels. Example 2 4,$All 5,Craig Clark, Cameron Cook 6,ALL 7,SERVMAN All users can complete this level Craig Clark and Cameron Cook can complete sub-levels. All teams can complete this level. Members of team SERVMAN can complete sub-levels.