1. Has the placement been sent to ESR?

   1. This can be viewed on the placement details in the TIS front end

   2. It can also be viewed in metabase in the ESRexporter - prod / Generatedapprecord collection and the status field will give information about the export status

   Open

   

2. If the placement hasn't been exported to ESR you can view the status in metabase shown above.

   TO_EXPORT means this record hasn't been picked up to export

   DELETED_BEFORE_EXPORT means the placement or reconciliation information was deleted before the record was exported

3. INVALID_DATA means there is a schema error which is blocking the sending of this record, the details can be found in the generation error field. Once this data is fixed (through the TIS UI) a valid record will be produced and be eligible for export

4. If the placement doesn't have an app record you should check the reconciliation status of the post.

   1. This should be displayed in TIS once the following tickets are completed (https://hee-tis.atlassian.net/browse/TISNEW-5141 , https://hee-tis.atlassian.net/browse/TISNEW-5461 )

   2. You can also check metabase in ESRreconciliation - prod / positions and the status field will let you know whether the postion is MATCHED or UNMATCHED.

   3. There is also another field in metabase “Deleted” which shows whether ESR has sent a deletion for a position record. Deleted positions will not produce applicant records or notifications to be sent to ESR.

   4. If no record exists in metabase for a post in this position collection then ESR has not sent the required information for producing applicant records and the trust should check their position set up.

5. If none of the above steps have resolved the issue please contact the team for further investigation.

(Historical discussion below)

1. Has the post been reconciled with a position in esr?
   
   This can be checked by….
   
   Old Interface:
   Searching tables Esroutboundpositioninformationrecord and Esroutboundpositionreconciliationrecord and filtering by Deanerynumber for the post in question. If no records are present the post is not reconciled with an ESR position and hence cannot be exported.
   
   
   New Interface:
   In the future, You will be able to view if a post is reconciled, you will be able to see this on the UI of TIS. see ticket: https://hee-tis.atlassian.net/browse/TISNEW-5141
   
   Currently, you’ll be able to verify this under ESRReconciliation > positions with the information within the Status column as MATCHED or UNMATCHED.
   
   

   Open

   

   
   Internal TIS team: We can also query the reconciliation and audit service for more detailed information
   
   

2. The placement has missing mandatory information
   
   This can be checked by…
   
   Old Interface:
   Querying the deanery number you are looking at in Esroutboundapplicantconfirmationrecord and looking whether the records associated with this have Esrloadstatus of fail and an esrstatusmessage containing mandatory
   
   Can use ESR reports in Tableau, also looking at BAU validation tools.
   
   New Interface:
   
   Future:
   
   Query the audit system, how do we report/show on front end? Show it doesnt export.
   
   

3. The applicant has not been exported to ESR
   
   This can be checked by…
   
   Currently:
   Querying Esrinboundapplicantdetailsrecord for the deanery number you are looking for and checking whether there is a record with a tisstatus of EXPORTED. If these records arent present then you can try querying the deanery number you are looking at in Esroutboundapplicantconfirmationrecord and looking whether there are records associated with this have Esrloadstatus of SUCCESS
   
   Causes:
   -Has placement been created on tis
   -Has it been added on time? 13 week - 2 day before start window*
   
   

   Future:
   Front end esr status on placement and first exported date. Query the exporter by placement id?
   
   

4. The applicant has been sent to ESR, but has not been processed
   
   This can be checked by…
   
   Querying the deanery number you are looking at in Esroutboundapplicantconfirmationrecord and looking whether the records associated with this have Esrloadstatus of fail