What/How it runs
WIM, weekly Friday at 6:00PM, linclife.kni, linclife.knx


Parent process
?


Child process
?


Input system/files
Lawson tables


Output system/files
common\LAWSON\linclife.csv
E:\Kronos\IFC\LincLife\Forrestgh.xls


Automation
SFTP connection, it needs a private key (in crypto folder) and a 
public key which lfg.com has to load on their side


ARCHIVE
none


Hard Coding
"EMPLOYEE"."COMPANY"=10  AND  NOT ("EMPLOYEE"."EMP_STATUS"='T3' OR "EMPLOYEE"."EMP_STATUS"='T4' OR "EMPLOYEE"."EMP_STATUS"='T5'
 OR "EMPLOYEE"."EMP_STATUS"='T6' OR "EMPLOYEE"."EMP_STATUS"='T7' OR "EMPLOYEE"."EMP_STATUS"='T9' OR "EMPLOYEE"."EMP_STATUS"='00');
lotsa lookup tables, better check it out
lotas SQL in variables
email address in send mail bat file


Contacts
Lawson Team, Hope
Sam.Glassley@lfg.com


DOWNTIME
Just re-run it.  You probably need to let lfg know you sent the file late or may be a day or two
 before it loads on their side.
Not sure if they ingest the file immediately, so not sure if it can be rerun.

NOTES:
From: Jordan, Hope 
Sent: Wednesday, July 03, 2019 11:04 AM
To: Pierce, Deborah; Peterson, Ruth
Subject: RE: Optional life spouse coverage

All employees that are not a term final or a 00 status go in the file.   then for the different fields in the file this is the way it is populated.   So it looks like when the status changes it will put a stop date in the file for 60 days  then after that the record is still there but all the data is blank.  So looks like they should be sending out information based off the stop date of the plan and it looks like we give them 60 days to do that.  


Life benefit  amount is populated WHERE  V_BENEFIT.PLAN_CODE in ('LFC')
and ((to_char(V_BENEFIT.stop_date,'YYYYMMDD'))  = 17000101 OR
(V_BENEFIT.STOP_DATE > current_date-60))

Addamont, adddate, addterm    and is populating the start and stop dates from benefit. 
WHERE  V_BENEFIT.PLAN_CODE in ('ADDC')
and ( (to_char(V_BENEFIT.stop_date,'YYYYMMDD' )) = 17000101 OR(V_BENEFIT.STOP_DATE>current_date-60))

Optlifeamt, oplifedate, oplifeterm is populating the start and stop dates from benefits.
WHERE  ("BENEFIT"."PLAN_CODE"='LFO')  
and ( (to_char(BENEFIT.stop_date,'YYYYMMDD' )) = 17000101
OR(BENEFIT.STOP_DATE>current_date-60))

Optspouseamt, optspousedate, optspouseterm is populating the start and stop dates from benefits.
WHERE  ("BENEFIT"."PLAN_CODE"='LFOS') 
  and ( (to_char(BENEFIT.stop_date,'YYYYMMDD' )) = 17000101
  OR(BENEFIT.STOP_DATE>current_date-60))

Optdepamt, optdepdate, optdepterm is populating the start and stop dates from benefits.
where V_BENEFIT.plan_code in ('LFOD')
  and ( (to_char(V_BENEFIT.stop_date,'YYYYMMDD' )) = 17000101
OR(V_BENEFIT.STOP_DATE>current_date-60))