Barclays-Claims Manager-MSGS Flow

M:\temp\rgeorge\documents\Barclay_ICM_payment message.xlsx

Daily imp	Stage	Stage desc	Depends on	Custom Function/Import rule	Scope/Activity	Details.	How/Where to check
MSGS	100	Housekeeping
MSGS	1000	Timelapse start
MSGS	1005	generating Auto Payments	1000	ProcessAutoPayments_Local()	Autopayment of ICM claims
MSGS	1500	Back population	1000	DoBackPopulations()
MSGS	2000	Skip Jobs SSI Imp if no source data found	1000	SkipImpJobsIfNoSourcedata()
MSGS	3000	Import SSI data	2000	CustJob_SSIIMP()
MSGS	3600	Call Output postings	1000	CallOutputPostings()	1. It generates posting messages for the APPROVED payadvices  - put pay messages in the M:\MERITRESEARCH\BARCAP_DIVCPN_UAT_20120423\PAYSETT\MSGOUT\PAY folder 2. It generates setting messages for the APPROVED & ACK payadvices  - put sett messages in the M:\MERITRESEARCH\BARCAP_DIVCPN_UAT_20120423\PAYSETT\MSGOUT\SETT folder	Flow 1. set cutofftime as nextCobDate 20210722 2. Call OutputPostingsExt22. This function pulls the journal recods with rlstimestamp > cutofftime (nextCobdate).  - Go through each record leaving the log entry "Processing Journal...".  - validates the record  - if valid, it calls the OutputPostingGroup() 3. In OutputPostingGroup(), a. Checks if post message can be created or not . The function CallCanPost(), returns the status and ack status of payadvice.  b. if CallCanPost() return OK*, then (If it is APPROVED, & AWTG then)      - Creates PAYMSG file, in Basepath\PAYSETT\MSGOUT\PAY\  with name PAYMSG20210722-  (20210722- is today's date)      - calls CallCreateCustomAckNak(). This simulates the Pay ack/nak creation for MERIT_UAT environment, for the PAYMSG created.             - For Merit_UAT, it creates sample swift_pay_acknoledgement files and put it in Basepath\PAYSETT\MSGOUT\PAY\             - CreateCustomAckNakPay -> CreateCustomAckNakPay_() (paysett_invoke.txt). create implem specific ACK/NAK messages(Merit Only) and put it in BPATH]PAYSETT\MSGIN\PAY\SWFTACKNAK*.TXT       - Update the PAY record in Journal table with RLSTIMESTAP = "20991231:23595900"       - '30991231=> Rejected journal; 20991231=> Processed journal; else=>Release date c. creates a SETT file in Basepath\PAYSETT\MSGOUT\SETT\, same as step b but will create the SETT messages. - Creates PAYMSG file, in Basepath\PAYSETT\MSGOUT\SETT\	1 Put Debugger in CallOutputPostings() & UploadSettMsgs() 2 Do a Approve a pay+sett 3. Run MSGS 4. Check the below queries in DB select MRTID, MRT_KEY, MRTSTATUS, MRTACK  from mrt_bcclaimsPAYADV order by mrtid select MRTID, MRTCMJREF, MRTTIMESTAMP, mrtrlstimestamp from mrt_bcclaimsJOURNAL where --21 (MRTRLSTIMESTAMP<='20210722:00000000') AND (MRTJTEXT NOT LIKE 'POST%') ORDER BY MRTTIMESTAMP,MRTORDER 5. Once the execution reaches UploadSettMsgs(), check the below, Basepath\PAYSETT\MSGOUT\PAY\ Basepath\PAYSETT\MSGOUT\SET\  BPATH]PAYSETT\MSGIN\PAY\ Also Execute the above query and verify the RLSTIMESTAMP
MSGS	4000	Upload SETT messages	1000	UploadSettMsgs()	1. Reads the pay out messages from the files in  the M:\MERITRESEARCH\BARCAP_DIVCPN_UAT_20120423\PAYSETT\MSGOUT\SETT folder 2. Write into CM_SETTLEMENT_DETAIL_BRIDGE and CM_SETTLEMENT_SUMMARY_BRIDGE, from file PAYSETT\MSGOUT\PAY\SETTMSG 3. It creates an intermediate file in "%TEMP%SETTMSG",".TXT", add to history entry Note: Upstream systems will read the records in SETTLEMENT_BRIDGE tables and update the records status to 'PRO' once they process the records.		1 Put Debugger in UploadSettMsgs() & UploadPAYMsgs() 2 Precondition, there should be atleat a payadvice, with APPROVED, MRTAK  = ACK, but the settlement message not yet generated. 3. Check the below queries in DB select * from CM_SETTLEMENT_SUMMARY_BRIDGE select * from CM_SETTLEMENT_DETAIL_BRIDGE 4. Run MSGS 5. Once the execution reaches UploadPAYMsgs(), check the below, Execute the above query, there will be new records in both the tables 6. Check Audit Trail in the payadvice. There will be sett message
MSGS	5000	Upload PAY messages	1000	UploadPAYMsgs()	1. Reads the pay out messages from the files in  the M:\MERITRESEARCH\BARCAP_DIVCPN_UAT_20120423\PAYSETT\MSGOUT\PAY folder 2. Write into CM_MQMSGS_OUT_BRIDGE from file PAYSETT\MSGOUT\PAY\PAYMSG, with CMOB_STATUS = 'NOT' 3. It creates an intermediate file in "%TEMP%PAYMSG",".TXT", and add it to history entry Note: Upstream systems will read the records in OUT table and update the records status to 'PRO' once they process the records.		1 Put Debugger in  UploadPAYMsgs() & UploadACKNAKMsg() 2 Precondition, there should be atleat a payadvice, with APPROVED, MRTAK  = AWTG, 3. Check the below queries in DB select * from CM_MQMSGS_OUT_BRIDGE. SEME_REF will be payadvice key 4. Run MSGS 5. Once the execution reaches UploadACKNAKMsg(), Execute the above query again, there will be new records in in the table , with SEME_REF, same as the recently APPROVED pay advice 6. Check Audit Trail in the payadvice. Ther will be pay message
MSGS	6000	Download ACK/NACK messages	1000	UploadACKNAKMsg()	1. Reads from 'CM_MQMSGS_IN_BRIDGE' table for items with CMIB_STATUS ='NOT'. (refer function GetSourceData_MQIN()) 2. for each record from step 1,   -Write it to MRT_BCCLAIMSIOQ table   -Update the status to 'PRO' in 'CM_MQMSGS_IN_BRIDGE' table Note 1: In MERIT_UAT, the data population from Upstream systems is mocked. This is done by CallOutputPostings() (step 2. b ) with corresponding payack txt file generation and creacted in the folder . Note 2. In MERIT_UAT, Another way is to insert aack/nak message in 'CM_MQMSGS_IN_BRIDGE at the begining of UploadACKNAKMsg(). Note 3: In MERIT UAT , by default ACK type messages are inserted in this IN_BRIDGE table. To test a NAK scenario, update the the messages's {451:0) to {451:0}, before calling the function GetSourceData_MQIN()	Moc records for NAK message 1. Put a debugger in MSGS Code just before GetSourceData_MQIN()) function. 2. Once, debugger hits, go to the db and do below.  - Read the records in IN_BRIDGE. Identify the message for which the NAK has to be tested. Eg CMIB_TAG=630  select * from CM_MQMSGS_IN_BRIDGE  order by CMIB_TAG  -  update CM_MQMSGS_IN_BRIDGE SET CMIB_DATA ='{1:F21BARCGB33AXXX0000000000}{4:{177:1110281218}{451:1}{405:T30012}{108:2021071913355144}}{1:F01ZYAFGB30XXXX3026311635}{2:I202ZYAFGB30XXXXN}{5:{CHK:308FFD99259A}{TNG:}}', CMIB_STATUS ='NOT' WHERE CMIB_TAG = 630  -  Clear the IOQ table entries, so that fresh data is inserted into it based on the IN_BRIDGE tables' STATUS= 'NOT'   type records. 3. Execute the debugger.	1 Put Debugger in  UploadACKNAKMsg() 2 Precondition, there should be atleat a payadvice, with APPROVED, MRTAK  = ACK, 3. Check the below queries in DB select * from CM_MQMSGS_IN_BRIDGE  order by CMIB_TAG 4. Run MSGS 5. Once the execution reaches UploadACKNAKMsg(), the payadvice will be updated with ACK/NAK status as per the pay ack created.
MSGS	6050	Skip Jobs ACKNAK Imp if no source data found	1000	SkipImpJobsIfNoSourcedata()
MSGS	6100	Import ACK/NAK messages	6050	115#PAYSETTIN. Also Post import rule 115#PAYSETTIN	1. Import schedule updates data from BCCLAIMSIOQ to PayAdvice Table, updates MRTACK column. 2.Post import rule executes few activities like, - deletes the entries in IOQ table