Custom XB vs. Baseline XB

Last Known Custom XB Changes Were Made in Spring 2010

Status

ASSESSING

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

key	summary	type	created	updated	assignee	priority	status	resolution

Loading...

Refresh

On this page

Global

Custom WHERE filter

For as long as these fake courses exist on SSASECT(SSBSECT) we will have to keep custom.

Will not pull SCBCRSE_SUBJ_CODE = ('CLEP', ‘TRNS’, ‘AP’, ‘AML1’, ‘CAR1’, ‘BB’. ‘CED1’, ‘CER1’, ‘HFW1’,'MED1’) and will not pull 'LIBR490AB' in XB_COS

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.

XB01

Can use baseline if Warning below is heeded.

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.

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’

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 more manual data entry than catalog level.

Out of compliance with this. Or at least, less accurate than the CO perhaps intended.

Custom Logic

cos_sv_mis_xb_bp.f_get_cvu_stat

  IF lv_inst_meth in ('50','51','52','53','54','61','62','63','64','71','71','72') OR
      lv_inst_meth like 'O%'  OR
      lv_inst_meth = '00' OR
      lv_inst_meth like 'V%' THEN
      CLOSE inst_meth_c;
      RETURN 'X';

Custom code references Instructional Method SSBSECT_INSM_CODE and returns “Unknown whether distance education session was developed by a CVU-trained instructor.”

Assessed 5/22 and Instructional Methods listed are still valid.

Baseline Logic

sv_mis_xb_bp.f_get_cvu_stat

Grabs SSRATTR_ATTR_CODE from SSADETL (can be inherited from SCADETL) and reports that.

GVATRMP does not seem capable of crosswalking values.

XB11

Can use baseline if XB01 Warning is heeded.

Custom

cos_sv_mis_xb_bp.f_get_wsch

STVACCT_CODE = lv_acct_mth = 'W' OR lv_acct_mth = 'L' OR lv_acct_mth = 'WE' then returns the sum of SSRMEET_HRS_WEEK for CRN and TERM, else return default 8888.88

Custom Code

FUNCTION f_get_wsch( p_acct_code STVACCT.STVACCT_CODE%TYPE,
                     p_crn       SSBSECT.SSBSECT_CRN%TYPE,
                     p_term      STVTERM.STVTERM_CODE%TYPE )
  RETURN VARCHAR2
IS
  lv_wsch               NUMBER:=0;
  lv_acct_mth           STVACCT.STVACCT_CODE%TYPE;

  CURSOR ssrmeet_c( p_crn        SSBSECT.SSBSECT_CRN%TYPE,
                    p_term_code  SSBSECT.SSBSECT_TERM_CODE%TYPE
                  ) IS
    SELECT *
      FROM ssrmeet
     WHERE ssrmeet_crn = p_crn
       AND ssrmeet_term_code = p_term_code;

BEGIN
  -- Get Accounting Method
   lv_acct_mth := f_get_acct_mthd(p_acct_code);

  IF lv_acct_mth IS NOT NULL AND
     ( lv_acct_mth = 'W' OR
        lv_acct_mth = 'L' OR lv_acct_mth = 'WE')
  THEN
    -- Calculate WSCH according with Chris' tech specification
    -- you need a cursor to get the ssrmeet rows using the crn, and term

    FOR lv_ssrmeet_rec IN ssrmeet_c(p_crn, p_term) LOOP
      -- lv_wsch   := NVL( NVL(lv_ssrmeet_rec.ssrmeet_hrs_week, sv_acad_calendar_bp.F_Calc_weekcontact_Hrs ( lv_ssrmeet_rec)),0) + lv_wsch;  -- C3SC Mod  JR 08/01/2007
      lv_wsch   := NVL(lv_ssrmeet_rec.ssrmeet_hrs_week, 0) + lv_wsch;  -- C3SC Mod  JR 12/05/2007
    END LOOP;
    RETURN (lv_wsch);
  ELSE
    RETURN 8888.88;
  END IF;

END f_get_wsch;

Baseline

sv_mis_xb_bp.f_get_wsch

STVACCT_CODE = lv_acct_mth = 'W' OR lv_acct_mth = 'L' then returns the sum of SSRMEET_HRS_WEEK for CRN and TERM, else return default 8888.88

Baseline Code

FUNCTION f_get_wsch( p_acct_code STVACCT.STVACCT_CODE%TYPE,
                     p_crn       SSBSECT.SSBSECT_CRN%TYPE,
                     p_term      STVTERM.STVTERM_CODE%TYPE )
  RETURN VARCHAR2
IS
  lv_wsch               NUMBER:=0;
  lv_acct_mth           STVACCT.STVACCT_CODE%TYPE;

  CURSOR ssrmeet_c( p_crn        SSBSECT.SSBSECT_CRN%TYPE,
                    p_term_code  SSBSECT.SSBSECT_TERM_CODE%TYPE
                  ) IS
    SELECT *
      FROM ssrmeet
     WHERE ssrmeet_crn = p_crn
       AND ssrmeet_term_code = p_term_code;

BEGIN
  -- Get Accounting Method
   lv_acct_mth := f_get_acct_mthd(p_acct_code);

  IF lv_acct_mth IS NOT NULL AND
     ( lv_acct_mth = 'W' OR
       lv_acct_mth = 'L' )
  THEN
    -- Calculate WSCH according with Chris' tech specification
    -- you need a cursor to get the ssrmeet rows using the crn, and term

    FOR lv_ssrmeet_rec IN ssrmeet_c(p_crn, p_term) LOOP
      -- lv_wsch   := NVL( NVL(lv_ssrmeet_rec.ssrmeet_hrs_week, sv_acad_calendar_bp.F_Calc_weekcontact_Hrs ( lv_ssrmeet_rec)),0) + lv_wsch;  -- C3SC Mod  JR 08/01/2007
      lv_wsch   := NVL(lv_ssrmeet_rec.ssrmeet_hrs_week, 0) + lv_wsch;  -- C3SC Mod  JR 12/05/2007
    END LOOP;
    RETURN (lv_wsch);
  ELSE
    RETURN 8888.88;
  END IF;

END f_get_wsch;

Custom XB vs. Baseline XB

Global

Custom WHERE filter

XB01

Custom Logic:

Baseline Logic

XB10

Custom Logic

Baseline Logic

XB11

0 Comments