1. Query Builder Reporting from Production

2. Database Structure Each application has 2 Oracle Schemas FAST(appname) and FAST(appname)_QUERY FAST Student  FASTSTU, FASTSTUDENT_QUERY; FAST Finance  FASTMCSL, FASTFINANCE_QUERY; FAST HR  FASTHR, FASTHR_QUERY; FASTBUDGET  FASTBUDGET, FASTBUDGET_QUERY; …. All baseline objects for the application exists in the non Query schema Query Builder access is through the Query schema only Buy default the Query schema has very little access

3. How does Query Builder Access work Query Object Access This page allow you to grant access to baseline objects

4. But what about Non-Baseline Objects You can access any production object that is part ERP system that your FAST application was built to support FAST Fiannce  FIMSMGR objects FAST Student  SATURN objects …. Access to these objects needs to be granted to the Query schema Several different ways to accomplish this Can depend on IT support Institutional guidelines

5. Ways to access Non-Baseline Objects Create a new dblink directly in the Query schema Needs DBA support Easy keep track of what non-baseline objects are being used More work keeping track of multiple accounts and access Set up a dblink using the FASTMCSL user in the Query schema Needs DBA support Access to all objects FAST has already been granted Less maintenance Use existing objects but the Query schema access to them No DBA support but will be limited to only the objects FAST already uses

6. FAST Baseline App FAST Baseline App Query Baseline Reports Custom Reports Production FASTMCSL dblink Query dblink (may just use FASTMCSL dblink) This must be created in the Query Schema of the application you are working in

7. We have access now what? You can now access the production objects by using the fully qualified path i.e. SATURN.SPRIDEN@[dblink_name]SATURN.SPRIDEN@[dblink_name This can be used directly in the Query Builder Or you can create a synonym for this object and then use that i.e. CREATE SYNONYM PSYNSPRIDEN for SATURN.SPRIDEN@[dblink_name]SATURN.SPRIDEN@[dblink_name You can now use the synonym name in the Query Builder