When processing incoming AssetPlus transfers, the system should only attempt to create DT_YAP_CORE_CHILD_PROTECTION_PLAN records if at least both a child protection category and date have been passed (as these are both non-nullable). In scenarios where a completely blank record is passed in the XML, we will ignore it as if it didn't exist, rather than allowing an exception to occur.
An issue has been brought to our attention by i2n recently, whereby Core+ was unable to process a transfer sent from YJAF. The cause of this was a single empty <Care_History_FE_Group/> element. Our system identified this as a valid DT_YAP_CORE_CHILD_PROTECTION_PLAN record, but would then trigger an exception due to non-nullable fields.
Technically, the system is correct in this behaviour, as it has been passed a blank record, rather than no record (which should be indicated by the complete omission of the Care_History_FE_Group element).
To resolve this issue, you need to raise a new case with us and reference this article so we can look at this and remove the empty element from the XML. This will then allow you to accept the inbound transfer.
Inbound transfer error when accepting
In this article, we'll be able to explain what to do when you encounter an error while accepting an inbound transfer.
D
Written by David Bayley-Hamilton
Updated over 4 months ago