1 / 30

Session RE-2 MIS Reporting in Banner CALB - Key Points & Troubleshooting TJ Baugus – California Community Colleges

Session RE-2 MIS Reporting in Banner CALB - Key Points & Troubleshooting TJ Baugus – California Community Colleges Solution Center (3CSC), SunGard High Education. MIS Reporting and Banner Baseline. MIS Reports – The CCCCO required reports for submitting statistical data.

lindsay
Download Presentation

Session RE-2 MIS Reporting in Banner CALB - Key Points & Troubleshooting TJ Baugus – California Community Colleges

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Session RE-2 MIS Reporting in Banner CALB - Key Points & Troubleshooting TJ Baugus – California Community Colleges Solution Center (3CSC), SunGard High Education

  2. MIS Reporting and Banner Baseline • MIS Reports – The CCCCO required reports for submitting statistical data. • Banner baseline – Includes a group of COBOL process to create these reports. • Completely replaced by CALB MIS reports (all except EB and EJ) with new processes • No longer maintained

  3. MIS Reporting in Banner CALB • REPT – Report Engine • 3CSC reporting tool used to create reports • Install prior to CALB • CALB – California CC Baseline • CALB MIS created via the Report Engine • CALB install adds MIS report definitions in REPT • User can modify the provide reports (Copy!)

  4. Running CALB MIS Reports • CALB Handbook Chapter 5 • GVAREPT Report Engine Run Form to create the “extract” and “transform” XMLs. • “Two-steps” in CALB 7.4.2 and prior • Major redesign: “One-step” in CALB 7.5 beta • GVPREPT Report Engine Generate Report File C3SC job to create the file submitted to CCCCO. • “Last step” • Output files (.lis and .ext) are not XML.

  5. GVAREPT – Up to CALB 7.4.2 • GVAREPT form. • Report name: CB • Resource Path for Transform – If it does not default, get it from your DBA or IT Staff. • Report parameters for Extract • District ID and “period” (Term or Year) • May include dates or other parameters • Submit Extract (locks session) • Submit Transform (if no error on extract; locks session)

  6. GVAREPT form – Up to CALB 7.4.2

  7. GVPREPT – All CALB Versions • Job accessed from GVAREPT Options menu (opens with Parameter Set) or directly. • Parameters (defaulted by Parameter Set) • Report Name: CB • Extraction Number: Null uses last successful extracted-and-transformed number. • File Name: CB.ext; file in jobsub directory you’ll submit to CCCCO. (The .lis is “human friendly” and notes GVAREPT Extract parameters.) • Generate XML File: Extra report documentation.

  8. GVPREPT job – All CALB Versions

  9. GVAREPT – CALB 7.5 forward • Major redesign of GVAREPT in CALB 7.5 beta • One submit creates both extract and transform XMLs • Executed in background as Oracle jobs (User session not locked!) • Improvements in performance (transform) • Two tabs: submission and status • GVPREPT – Fixed O/S system specific error

  10. CALB 7.5 GVAREPT Job Submit tab

  11. CALB 7.5 GVAREPT Job Status tab

  12. XML files: Extract and Transform • How will the typical end-user/functional-user use the XMLs? They probably won’t. • Technical-users • Troubleshooting • If you can read XML… • Extract will show the raw Banner data selected. (CB report’s raw Subject and Course data) • Transform will show how the Extract data is formatted for MIS. (Subject and Course  CB01 element)

  13. GVPREPT Output Files • “Human friendly” .lis (GJIREVO) • CCCCO-submitted .ext (jobsub directory)

  14. Extract Error: “no data found” • Most common: GTVDICD and STVCAMP • GTVDICD District Division Code Validation must list district/college IDs (GI01, even if only one). • STVCAMP Campus Code Validation must link the campuses (even if only one) to the district/college IDs. • Without this, all reports will hit the “no data found” (all except CB).

  15. Extract Error: “no data found”

  16. Extract Error: “no data found” • Other reasons: Missing key data setups (new fields to CALB or not) that satisfy report domain. • A report’s “domain” is the SQL statement defined on GVARSQL Report Engine SQL Form that represents the CCCCO report domain. (Technical-user can edit copied reports; do not edit provide reports!)

  17. CB Course Report Domain (part 1) • For the report term, the course is... • active for the term by its SCABASE Course Base Maintenance.

  18. CB Course Report Domain (part 2) • (and) active by its SCACRSE Basic Course Information Status (SCBCRSE_CSTA_CODE) and its status' STVCSTA Course Status Code Validation Active indicator (STVCSTA_ACTIVE_IND). (Defect 1-29DXYG CALB 7.4.1)

  19. CB Course Report Domain (part 2)

  20. CB Course Report Domain (part 3) • (and) on SCASRES Catalog Schedule Restrictions the course either 1) is not setup at all or 2) [is not excluded / is included] for the reported district ID's campus(es). (Defect 1-3CLM15 patch after CALB 7.4.2) • For Exclude, all campuses for the district ID must be listed in order to exclude that course from the district ID's report. • For Include, at least one of the campuses for the district ID must be listed in order to include that course on the district ID's report.

  21. CB Course Report Domain (part 3)

  22. CB Course Report Troubleshooting • To resolve problems with CB data: • Select one course. • Review the points above to see if this course appears to meet all of the requirements. • If you do not see a fix to the course or data, create an Service Request and attach print screens of the forms noted above. (Include GVAREPT/GVPREPT errors or output.)

  23. Future FAQ • FAQ in the works that will define the domain for all of the CALB MIS reports. • States in English the domain and provides print screens of the related forms highlighting the fields used.

  24. Other 3CSC FAQs • Optional scripts to load seed data (valid values; validation tables): FAQ 1-2IIA5D • Also listed in CALB Handbook Chapter 5 • Optional scripts list (some are mandatory but manually executed): FAQ 1-3L0SN3 • FAQs are on the UDC customer support site: http://connect.sungardhe.com

  25. Other Setup Scripts • Review the Release Guide, the Install instructions, and the Handbook carefully. • GTVSDAX setup scripts (CALB Handbook Chapter 5 Setup Scripts) • Residency address • CalWORKS for SB27 (obsolete unless resubmitting an old report) • BOG Waiver detail code (possible future obsolete) • TBA Meeting code (future obsolete)

  26. Setups on GVATRMP Form • GVATRMP Report Engine Map Values Form: Used to “map” Banner values to MIS values. • Example: SB09 for USA state and possessions conversions (‘CA’ = ‘50000’). • Should review this form for all elements of the reports and adjust the Banner Value list to your valid values. (Insert more if needed.) • CALB Handbook Chapter 5 notes for each report

  27. SM03 on GVATRMP Form

  28. CALB New Fields/Columns • Review the Release Guide and Handbook for new fields (or relabeled fields). • If it looks familiar for MIS, probably is for MIS. • Example: SCACRSE Basic Course Information form new field Credit Status • Separated from Approval field for CB04 Course-Credit-Status (impacts other elements, too) • Script to populate: mis_scbcrse_update.sql

  29. SCACRSECredit Status

  30. MIS Reporting in Banner CALB QUESTIONS?

More Related