isupport Case Management Project Accrual Accrual Batch Processes Design Specification Document isupport Daily Accrual Batch Processes

Transcription

1 isupport Case Management Project Accrual Accrual Batch Processes Design Specification Document isupport Daily Accrual Batch Processes Version No: 2.0 February 22, 2016

2 Revision History Revision Date Version No. Updated By Requested By Description of Revision 06/11/ Protech Solutions Inc., isupport Initial Version 22/02/ Protech Solutions Inc., isupport Corrected the wrong execute statement in Scenario2. Page - 2 Last Updated: Feb 22, 2016

3 Table of Contents 1. Daily Accrual Batch Process Purpose Process Description Execution Frequency Dependencies Predecessors: Successors: Restart Procedures Instructions if Job is skipped Input File(s) File Layout Mapping table Output File(s) File Layout Mapping table Job ID Program... 8 Page - 3 Last Updated: Feb 22, 2016

4 1. Daily Accrual Batch Process 1.1. Purpose The Daily Accrual Batch Program processes open cases with open obligations (where the obligation end date is equal to or greater than the current date). The program will take each obligation due for accrual and accrue for the period specified on the obligation by means of the frequency. The VLSUP table will be updated with the new charge amount towards the current support owed Process Description This batch will process each obligation due for accrual, and charge for the next accrual period specified on the obligation based on the frequency. For Weekly obligations, the accrual occurs on the same day of the week, for each week during the month. For Bi-Weekly obligations, the accrual occurs every alternate week on the same day. For Semi-monthly obligations, the accrual occurs on the obligation effective date (of each month) and then 15 days thereafter. For Monthly obligations, the accrual occurs on the same date each month. For Annual obligations, the accrual occurs on the same day of every year. For Quarterly obligations, the accrual occurs on the same day of every 3 month. For Half yearly obligations, the accrual occurs on the same day of every 6 month. Accrual won t happen for one time obligations like Instalments and Lump sum. Future dated obligations will be selected by the batch process when the day reached or passed. The procedure processes all open cases that meet the following conditions: Must have at least one active obligation of any below: AR - Arrears Page - 4 Last Updated: Feb 22, 2016

5 HI - Health Insurance IN - Interest OP - Other Payments RM - Retroactive Maintenance SF - School Fees SM - Support Maintenance I1 - Instalment1 I2 - Instalment2 I3 - Instalment3 I4 - Instalment4 I5 - Instalment5 I6 - Instalment6 I7 - Instalment7 I8 - Instalment8 I9 - Instalment9 LS - Lump Sum The next accrual date on the obligation records must be equal to the process date i.e. DT_ACCRUAL_NEXT = DT_RUN Process date should fall between begin and end date of the obligation. The accrual process runs daily if for some reason, the process was skipped, the process accrues for each of the skipped days sequentially, up to and including the current date. EXAMPLE: If the current date is 12/29/2015 and the accrual program last ran on 12/26/2015. The program will run for cases and obligations that meet the accrual criteria beginning on 15/27/2015, accrue for all eligible obligations and then set the next accrual program run date to 01/28/2014, accrue for all eligible obligations for that day and continue up to the current date. Updates will be made to VLUSP and VOBLE tables for each individual day. The accrual process automatically charges when the future effective date becomes current. The MSO is calculated by the Month Support Batch Process, if any of the charge dates fall within the month. For each selected obligation in the above steps, the program will do the following: Page - 5 Last Updated: Feb 22, 2016

