At some point in the history of the project the department code was changed.  You do need to map both lines on the crosswalk, but you should map them both to the same Quantum Account Combo, using the correct Org.  This will consolidate the history.

In order to “let a project die” you should address the net asset balance, if any, to close it out in PeopleSoft.  You can then crosswalk this project id to a Quantum account combo using a similar source (one of the revolving sources if it is a revolving project or a State source if it is a state project).  It can be a Quantum account combo that you are using for another project.

A list of functions and their definitions are included on the Quantum website.  The expenses being recorded should fall under those definitions.  If the use of the project id has not changed, the defaulted values are probably fine, but it wouldn’t hurt to review the activity and the function assigned.  Function is similar to the current programs in PeopleSoft.

If there is no activity in that project/fund combination for FYs 16 – 19 in RAVEN, you will not see it in the crosswalk.

12/11/18 Update: The crosswalk logic has been adjusted to include projects that were created in FY 19, even though they have no activity. If you complete the crosswalk now for those new projects, it will allow transactions to be properly mapped into Quantum if they post before conversion.

For the projects that exist at this time, you will not have to complete the crosswalk again before go-live. As long as you are satisfied with the mapping you do now, it will be carried forward into Quantum.  The crosswalk tool will continue to be available up to a yet to be determined blackout period that will occur immediately before go-live, with a short period of “view only” access during the validation and conversion process, beginning 12/17/18.  For new projects or corrections of the decisions you make now, you will be able to use the crosswalk to complete the Quantum mapping then.

The project ID may have existed when we initially populated the crosswalk table, but it did not yet have transactions.  The transactions hit later and after the weekly sync of the crosswalk table, the project ID will now appear in the crosswalk.

12/11/18 Update: The crosswalk logic has been adjusted to include projects that were created in FY 19, even though they have no activity. If you complete the crosswalk now for those new projects, it will allow transactions to be properly mapped into Quantum if they post before conversion.

The list should be sent to Lynn McGinley as a spreadsheet with only two columns containing segment value and segment description. Descriptions cannot be longer than 50 characters. There must be no skipped lines or column headers/subheaders. The load process will not complete if it gets to a blank row.

No, user access in RAVEN will not transfer into Quantum.  The roles assigned to users in Quantum will be decided by the users’ departments and communicated for set up via an online web form.

No, the Reviewed box on the crosswalk table is provided for your tracking purposes only.  You can choose how you use it for your own validation purposes.

For the purposes of converting historical balances, we are not able to convert a single eUMB project to multiple Quantum Account Combinations.  However, during this process you may identify that you may want to track similar post go-live transactions in multiple Quantum Account Combinations.  You should pick one of those Quantum Account Combinations for the crosswalk and make a note of the other combinations to request later.  The Quantum Account Combinations identified in this crosswalk table will automatically be available for transaction coding after the system goes live.  Before Quantum goes live, you will be asked to identify the other combinations you will require for coding transactions in Quantum.

The Project Status codes used in the crosswalk are O = Open, C = Closed, R = Re-open, P = Pre Award, and 9 = 90 Day.