[SICSR-16081] Rule 166 Reject Payment Request until Reinstatement is received not valid for LPC
Product Line:	P&C
Component/s:	eMessaging TA
Affects Version/s:	SICS 4.8.6 SSP5
Fix Version/s:	SICS 4.9.3 SICS 4.9.2 SSP2
Customer:	Swiss Re Zurich
External Issue ID:	PRB000604850

Problem:
In PROD, Claim Movement message UUid = 89F8CC40-CBE3-49F2-8941-69A1368A0E8C has received an error from the rule
RejectPaymentRequestUntilReinstatementReceived.
The message is a LIRMA claim movement, as evidenced by the presence of the service provider, the agency of the receiver, and a sequence number in the extension. The message receives a message function of 'service provider'.
London market claims do not link reinstatements to the claim worksheet, so we are unclear why this rule has set an error on this message. There are no other examples of London CM messages linked to a business that has reinstatements requiring the reinstatement message to be received before the CM can be processed. See for example CM UUid = BE00738D-B331-4D4E-BFFD-B88CBC11B8B9. This one (from the same broker) processed with no error set by RejectPaymentRequestUntilReinstatementReceived. Looking through the message content, there is no obvious difference that would cause the rule to set an error on one and not the other.

Solution:
if the ModifyClaimBookingBehaviourRule is being used then RejectPaymentRequestUntilReinstatementReceived should exit without validation

Workaround:
In the ClaimMovement Message rule set, for RejectPaymentRequestUntilReinstatementReceived a new Message Function Service Provider rule configuration should be added for the rule.
Select the new configuration that has Service Provider and then turn off the rule.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected