GP to BC Compare: Customer Address Master Record Tables
There are many differences between Dynamics GP and Dynamics 365 Business Central, but this page highlights the technical differences important to me between the primary master record tables for CUSTOMER ADDRESSES for carrying over this information to BC. BC is not GP in the cloud, as you can see by the underlying table structure differences for these vendor-related master records.
Business Central |
|
Dynamics GP |
||||||
Table ID |
Page ID |
Page Name |
Table Columns |
|
Table ID |
Table Name |
Form Name |
Table Columns |
18 |
21 |
Customer Card |
188 |
|
RM00101 |
Customer Master |
Customer Maintenance |
103 |
222 |
300 |
Ship-To Address |
36 |
|
RM00102 |
Customer Address Master |
Customer Address
Maintenance |
33 |
13 |
5116 |
Salesperson/Purchaser
Card |
31 |
|
RM00301 |
Salesperson Master |
Salesperson Maintenance |
39 |
This next table shows the best and most important field matches for the vendor address master records between Dynamics GP and Business Central.
Business Central |
|
Dynamics GP |
|
The Dynamics Mindset |
||
Table 222 |
|
Table RM00102 |
|
GP to BC CUSTOMER
ADDRESS Field Mapping Notes |
||
Field |
Field Length |
|
Field |
Field Length |
|
**Filtered and Mapped
Fields |
Customer No. |
Code 20 |
|
CUSTNMBR |
15 |
|
Auto-numbering available
in BC |
Code |
Code 10 |
|
ADRSCODE |
15 |
|
BC is 5 char less than
GP |
Salesperson Code |
Code 20 |
|
SLPRSNID |
15 |
|
BC uses a shared
Salesperson/Purchaser card (table 13, page 5116) |
UPS Zone |
Code 2 |
|
UPSZONE |
3 |
|
|
Shipment Method Code |
Code 10 |
|
SHIPMTHD |
15 |
|
BC is 5 char less than
GP; may not align functionally |
Contact |
Text 100 |
|
CNTCPRSN |
60 |
|
|
Address |
Text 100 |
|
ADDRESS1 |
60 |
|
|
Address 2 |
Text 50 |
|
ADDRESS2 |
60 |
|
BC is 10 char less than
GP |
Country/Region Code |
Code 10 |
|
CCode |
6 |
|
BC Region/Country (table
9, page 10) |
City |
Text 30 |
|
CITY |
35 |
|
BC is 5 char less than
GP |
State (County) |
Text 30 |
|
STATE |
29 |
|
|
ZIP Code |
Code 20 |
|
ZIP |
10 |
|
BC has optional Post
Code (table 225, page 367) |
Phone No. |
Text 30 |
|
PHONE1 |
20 |
|
BC only allows numbers |
Fax No. |
Text 30 |
|
FAX |
20 |
|
BC only allows numbers |
Location Code |
Code 10 |
|
LOCNCODE |
10 |
|
Default company
site/location |
This table shows the Dynamics GP customer address master table fields not included in the matched field mapping above.
Many simply don’t fit, or their purpose is conceptually or fundamentally different or incompatible with a clean, straight mapping of data from GP to Business Central.
Dynamics GP |
|
The Dynamics Mindset |
Table RM00102 |
|
GP to BC CUSTOMER
ADDRESS Field Mapping Notes |
Field |
|
**UN-Mapped Fields |
ADDRESS3 |
|
BC does not have Address
3 |
COUNTRY |
|
BC uses the
Country/Region codes and descriptions (table 9, page 10) |
CREATDDT |
|
System-generated |
DECLID |
|
GP Tax Declarant ID |
DEX_ROW_ID |
|
System-generated |
DEX_ROW_TS |
|
System-generated |
GPSFOINTEGRATIONID |
|
|
INTEGRATIONID |
|
|
INTEGRATIONSOURCE |
|
|
MODIFDT |
|
System-generated |
PHONE2 |
|
|
PHONE3 |
|
|
Print_Phone_NumberGB |
|
|
SALSTERR |
|
BC does not treat Sales
Territories same as GP |
ShipToName |
|
|
TAXSCHID |
|
BC taxes map to Tax
Areas (table 318, page 464) and Jurisdictions (table 320, page 466) |
USERDEF1 |
|
BC does not have
user-defined fields on the customer address |
USERDEF2 |
|
BC does not have
user-defined fields on the customer address |
This table shows the Business Central customer address master table fields not included in the matched field mapping above.
Many simply don’t fit, or their purpose is conceptually or fundamentally different or incompatible with a clean, straight mapping of data from GP to Business Central.
Business Central |
|
The Dynamics Mindset |
Table 222 |
|
GP to BC CUSTOMER
ADDRESS Field Mapping Notes |
Field |
|
**UN-Mapped Fields |
Created At |
|
System-generated |
Created By |
|
System-generated |
Email |
|
This resides on the
Internet Information window in GP (SY01200) |
GLN |
|
BC Electronic Document
config (European) |
Home Page |
|
This resides on the
Internet Information window in GP (SY01200) |
Last Date Modified |
|
System-generated |
Modified At |
|
System-generated |
Modified By |
|
System-generated |
Name |
|
|
Name 2 |
|
|
Place of Export |
|
|
RowVersion |
|
System-generated |
SAT Address ID |
|
For Community
Development Financial Institution reporting |
Service Zone Code |
|
For warehouse config in
BC |
Shipping Agent Code |
|
Shipping company for
vendor products |
Shipping Agent Service
Code |
|
Shipping company service
option for customer delivery |
System ID |
|
System-generated |
Tax Area Code |
|
BC Tax Config |
Tax Liable |
|
BC Tax Config |
Telex Answer Back |
|
|
Telex No. |
|
|
Author’s note and Disclaimer:
Mapping ERP systems is a complex and subjective task for any one person.
Significant differences between GP and BC will require you to learn more deeply about the product to perform a successful implementation.
There is more than one way to map particular fields, but I think you’ll get a lot out of the references provided.
I am not infallible, so let me know if you spot an issue I need to update. I don’t want to present anything factually incorrect here, however how you map your data in real life is up to you.
I needed to know the differences that really matter between the master records in both Dynamics GP and Business Central. I hope you gain value from my analysis and notes.
As I do more BC implementations, and if / when BC changes, I’ll keep this up to date, and make adjustments and add additional notes where needed. I’ll also work on filling in any holes to make this complete because these are MY personal reference pages too.
Some of the tables on the individual pages probably won’t render very well on some mobile devices, but try tipping it horizontally instead!