| Info |
|---|
Last Known Custom XB Changes Were Made in Spring 2010 |
GVARSQL - shows the SQL used on Custom
Status |
| ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Owner | Scheduling Coordinator | ||||||||||||
Contributors | |||||||||||||
Goals | Assess the difference between Baseline and Custom XB reports. Assess deficiencies w/ Custom Report and recommend implementation of Baseline Business Practices. | ||||||||||||
Jira tickets |
| ||||||||||||
On this page |
|
Global
Custom WHERE filter
...
| Code Block |
|---|
AND A.SCBCRSE_SUBJ_CODE NOT IN
('CLEP','TRNS','AP','AML1','CAR1','BB','CED1','CER1','HFW1','MED1') -- COS change ADDED
AND (SCBCRSE_SUBJ_CODE || SCBCRSE_CRSE_NUMB <> 'LIBR490AB')
--COS Above 2 lines added |
- Jordan Lamb Ask Daniel Alvarado if any
SCBCRSE_SUBJ_CODE= ('CLEP', ‘TRNS’, ‘AP’, ‘AML1’, ‘CAR1’, ‘BB’. ‘CED1’, ‘CER1’, ‘HFW1’,'MED1’) are still active on the catalog level. If not, then we can remove this line of code.
...
| Note |
|---|
STVACCT codes must begin with the XB01 value that is to be reported. Regardless of Baseline or Custom. Obsolete codes that do not follow this practice are a liability in reporting correctly. For example, the ‘XE’ codes. |
Baseline Logic
...
. |
...
Custom Logic:
cos_sv_mis_xb_bp.f_get_acct_mthd(SSBSECT_ACCT_CODE) ACCT_CODE
If SSBSECT_ACCT_CODE, XB01 = ' ‘, if SSBSECT_ACCT_CODE = ‘WE’ THEN XB01 = 'I’
SSBSECT_ACCT_CODE = ‘WE’ has been obsoleted for a long while.
Baseline Logic
XB01 uses the first character of SSBSECT_ACCT_CODE. STVACCT
XB10
- Would require a business practice change and decision from Academic Services on if it could be assessed on a catalog or section level. Section level requiring requires more manual data entry than catalog level.
...