Supplemental Data Engine

1. Supplemental Data Engine With an example application for Human Resources Prepared by Raj Doshi, Kern Community College District and Julie Monfette, SunGard Higher Education

2. Supplemental Data Engine Introductions • Raj Doshi is an HR Analyst • Kern Community College District • Julie Monfette is an HR Consultant • SunGard Higher Education

3. Supplemental Data Engine Resources General User Guide

4. Supplemental Data Engine Purpose The purpose of this session is to demonstrate a Banner Baseline functionality using the Supplemental Data Engine We will demonstrate it with an application in the Human Resources Faculty Administration module on PEAFACT: adding a field to allow for the recording and reporting of the Faculty Seniority.

5. Supplemental Data Engine SDE allows you to create additional fields associated with a specific Banner table but stored in a separate table called the Supplemental Data Table.

6. Supplemental Data Engine The new data is displayed in a popup window, the Supplemental Data Window, and is stored in a supplemental data table. Because no customization is needed. Supplemental data is generally not impacted by Banner upgrades. Each supplemental data record created through SDE is tied to a specific Banner table.

7. Supplemental Data Engine The Banner table’s unique key enables a specific record on the source table to be linked to a specific record on the Supplemental Data table.

8. Supplemental Data Engine In addition to specific set up forms, SDE uses the Supplemental Data Window, which does not appear on any menu. The SDE columns, after they have been set up, are displayed in the SDE window.

9. Supplemental Data Engine A user with the appropriate permissions can add or edit data on this window. The permissions in the SDE window match the permissions in the form displayed in the main Banner window. After this was set up at Kern CCD on the PEAFACT form, the staff could see a light bulb icon on the Banner toolbar indicating there is supplemental data to present.

10. Supplemental Data Engine

11. Supplemental Data Engine

12. Supplemental Data Engine

13. Supplemental Data Engine

14. Supplemental Data Engine

15. Supplemental Data Engine

16. Building SDE GTVSDTB Tables with Existing Supplemental Data Attributes Form. This lists Banner tables that are enabled for SDE. GOASDMD Supplemental Data Attributes Definition Form defines the attributes for supplemental data fields that will be displayed on the SDE window. GOADISC Supplemental Data Discriminators Form identifies discriminator codes for SDE, and defines the discriminator methods that will dynamically handle supplemental data.

17. Building SDE The first task is to find the attributes of the form on which you are creating the SDE field

18. Building SDE-GOASDMD

19. Building SDE-GOASDMD

20. Building SDE-GTVSDTB

21. Building SDE-GTVSDTB

22. Building SDE-GOADISC • GOADISC • Supplemental Data Discriminators Form identifies discriminator codes for SDE, and defines the discriminator methods that will dynamically handle supplemental data.

23. Building SDE-GOADISC Set up a new discriminator in the Supplemental Data Discriminators form GOADISC. There are different kinds of discriminators that give you different options. If you are creating a single SDE field, no discriminator is necessary.

24. Reporting SDE fields

25. Reporting SDE fields select * from GOVSDAV

26. Reporting SDE fields

27. SDE Limitations • There limitations of SDE as not all Tables, Blocks, and Forms Work with it. • Supplemental data can only be associated with tables; therefore, any form that relies on a view to display data cannot use SDE. • The security tables owned by BANSECR cannot be used with supplemental data.

28. SDE Self Service Generate DDL and create a view if you plan to use this SDE attribute in Banner Self-Service or in some other context that requires a view. Generate DDL code for the view in GOASDMD. Modify Self-Service if necessary. To make full use of supplemental data in Self-Service, custom modifications must be made in Banner Self-Service packages.

29. SDE short cut key stroke • Can be applied to allow the user to access the SDE window: • The Ctrl-D keystroke is a convenient way for users to show and hide the SDE window. • To enable this keystroke for users at Kern, add the following line to the fmrweb.res file in your $ORACLE_HOME/forms/java directory on your Oracle Application Server: 68 : 2 : "Ctrl+D" : 11022 : "Accelerator1"

30. SDE Inquiry and Delete Process SDE Inquiry and Delete Process GUSMDID This new process allows you to review and delete orphaned supplemental data records. Supplemental data records can become orphaned when their corresponding “parent” records in base Banner tables are deleted. Although the supplemental data record cannot be viewed after the parent record is deleted, it still exists in the Supplemental Data Table. This process provides an optional way to clean up these orphaned records.

31. SDE Inquiry and Delete Process SDE Inquiry and Delete Process GUSMDID The report output shows, for each record found, table name attribute name, primary key, and parent status.

32. SDE Inquiry and Delete Process SDE Inquiry and Delete Process GUSMDID The GUSMDID report does not show the actual values for each supplemental data record. To review the actual data, you can use supplemental data views for each attribute. Code to create these views can be generated in the Generate DDL block of the Supplemental Data Attributes Definition form (GOASDMD).

33. SDE Set Up Cheat Sheet Steps to create the SDE window: 1. Add the desired table the GTVSDTB form. 2. To add multiple, related supplemental data fields under a single SDE attribute. 3. Set up the attribute on the Supplemental Data Attribute Definition form GOASDMD. 4. Create a view to use this SDE attribute in Banner Self-Service or in some other context that requires a view. 5. Modify Self-Service if necessary. To make full use of supplemental data in Self-Service, custom modifications must be made in Banner Self-Service packages.

34. Supplemental Data Engine Questions?