Buy@Duke Database Upgrade – May 14, 2016

Buy@Duke will be unavailable for use on Saturday, May 14, 2016 from 6:00 a.m. to 6:00 p.m. in order to upgrade the Buy@Duke database.  This database migration is part of larger SAP modernization effort that will take place over the next twelve months.

This database migration will NOT change the look of any Buy@Duke screens or change any processes related to creating and displaying shopping carts, approving shopping carts or displaying Purchase Orders.

The database migration will have an impact if a Buy@Duke user has personalized the selection criteria for any of the Report Queries shown below:

Or if a user has created a new custom Report Query (such as SC Created by JSMITH in the example below):

The database conversion will remove all user’s Custom Report Queries and remove the user’s personalization of selection criteria on System Standard Queries.  Only the Standard Report Queries and Standard Selection Criteria will be available after the database migration.

Buy@Duke users will need to recreate any Report Query personalizations that they want to continue using after the database migration is completed on May 14.

WE HIGHLY RECOMMEND that  anyone wanting to continue using existing personalized report selection criteria and/or Custom New Report queries make and keep a screen shot by May 13, 2016 to facilitate recreating the report after database migration beginning on Monday, May 16.

We apologize for the inconvenience caused by need to recreate any customized Buy@Duke reporting as a result of the database migration.  We thoroughly investigated options to preserve customized Buy@Duke reports, but were unable to come up with a centralized technical solution.

If you have any questions regarding the database migration and its impact on Buy@Duke, please contact the Buy@Duke helpdesk at 919-681-1872 or email procurementduke.edu. Attached are instructions to assist with recreating personalized report selection criteria and/or Custom New Report queries.