Integrating FIM with SAP using web services connector

Hi 

I am implementing the FIM web services connector to integrate with SAP. The MS connector config guide for SAP documentation seems to me missing some content or at least I think it might be written for an earlier version of SAP than the version we are working with(different screenshots, options, etc). The version of SAP we have implemented is EHP6 for SAP ERP6 which I believe translates to ECC6.
SAP web services have been configured and FIM performs successful discovery of the wsdl endpoint and BAPI operations as expected. Our issue is that FIM fails to run a full import. From the digging around web service config and error logs two observations comes out:

1. FIM Full Import workflow does not render correctly through the web service configuration tool and complains of a duplicate attribute "xml:space is a duplicate attribute on line on line 424 on position 103". Review of the wsconfig generated by the webservice config tool points to an variable supplied to a construct the query to a BAPI of HR infotype 0006. Extract below:

...<InArgument x:TypeArguments="d:BAPIP0006L" xml:space="preserve">[If(Not IsNothing(addressInfo) AndAlso Not IsNothing(addressInfo.item), addressInfo.item, Enumerable.Empty(Of BAPIP0006L)()).
OrderByDescending(Function(a) DateTime.ParseExact(a.VALIDBEGIN, dataSourceDateFormatValue, Nothing)).
ThenByDescending(Function(a) Integer.Parse(a.RECORDNR)).FirstOrDefault()]</InArgument>...

I can only guess that it means the query should keep the spaces within the string it passes to SAP but this is where my understanding stops.

 
2. SAP returns errors about not implementing a BAPI EMPLOYEE_GETDATA function which is not part of the exposed BAPI operations. Well the obvious solution to this would be expose this missing operation (which is undocumented in MS config guide) however this BAPI is a core requirement to retrieve person information. I would be hugely surprised if this operation was not factored into the config. This makes me think that to understand this better I need to resolve issue 1 first and get the rendering sorted first. 

Has anyone come across the above issues with a recent implementation with this connector? Or help point me in the right direction? 

any help would be greatly appreciated!

thanks!!