SAP Knowledge Base Article - Preview

1408402 - Data Services XI 3.2 (version Fix Pack Release Notes


Data Quality Updates

Geocoding Parcel for US by NAVTEQ

This release includes new geocoding parcel directories that are used with the geocoding functionality in the USA Regulatory Address Cleanse transform (not in the Geocoder transform). The geocoding parcel directories contain the most precise and accurate latitude and longitude values available in the market for addresses. Usually, using regular geocoding directories, latitude and longitude values for a house are calculated by interpolating between a beginning and ending point of a line segment where the line segment represents a range of houses. The regular geocoding latitude and longitude values may be slightly offset from the exact location from where the house actually exists. Geocoding parcel data is stored as points, so rather than getting you near the house, it takes you to the exact door. The geocoding parcel data currently contains an estimated 70 million points in the US with continued expansion. A common way to use the geocoding parcel directories is to first run an address through a USA Regulatory Address Cleanse transform using the geocoding parcel directories and, if no assignment is made, to then process the address through a transform using the regular geocoding directories.  Geocoding parcel directories are named similarly to the regular geocoding directories except that “_pt” is appended to the name; for example, ageo1_pt.dir. Regular geocoding and parcel directories can exist in the same folder. 

German Geocoder directory

This release includes a new directory that provides basic geocoding for Germany through the Geocoder transform. 

AMAS certification

This release includes the assignment changes necessary to be approved by Australia Post in accordance with the Address Matching Approval System (AMAS) Cycle December 31, 2010. 

SendRight certification

 This release includes the assignment changes necessary to be approved by New Zealand Post in accordance with the SendRight Address Accuracy Programme from January 2010 through December 2010.

Product Issues addressed in this Fix Pack


Persistent Cache datastore was missing the Configuration Edit button to add additional configurations. This issue has been resolved. 


Data flows that used Web Service functions imported either using Native Web Service datastore or Adapter datastore crashed with Access Violation if the function call failed. This issue has been resolved in this release.  


Importing functions from Salesforce WSDL failed with error "Unable to Import Metadata" when the Adapter Datastore was used. This issue has been resolved.  


The resource control auto scripts in Linux SuSE generated in Data Services did not execute at system startup nor shutdown. This issue has been fixed in this release. 


The Designer performance and memory management has been improved in this release. The start-up time and memory usage for the Designer is much improved for a large repository.  


Performance in generation of the DQ Reports were negatively affected by the SQL calls made by the JDBC driver. This issue has been resolved. 


AR RapidMart DataFlow DF_BillingDistributionFact_OA failed with error "System running out of virtual memory", even with cache type set to pageable. This issue is resolved.  


When in the Break Key section of the Match Editor for the Match transform, the "Maximum allowable break group size" option was disabled and could not be edited.  A default value of 'unlimited' was utilized upon job execution.  This option is now enabled within the Match Editor.

 For more information please read the full Fix Release Notes that are attached to this SAP Note in PDF format.



SAP Data Services XI 3.2


KBA , EIM-DS , Data Services , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.