Program Registration Enhancements

• In the child care module for table file setup, a sign up fee on a *FIXED basis may be specified.  When selling a program for this year the sign up fee is charged correctly, but when selling it for next year the fee was not charged at all.  Modifications have been made to always set the initial monthly/weekly fee equal to the table file sign-up fee amount when the sign-up fee calculation method is set to *FIXED.  This will only occur during the sale of a monthly/weekly program.     
• Program statistics:
  • Created a new 3^rd party column that is calculated by extracting 3^rd party amounts from the subsidy column.
  • Added logic to prevent age calculation errors when a member's birth date occurs after the begin date of the program for which the member has been registered or when the member's not been specified.
  • Build process to clear the program statistical datamart PGMSTAT1 and the associated log file PGM400LG every time the job is run.  This forces all counts and amounts to be recalculated allowing for inclusion of changes made to historical activities.  When selecting the Update Program Registration Statistics Datamart option, only log information from the last run will be available as a result of the files being cleared. 

• New *ACTIVESTS method has been developed as a means of testing a members membership status during the program registration sales process.  This value indicates that a member with an active full membership as of the current registration date may receive the FULL member pricing.
  • New parameter in the system parameter table file.
  • New status checking calculations when selling programs.
  • Eliminates the need to renew a membership.
• Fixed logic flaw in Program Master Table File that would cause program to load more records to the screen than it could hold.  Now possible to select options F6=Create and F4=Prompt.

Fixed logic flaw in Program Offerings selection which would cause error when displaying roster, details or waiting list from F9-Navigator, OF-Offerings, and View 2.  Passing a lower case parameter as opposed to the required upper case parameter caused this problem.