I just wanted to provide you with an update regarding the development for the OEM mileage issue.
As you may already be aware I have consolidated yours and AGA CN’s original tickets into MEWII-2609. Whilst creating the latest BR document a couple of additional points have been raised one of which I would like to share with you.
All the policies for AGA TH originate from your own internal sales system before being data loaded, via XML, to MEWv2. Your original request was to be able to amend the policy, in MEW, to allow a claim to be submitted where the OEM mileage limit is exceeded before the EW policy start date. Having discussed this internally, this conflicts with our (HQ) opinion that policy amendments should only be made in the ‘Primary’ system they originated from with the amendments data loaded to the ‘secondary’ (MEWv2) system.
Assuming we implemented this process for imported policies, we still have a further issue where the existing XML process will not allow an ‘as is’ load of amended policies; policies in the XML have to adhere to a set format which results in an error file when they don’t.
For the time being we have decided to do the following for policies imported to MEW:
• Allow the EW policy to be amended directly in MEW for policies with the OEM mileage limit issue
• We will look at the XML file, for imported policies, at a later phase – This would then allow the policy amendment in the ‘Primary’ system before dataload to MEW
• For the time being we would suggest that AGA TH still update the corresponding policy in their own internal systems so there it matches the policy amendments made directly in MEW
Hopefully my explanation is clear to you but if not please let me know and we can discuss further.
I just wanted to provide you with an update regarding the development for the OEM mileage issue.As you may already be aware I have consolidated yours and AGA CN’s original tickets into MEWII-2609. Whilst creating the latest BR document a couple of additional points have been raised one of which I would like to share with you.All the policies for AGA TH originate from your own internal sales system before being data loaded, via XML, to MEWv2. Your original request was to be able to amend the policy, in MEW, to allow a claim to be submitted where the OEM mileage limit is exceeded before the EW policy start date. Having discussed this internally, this conflicts with our (HQ) opinion that policy amendments should only be made in the ‘Primary’ system they originated from with the amendments data loaded to the ‘secondary’ (MEWv2) system.Assuming we implemented this process for imported policies, we still have a further issue where the existing XML process will not allow an ‘as is’ load of amended policies; policies in the XML have to adhere to a set format which results in an error file when they don’t.For the time being we have decided to do the following for policies imported to MEW:• Allow the EW policy to be amended directly in MEW for policies with the OEM mileage limit issue• We will look at the XML file, for imported policies, at a later phase – This would then allow the policy amendment in the ‘Primary’ system before dataload to MEW• For the time being we would suggest that AGA TH still update the corresponding policy in their own internal systems so there it matches the policy amendments made directly in MEWHopefully my explanation is clear to you but if not please let me know and we can discuss further.
การแปล กรุณารอสักครู่..
