Importing projects into Solomon Work in progress, under construction

Notes as at 3-Apr-2007 Solomon simulation session. Still to be evolved into a Work Instruction.

MS Project Server side

Main reference - "Sam Sharp's course notes", Page 29 onwards.

Options: Overwrite current setting -> Yes. Change calendar -> to AAO Calendar. Type -> Internal/External/Testing/Adminstrative. (See note 1 above)

Check resources against enterprise resources.

Note -> Unclear if we should materials in schedule.

If we have materials - keep local with base calendar, so that we don't pollute the resource poll.

Won't go across to Solomon.

Map Task Fields -> Hit next button. Unclear what this is really about?

Shows lists of tasks (if there are no errors) -> we ignored the statement that the calendar was "none".

Then select "Import".

Note - is imported but has not yet been published to Web access. See note page 35.

Note - if you base your imported schedule on a schedule with one with another template (e.g. CJE's) you may be asked to confirm how this is to be handled, if it has the same name as an existing one.

Validate the schedule has not been changed by importing to Solomon.

Ensure schedule is published. Collaborate->Publish->All Information

This will trigger emails to be sent out. See note 2 above.

Importing to Solomon.

Open schedule in MSP Server.

Invoke "Solomon Project Information" button (Solomon "P" button)

(Won't have this button if solomon MSP project extensions are not installed)

Dialog Appears. Invoke number builder button next to "Project" line.

Build project number. (OP003 08001). "Increment Button increments the wrong field"

Select project manager and Division Head (SCB/JBH).

Fill in Customer, contract type (fixed price to WIP).

Invoke OK.

Invoke "feet by themselves" button.

Note - if macro cannot be run - invoke Options->Security->Macro Security. Set to Medium/Low (unclear).

Note - macro may fail if you don't have the P drive. (which must be mounted as the P drive).

When we did this - we got an error about "the database file with the specified name already exists on the disk". The file name was not supplied. Various options available - unclear what file. At this point we had been trying to get around the macro issues above. The "Unique ID", "Text1", "PS TUID" and "Text10" fields had appeared in the view.

Selected overwrite. Got this message. "The file "<P:\Numerix\AAO\AAO_Project_Data.mbd?>\not needed" cannot be deleted because it is open or being used by another program."

Exited from error dialog. There was a lock file (AAO_ProjectData.lbd file) in the same directory.

When we tried to append - it give details of who had it open. This lock file appeared and disappeared when we tried Sam's tool - so this was not the problem.

We have do have access to the P drive file from helen's account to get this to work. We did an "Append" and this worked. When we tried to Overwrite it failed.

Project-DSL Pre-Syncrhonisation dialog came up. Wanted to know if we wanted to save the project "not needed". It appears Sam Sharp's tool is naming the project "not needed" when it saves it to the access database.

AT this point we consider the Pre-sync tool to have failed.

We now tried to do it the solomon way - using project Widget_jpd. Solomon Project ID = UNSW0108001

We need to copy the UID into a particular field. (PS TUID - text 40). Just use copy/paste to copy the UID of all bottom level task UID's to the PS TUID field. (no milestones or rollups).

Save. Press "Synchronize project with Solmon" button.

Project now appeared in the project list.

Now went into Solomon and brought up project maintenace Was unable to open project as it was checked out.

Closed MS Project Server version and then went back into Solomon and now we could open it.

Note - if you have project opened in Solomon (e.g. project maintenance) then from the MSP the project is locked by "Administrator". This was probably the previous issue.

We have to do budget Now. (Sam Sharp's program should have done this).

---- Need at this point, a budget report from MSP giving us the details we need to put in.

Use Solomon->Project Budgeting->Budget Revision Maintenance Select Project Revision Number Post Period - 07/2008 (Unclear on this) Preparer - JPD Approver - SCB Start Date/End date - as appropriate. REv Type -> New Amounts Update Type - Orig Budget Only. STatus - In Process

For each task. Put UID into "Revision Task" field Select account Category (DIRLAB/MATERIALS) Set "Budget Amount" to the right value. Save.

BUT - When we looked the task from Business portal at this point, we found the information already there from the MSP server. This we found in Project Analyst. This view appeared to be looking at the MSP stuff. But this information was not in the Solomon budget.

How to be able to use the "Import From File" button to import stuff from flat field produced by Sam Sharp's tool.

Use Solomon->Project Budgeting->Budget Inquiry and Analysis

Note - solomon rounds the cents in this screen.

Use Solomon->Project Budgeting->Budget Revision Maintenance Select Project Revision Number

Set "Status" to "Completed" and save.

Sam should not have been able to do Use Solomon->Project Budgeting->Budget Review & Approval.

Sam could not do this.

William was able to do this, putting in Sam's name.

"View Detail" gives the Budget Inquiry and Analysis screen.

Sam tried to do this with Business Portal. Project Communicator - Message Available. Just takes Sam to Solomon, still can't do it.

Decided to have William approve John's schedule's budget using Budget Review & Approval.

Also rejected his own one.

Press "Begin Processing".

Project Controller->Project Maintenance set "Status" to "Active". (This is now possible due to budget being approved".

Also ensure that

WARNING-> If projects don't appear in timesheet entry, ensure project is active.

-- TonyFarrell - 03 Apr 2007

Edit | Attach | Watch | Print version | History: r7 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2007-04-03 - TonyFarrell
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback