web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

SAP Customer Data migration to D365 FO - ADDRESSSTREET format

(2) ShareShare
ReportReport
Posted on by 6
We don’t know how to format the ADDRESSSTREET field in the D365 template so that our SAP address data stacks with carriage returns when importing.  Our attempts have not worked.  
 
Challenge:  The SAP street address data is stored in separate fields (Street, Street2, etc).  During migration, we must extract from SAP and bring multiple fields together into the ADDRESSSTREET field in D365 template. Thie issue is that we have to insert line separators in this ADDRESSSTREET to separate lines when importing into FO. 
 
We need to extract from SAP and bring these fields together with some sort of 'carriage return' function that will cause separate lines in the ADDRESSSTREET field in D365 template.  Our SAP ABAP developer tried a few things like '\n\r' but nothing has worked.  Any tips are apprecicated.
 
The source data extracted from SAP will be imported into D365 using VerticalBarSeparated files.
Categories:
I have the same question (0)
  • Martin Dráb Profile Picture
    236,972 Most Valuable Professional on at
    SAP Customer Data migration to D365 FO - ADDRESSSTREET format
    How are you importing the data? Which data entity?
     
    Please describe the issue too. At what point does it fail and how? For example, do you get an error or do you get text without line breaks in the staging table?
  • OM-04112205-0 Profile Picture
    6 on at
    SAP Customer Data migration to D365 FO - ADDRESSSTREET format
    Data entity: Customers V3
    Data entity: Vendors V2
    Data entity: Customer Postal Addresses
     
    We are loading master data.  Customers and Vendors have mailing/business addresses that need to be imported into D365.
     
    In SAP, the address data is captured in separate fields.  There is a Street1, and a Street2, etc. 
    In D365, there is a single field that contains the street address information.  This field ADDRESSSTREET presents the address block, for example:
     
    123 Main Street
    Building A
    Office No. SO541
     
    When entering the address data in D365 manually, the user must use the carriage return to separate the rows, so that they present as a proper address block on forms, identical to the above example.
     
    The ISSUE:  Our SAP program extracts the data and populates the ADDRESSSTREET field.  This is a single field in the template.  So, it is in a single string.  In this example it would be:
     
    123 Main Street Building A Office No. SO541
     
    When this imports into D365, it is a WRAPPED string.  There are no distinct rows, with carriage returns to stack the address.
     
    Our question:  what 'special' code is used to cause the import program to recognize the carriage return in this string?  I'm certain we are not the only client to face this data migration issue.  
     
    Our developer found a suggestion to insert /n/r where a carriage return is needed.  That didn't work.
     
    Thanks for your help. 
  • Martin Dráb Profile Picture
    236,972 Most Valuable Professional on at
    SAP Customer Data migration to D365 FO - ADDRESSSTREET format
    You seem to be saying that the what you get from SAP is 123 Main Street Building A Office No. SO541, i.e. the information about line break got lost when exporting from SAP. If so, then there is no problem on F&O side; you'll need to fix the export from SAP.
    Nevertheless check the data carefully; there may be control characters with the information that you don't see.
     
    There is no special code, as far as I know. You need line breaks if you want to import line breaks. If you can't get line breaks from SAP but can get another indicator, then you can transform the file before importing to F&O.
     
    It may be easier if you use format that don't use line breaks as record delimiters, such as XML, although even formats like CSV can contain line breaks in values (if the value is wrapped in quotation marks) or you can define another record delimiter in DMF source format configuration.
     
    In short, the key step is getting the information from SAP, in one way or another. When you have that, you can transform the file to get exactly what you need for import to F&O, even if SAP can't give you that directly.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 701 Super User 2025 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 588 Most Valuable Professional

#3
Sumit Singh Profile Picture

Sumit Singh 544

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans