Child pages
  • uclaEmailEligibility

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • BOL: A person will have 'BOL' value in uclaEmailEligibility if he/she satisfies any of the following logic.
    • Logic 1: The Registrar's Office asserts BOL email eligibility for the person from student perspective by including his/her UID in the file ed_stu_aff.dat (formerly Focus Job SR0#V618 Report), which is generated by data in SR2 and tranferred transferred from RO to AIS ITS on a daily basis. To the best knowledge of AISITS, the file includes:
      • a. all students enrolled in the current term (grad and undergrad). Current term is the term until the next subsequent term starts based on quarter dates.
      • b. all students enrolled in the previous full term (grad and undergrad).
      • c. all students enrolled in the next full term (grad and undergrad).
    • Logic 2: The Payroll System (PPS) defines the person as current UCLA employee by stating EMP_STATUS = ('A', 'I', 'N', 'P') in table PP0PER AND LOCATION = '4' in table FF0DDP.
    • Logic 3: The UCLA Extension System (UNEX) claims the person as UNEX students concurrently enrolled in UCLA campus courses by including his/her UID in file ucla-edimi-dir-file-transmission-uclaunexconcurrents.txt, which is transferred from UNEX to AIS on a daily basis. To the best knowledge of AIS, the file includes UNEX students who has Petition_Status = 'Approved' or 'Pending' for the concurrent UCLA quarter only.
    • Logic 4: The ASUCLA Payroll System claims the person as current ASUCLA employee by including his/her ASUCLA ID in file EDFILE.txt with status of 'A' or 'L' sent to AIS on a daily basis.

...