The tables involved are
| Flow | Table name | Owner | How data is populated |
| 1 | CM_ASSASSIN_SSI_BRIDGE | Barclays | Barclays has to populate the SSI details to this table from Barclays internal systems. Once the record is added in this table, Merit has to work on it |
| 2 | MRT_BCCLAIMSSSI | Merit | MSGS service reads the new SSI information added in CM_ASSASSIN_SSI_BRIDGE, and populate it in MRT_BCCLAIMSSSI |
| 3 | MRT_CLAIMS | Merit | For a Claim (MRT_BCCLAIMS) to populate an SSI (MRT_BCCLAIMSSSI), that claim’s Claim Department and Currency, should be same as SSI’s Claim Department and Currency.
|
Details:
When a query on the SSI information missing/not-getting-populated in the Claims is received, the analysis can be done with the help of below questions.
Questions to Barclays
- When was the user raised the SSI was raised/executed and for which currency it is raised?
- Result of the below query
- select CMAB_TAG,ASSASSIN_SSI_ID,CURRENCY,COUNTRY, SECURITY, ACTIVE_FLAG, DEFAULT_FLAG,LAST_AMENDED_DATE,LAST_AMENDED_BY from CM_ASSASSIN_SSI_BRIDGE where COUNTERPARTY_SDS_ID='_<SDS ID here>_' and CURRENCY='_<CURRENCY here>_';
- select MRTCMAB_TAG, mrt_key, MRTASSASSIN_SSI_ID, MRTCURRENCY, MRTACTIVE_FLAG, MRTSECURITY,MRT_LASTUPDATE, MRT_CLOSEDFLD, mrtitemupdateidsvc_msgs from MRT_BCCLAIMSSSI where (MRTCOUNTERPARTY_SDS_ID='_<SDS ID here>_')AND (MRTCURRENCY='_<CURRENCY here>_')
- If there is a claim where the SDS IDs are expected to be populated, run the below query for those claims’ keys and share the result.
- select MRTSDSID, MRTCLAIMDEPT, MRTCCY,MRT_LASTUPDATE, MRT_CLOSEDFLD from MRT_BCCLAIMS where MRT_KEY = 'key_of_claim_here'
How to investigate
| Steps | Flow | How to check/analyze the status of SSI in Barclays’ system and find out why SSI is not populating |
| 1 | User creates an SSI record within the internal system (Barclays). | |
| 2 | A process running within the application server will create a new record within CM_ASSASSIN_SSI_BRIDGE table. This process is managed by Barclays IT. Merit does not have any control over this process. |
Result for Query 2. a. In the below mail, will confirm it. If there is are records with recent date in ‘LAST_AMENDED_BY’, then Barclays has uploaded the data in to CM_ASSASSIN_SSI_BRIDGE table. So, proceed with analysis, go to the Step 3. Else Barclays have not yet uploaded data to CM_ASSASSIN_SSI_BRIDGE for CM to read from Response to Barclays : Barclays have to check with their internal support teams to find out why the record is not inserted into this table End |
| 3 | Once the record is present on the above table MSGS service will import the record into MRT_BCCLAIMSSSI table. |
Result for Query 2. b. In the below mail, will confirm 3 & 4 points. If there is a record, then data is pulled into CM. And it is available for Claims to use. So, proceed with analysis, go to the Step 5. Else data is not yet read by MSGS from CM_ASSASSIN_SSI_BRIDGE table. For this, we will need to check the MSGS logs. Response to Barclays : Share the MSGS logs for the day on which the SSI data was uploaded to CM End |
| 4 |
Once record is created on this table, users will be able to lookup these records using the condition (MRTCOUNTERPARTY_SDS_ID='__<SDS ID here>__')AND (MRTCURRE NCY='__<CURRENCY here>__') |
|
| 5 | For a Claim to populate an SSI, that claim’s Claim Department and Currency, should be same as SSI’s Claim Department and Currency. |
This can be confirmed with the result Query 3. 1. The values of MRTSECURITY, MRTCURRENCY of Query 2.2 should be same as MRTCLAIMDEPT, MRTCCY of Query 3.1. If MRTSECURITY== MRTCLAIMDEPT && MRTCURRENCY== MRTCCY then, Further need to analysis on data is need to understand why Claim is not showing the SSI data . Response to Barclays : Collect MSGS logs for the day of SSI upload ELSE Response to Barclays : Claim’s claim department and/or Currency does not match with the uploaded data. Please upload the data to CM_ASSASSIN_SSI_BRIDGE. End |
Comments
0 comments
Please sign in to leave a comment.