Internal: Running the ProSystem fx Engagement to Engagement Manager conversion
Internal use only
The conversion utility can be downloaded from Engagement Manager, go to
Setup
, then Downloads
.If you're assisting with an Engagement Manager implementation for a firm that uses ProSystem fx, refer to this PDF guide for instructions.
Check also: Conversion assistance call guide.
Post-conversion report location
If you encounter difficulties after the conversion is finished, the data conversion from ProSystem fx Engagement to Engagement Manager creates a report for each engagement converted. The Data Conversion report lists certain modifications made during the conversion process, such as truncations, abbreviations, and so on.
Most items in the report are informational and don’t require immediate attention. However, it can be helpful to look at. To access the report, locate and open YYYYYY.html, where YYYYYY is the binder name. The report is placed in the user's Documents folder.
Get a ProSystem fx Engagement binder
If you need to get the ProSystem fx Engagement binder for development to try the conversion, set up a secure file exchange for the firm out on MKT Web Tools after you sign in at http://mkt/default.aspx?Individuals. Have the firm create a "binder package" to send to you using the following steps:
- Open the Workpaper Management module and highlight the client in the Local File Room.
- Highlight the engagement in question.
- Go toTools, thenCreate Binder Package.
- Choose the optionsInclude All WorkpapersandSave Package To A File.
- Browse to a convenient location, then selectOK.
This will create a file with a .AZP extension.
Don’t go to File/Backup because development won't be able to restore that file.
Internal: Hidden features in the conversion utility
Internal use only
Below is some information about additional features available in the conversion utility.
important
Before doing these steps, you must contact a senior consultant and enter a walk-up ticket to obtain permission.
Overriding the open Word and Excel processes warning
If you see a window displayed that says "Running Excel and Word processes were detected. These programs interfere with the conversion and should be quit before the conversion begins. Close both applications, and then restart the conversion."
Press Ctrl + Alt + O on the keyboard to override the warning and continue the conversion.
This warning is in place to prevent Microsoft Word and Excel documents from opening when the conversion is running. If you're running the conversion on a standalone workstation, use the Task Manager to locate the WINWORD.EXE, and EXCEL.EXE processes and end them.
Hidden files for alternate data locations
By default, the conversion utility looks for data in 3 locations:
- The SQL instance is named XXX\PROFXENGAGEMENT where XXX is the name of the computer that has the Local File Room. We pull the Trial Balance and the balances from here, among other things.
- The physical location where the workpapers actually exist. By default, \Pfx Engagement\WM\Workpapers. You'll need to go down a couple more folders to get at the actual files because they need to have GUIDs associated.
- The MDB files in the \Pfx Engagement\WM location that contain the tax codes.
Conversion utility and SQL instance with the Local File Room are not in the same place.
If you can't install the conversion utility on the same machine where the Local File Room exists (such as a terminal server installation), use the following steps:
- Go to \Program Files\CSIConvert\Enagement Manager.
- In the Engagement Manager folder, create a file called internal.csiconv.
- Run the conversion utility.
- You should see a new window letting you select which Local File Room you want to use (the selections display any machine with a PROFXENGAGEMENT instance).
note
- The conversion utility will expect the workpapers and tax codes to be at the default locations on the chosen machine.
- You will need sufficient permissions on your machine to access the other machine that has the Local File Room. Generally, the user will need local Admin rights to that SQL server. If permissions are not sufficient, you will see a window that says "an error occurred during authentication" or "authentication failed...exiting."
- The path to the Pfx Engagement folder must be shared so that it can be accessed from a remote (different machine) location. You should see a pop-up in the conversion process saying this.
Workpapers physically reside in a non-default location.
Use the 2nd hidden file to adjust where the conversion utility looks for the workpapers.
- Go to C:\Program Files (x86)\CSIConvert\Enagement Manager.
- In the Engagement Manager folder, create a file called internal_wp.csiconv.
- Run the conversion utility.
- You'll see a new window box asking you to set the location of the workpapers files. You will need to enter the location including the 1st GUID folder in the Workpapers folder (which is the GUID for the current user in the Local File Room).
Other considerations
The path to the tax codes can't be changed. If an alternative path is being used, you will need to create the default path and copy the MDB files over.
You can use both of the hidden files together. Here is an example of when you might need to:
An example of when you would use hidden file 1 and hidden file 2 together is if a firm wants to install the conversion to a Terminal Server that ProSystem fx Engagement doesn't exist on. The SQL instance of ProSystem fx exists on a data server (data server1) and the workpapers exist on a separate data server (data server2).
Hidden file 1 would allow you to point to the alternative SQL instance (data server1) and hidden file 2 would allow you to point to the workpaper location (data server2). If you set up a network location on the Terminal Server to data server 2, we’ll populate this hidden file window 2 with this path. You can always just manually populate the path.
