GP to BC Compare: Site / Location 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 SITES / LOCATIONS 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 master records.
|
Business Central |
|
Dynamics GP |
||||||
|
Table ID |
Page ID |
Page Name |
Table Columns |
|
Table ID |
Table Name |
Form Name |
Table Columns |
|
27 |
30 |
Item Card |
223 |
|
IV00101 |
Item Master |
Item Maintenance |
90 |
|
14 |
5703 |
Location |
73 |
|
IV40700 |
Sites |
Site Maintenance |
33 |
This next table shows the best and most important field matches for the site / location records between Dynamics GP and Business Central.
|
Business Central |
|
Dynamics GP |
|
The Dynamics Mindset |
||
|
Table 14 |
|
Table IV40700 |
|
GP to BC SITE Field
Mapping Notes |
||
|
Field |
Field Length |
|
Field |
Field Length |
|
**Filtered and Mapped
Fields |
|
Code |
Code 10 |
|
LOCNCODE |
10 |
|
BC Locations (table 14,
page 5703) |
|
Name |
Text 100 |
|
LOCNDSCR |
30 |
|
|
|
Address |
Text 100 |
|
ADDRESS1 |
60 |
|
|
|
Address 2 |
Text 50 |
|
ADDRESS2 |
60 |
|
BC is 10 char less than GP |
|
City |
Text 30 |
|
CITY |
35 |
|
BC is 5 char less than GP |
|
State (County) |
Text 30 |
|
STATE |
29 |
|
|
|
ZIP Code (Post Code) |
Code 20 |
|
ZIPCODE |
10 |
|
BC has optional Post
Code (table 225, page 367) |
|
Country/Region Code |
Code 10 |
|
COUNTRY |
60 |
|
BC Region/Country (table
9, page 10) |
|
Phone No. |
Text 30 |
|
PHONE1 |
20 |
|
Only numbers allowed in
BC, no alpha or special characters |
|
Phone No. 2 |
Text 30 |
|
PHONE2 |
20 |
|
Only numbers allowed in
BC, no alpha or special characters |
|
Fax No. |
Text 30 |
|
FAXNUMBR |
20 |
|
Only numbers allowed in
BC, no alpha or special characters |
This table shows the Dynamics GP site / location 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 IV40700 |
|
GP to BC SITE Field
Mapping Notes |
|
Field |
|
**UN-Mapped Fields |
|
NOTEINDX |
|
System Generated |
|
ADDRESS3 |
|
BC does not have Address
3 |
|
PHONE3 |
|
|
|
Location_Segment |
|
|
|
STAXSCHD |
|
BC taxes map to Tax
Areas (table 318, page 464) and Jurisdictions (table 320, page 466) |
|
PCTAXSCH |
|
BC taxes map to Tax
Areas (table 318, page 464) and Jurisdictions (table 320, page 466) |
|
INCLDDINPLNNNG |
|
GP Include in Item
planning |
|
PORECEIPTBIN |
|
GP Bin Location |
|
PORETRNBIN |
|
GP Bin Location |
|
SOFULFILLMENTBIN |
|
GP Bin Location |
|
SORETURNBIN |
|
GP Bin Location |
|
BOMRCPTBIN |
|
GP Bin Location |
|
MATERIALISSUEBIN |
|
GP Bin Location |
|
MORECEIPTBIN |
|
GP Bin Location |
|
REPAIRISSUESBIN |
|
GP Bin Location |
|
WMSINT |
|
|
|
PICKTICKETSITEOPT |
|
|
|
BINBREAK |
|
|
|
CCode |
|
BC Region/Country (table
9, page 10) |
|
DECLID |
|
|
|
INACTIVE |
|
|
|
DEX_ROW_ID |
|
System Generated |
This table shows the Business Central Item 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 14 |
|
GP to BC SITE Field
Mapping Notes |
|
Field |
|
**UN-Mapped Fields |
|
RowVersion |
|
System Generated |
|
Default Bin Code |
|
BC Bins map to Bin Card
(table 7354, page 7302 ) |
|
Name 2 |
|
BC additional Location
description field |
|
Telex No. |
|
|
|
Contact |
|
|
|
Email |
|
|
|
Home Page |
|
|
|
Use As In-Transit |
|
BC Warehouse option |
|
Require Put-away |
|
BC Warehouse option |
|
Require Pick |
|
BC Warehouse option |
|
Cross-Dock Due Date
Calc. |
|
BC Warehouse option |
|
Use Cross-Docking |
|
BC Warehouse option |
|
Require Receive |
|
BC Warehouse option |
|
Require Shipment |
|
BC Warehouse option |
|
Bin Mandatory |
|
BC Warehouse option |
|
Directed Put-away and
Pick |
|
BC Warehouse option |
|
Default Bin Selection |
|
BC Warehouse option |
|
Outbound Whse. Handling Time |
|
BC Warehouse option |
|
Inbound Whse. Handling Time |
|
BC Warehouse option |
|
Put-away Template Code |
|
BC Warehouse option |
|
Use Put-away Worksheet |
|
BC Warehouse option |
|
Pick According to FEFO |
|
BC Warehouse option |
|
Allow Breakbulk |
|
BC Warehouse option |
|
Bin Capacity Policy |
|
BC Warehouse option |
|
Pick Bin Policy |
|
BC Warehouse option |
|
Check Warehouse Class |
|
BC Warehouse option |
|
Put-away Bin Policy |
|
BC Warehouse option |
|
Open Shop Floor Bin Code |
|
BC Warehouse option |
|
To-Production Bin Code |
|
BC Warehouse option |
|
From-Production Bin Code |
|
BC Warehouse option |
|
Prod. Consump. Whse. Handling |
|
BC Warehouse option |
|
Adjustment Bin Code |
|
BC Warehouse option |
|
Prod. Output Whse. Handling |
|
BC Warehouse option |
|
Always Create Put-away
Line |
|
BC Warehouse option |
|
Always Create Pick Line |
|
BC Warehouse option |
|
Special Equipment |
|
BC Warehouse option |
|
Receipt Bin Code |
|
BC Warehouse option |
|
Shipment Bin Code |
|
BC Warehouse option |
|
Cross-Dock Bin Code |
|
BC Warehouse option |
|
To-Assembly Bin Code |
|
BC Warehouse option |
|
From-Assembly Bin Code |
|
BC Warehouse option |
|
Asm.-to-Order Shpt. Bin Code |
|
BC Warehouse option |
|
To-Project Bin Code |
|
BC Warehouse option |
|
Asm. Consump.
Whse. Handling |
|
BC Warehouse option |
|
Project Consump. Whse. Handling |
|
BC Warehouse option |
|
Base Calendar Code |
|
BC Warehouse option |
|
Use ADCS |
|
|
|
Tax Area Code |
|
BC taxes map to Tax
Areas (table 318, page 464) and Jurisdictions (table 320, page 466) |
|
Tax Exemption No. |
|
|
|
Do Not Use For Tax Calculation |
|
|
|
Provincial Tax Area Code |
|
|
|
SAT Address ID |
|
For Community
Development Financial Institution reporting |
|
SAT State Code |
|
For Community
Development Financial Institution reporting |
|
SAT Municipality Code |
|
For Community
Development Financial Institution reporting |
|
SAT Locality Code |
|
For Community
Development Financial Institution reporting |
|
SAT Suburb ID |
|
For Community
Development Financial Institution reporting |
|
ID Ubicacion |
|
For Community
Development Financial Institution reporting |
|
System ID |
|
System Generated |
|
Created At |
|
System Generated |
|
Created By |
|
System Generated |
|
Modified At |
|
System Generated |
|
Modified By |
|
System Generated |
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!