6 o The system will generate a Global Sequence ID using SP_GENERATE_SEQ The accruals for case obligations can be viewed from the FDMO event log grid (FDMO Monitor Funds) screen the Global Sequence ID is used to identify the accrual for each individual day. All obligations, which accrue on the same day, will have the same Sequence Event Global ID. o The latest balances (as of accrual run date) for each obligation is obtained from VLSUP table by passing the Obligation Key (Case ID, Sequence Order, Member ID (i.e. Actor ID) and Sequence Obligation). o The accrued amounts in current support, new balances, Sequence Global Event ID, are then inserted into the VLSUP table. o The next accrual date is then calculated as described below using the ACCRUAL procedure: When the frequency is monthly, the Date Accrual Next is obtained by adding one month. When the frequency is bi monthly, the Date Accrual Next is obtained first by the obligation effective date and then by adding 14 days. When the frequency is weekly, the Date Accrual Next is obtained by adding 7 days. When the frequency is bi weekly, the Date Accrual Next is obtained by adding 14 days. When the frequency is annual, the Date Accrual Next is obtained by adding 12 months. When the frequency is quarterly, the Date Accrual Next is obtained by adding three month. When the frequency is half yearly, the Date Accrual Next is obtained by adding six month. If Next Accrual date is greater than the end date of the obligation Then High Dates (12/31/9999) is updated in the Date Accrual Next field of VOBLE table to skip the further accrual in future. Page - 6 Last Updated: Feb 22, 2016

7 1.3. Execution Frequency Daily 1.4. Dependencies Predecessors: Batch Update VPARM date ( DAILY - BATCH_UPDATE_VPARM_DATE.SP_UPDATE_PARM_DATE) Successors: On month end day: MSO Month Support Batch Job - (ISB SPKG_BATCH_MONTH_SUPPORT.SP_BATCH_MONTH_SUPPO RT) Note: On month end day, after execution of Daily Accrual batch job, MSO Month support batch job must be executed in isupport Restart Procedures Restart the job from the beginning Instructions if Job is skipped Job cannot be skipped Input File(s) NO NAME OF THE FORMAT TRANSFER MECHANISM LOCATION N/A N/A N/A N/A N/A N/A ESTIMATED SIZE (IN MB S) Page - 7 Last Updated: Feb 22, 2016

8 File Layout FIELD NAME POSITIO N LENG TH TYPE C-CHAR D-DATE N- NUMBER FORMAT / DEFAULT VALUE N/A N/A N/A N/A N/A N/A DESCRIPTION Mapping table N/A SOURCE N/A TARGET 1.8. Output File(s) NO NAME OF THE FORMAT TRANSFER MECHANIS M LOCATION N/A N/A N/A N/A N/A N/A ESTIMATED SIZE (IN MB S) File Layout FIELD NAME POSITIO N LENG TH TYPE C-CHAR D-DATE N- NUMBER FORMAT / DEFAULT VALUE N/A N/A N/A N/A N/A N/A DESCRIPTION Mapping table SOURCE N/A N/A TARGET 1.9. Job ID Program ISB BATCH_FIN_ACCRUAL.SP_BATCH_ACCRUAL_DAILY Page - 8 Last Updated: Feb 22, 2016

9 These batch jobs can be scheduled in the scheduler to run daily or as per the frequency set for each batch in VPARM table Instructions to run the job manually (From SQL window / command prompt): The Accrual Job should be executed after executing the DAILY- BATCH_UPDATE_VPARM_DATE.SP_UPDATE_PARM_DATE job. This batch sets the run date (execution date) for the day. Scenario1: If system date is same day of batch execution. 1. EXEC BATCH_UPDATE_VPARM_DATE.SP_UPDATE_PARM_DATE; 2. EXEC BATCH_FIN_ACCRUAL.SP_BATCH_ACCRUAL_DAILY; Scenario2: If system date is not the same day of batch execution (in case of holidays the input parameters should set as below. Date format should be YYYYMMDD.) 1. EXEC BATCH_UPDATE_VPARM_DATE.SP_UPDATE_PARM_DATE ('DAILY', 'YYYYMMDD', 'BATCH'); 2. EXEC BATCH_FIN_ACCRUAL.SP_BATCH_ACCRUAL_DAILY; -----End----- Page - 9 Last Updated: Feb 22, 2016