Batch run leave the claim in Process


the Claim for Utha / april 2020 are still in process but the april batch run was executed (date processed should be in April too)

there is also no relative index created but it is not supprising because the claim were not takem into account




Xavier Gillmann
June 2, 2020, 9:32 AM

Logs from the serever seem to point to tblClaimDedRem:


Eric Darchis
June 2, 2020, 9:40 AM

That issue seems to be a null PolicyID. I have to check why it's null.

Here is the formatted query that fails:

SET NOCOUNT ONINSERT INTO [tblClaimDedRem]([ValidityFrom], [ValidityTo], [LegacyID], [PolicyID], [InsureeID], [ClaimID], [DedG], [DedOP], [DedIP], [RemG], [RemOP], [RemIP], [RemConsult], [RemSurgery], [RemDelivery], [RemHospitalization], [RemAntenatal], [AuditUserID])VALUES ('2020-06-02 02:07:34', null, null, null, 15, 297, 0.00, 0.00, null, 0.00, 00.00, Null, 0, 0, 0, 0, 0, 1);

Eric Darchis
June 4, 2020, 9:40 AM

The claim that seems to be stuck has a rejected service and another one that looks ok. However, that service has a rejection_status of 10. Therefore, when processing the claim, the validation is first run on the claim and since all its services have a rejection reason, the claim is rejected and therefore not processed.

I am not 100% sure of the exact event sequence that triggers this situation but my guess is something like this:

- the claim is created and submitted. It is valid.

- the claim is reviewed and one service is rejected. Its status is REJECTED and its ResasonCode is -1

- in the mean time, the limit for this product is reached from other claims

- when the claim is actually processed, the claim is validated again and the rejection reason is set to 10. When I tried this, it also changed the status but there is probably a situation where it is not.


I am reviewing the various places where the rejection reason is updated to understand where we can update one without updating the other.

Patrick Delcroix
June 4, 2020, 10:03 AM

Normally when they are processed, only the valuation remains, meaning the limits should already be taken into account during the checks. but the weird part is all those claims with A1 (relative pricing) are in the status valuated:

Also no relative pricing are created


UPDATE: there is no contribution for that period, I have to retest…

Patrick Delcroix
August 14, 2020, 7:08 AM

I just tired again on Demo (Should have tied on release ?) and there is 4issues:

1- I can execute multiple time a batch run for the same location/timeframe (It should give an error on the second time)

2- I still dont see the relative indexes

3- the list of batch run in Account doesn’t show the location/period of that batch run but only the runing date

4- The pdf generated still give an error



Patrick Delcroix


Patrick Delcroix