we found the same problem on the test bench. Occurs only if the target table is empty. For the null case, we simply added the null processing above the method call.