Customer Import Guide - Revision history

Freddy at 15:24, 15 July 2019

2019-07-15T15:24:47Z

Freddy at 16:27, 28 January 2019

2019-01-28T16:27:01Z

Freddy at 19:27, 10 January 2019

2019-01-10T19:27:15Z

Freddy at 15:38, 24 October 2018

2018-10-24T15:38:48Z

Freddy at 14:10, 24 October 2018

2018-10-24T14:10:09Z

Freddy at 19:27, 16 October 2018

2018-10-16T19:27:41Z

Freddy at 12:52, 26 September 2018

2018-09-26T12:52:13Z

Freddy at 14:37, 25 September 2018

2018-09-25T14:37:32Z

Freddy at 14:34, 25 September 2018

2018-09-25T14:34:16Z

Freddy: /* Customer Import Reconciliation */

2018-09-25T13:49:58Z

‎Customer Import Reconciliation

@@ Line 77: / Line 77: @@
 '''f6 - ZipCode''' - Physical Address Zip Code (you can use zip+4 if you have it)
-http://www.abiscorp.com/faq/index.php?title=Special:Preferences
 '''f7 - Phone''' - Main phone number for the organization

@@ Line 55: / Line 55: @@
 '''Map Fields:''' Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping.  Repeat for any red lines on the left that should be mapped.  If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.
-'''Try To Match Existing Orgs:''' Check this box to turn on additional logic that looks through your existing customers in Adjutant and tries to match each record in the spreadsheet with one in Adjutant. If the import program finds a match, it will update that customer's information with the info in the spreadsheet. The program matches on custno, then the first 5 characters of company name and the first 5 characters of address1, then city.
+'''Try To Match Existing Orgs:''' Check this box to turn on additional logic that looks through your existing customers in Adjutant and tries to match each record in the spreadsheet with one in Adjutant. If the import program finds a match, it will update that customer's information with the info in the spreadsheet. The program matches on custno, then the first 5 characters of company name and the first 5 characters of address1, then city.  This feature can be used to update organization information other than the company name and address details, which will not be changed.
 This box should be checked if you are attempting to update existing organizations with an import file that has custnos entered.  If this box is unchecked, and the import file contains custnos that already exist, the import process will create new organizations for the duplicates using the default org numbering logic.

← Older revision		Revision as of 19:27, 10 January 2019
Line 1:		Line 1:

−	==General Import ~~Template File~~ Notes==	+	==General Data Import Notes==

−	*Template files are typically generated from their respective Import screen using an 'Export Template' button.	+	Refer to the [[Data Import General Information]] page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.
−	*Using the 'Export Template' button from an updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors.
−	*Templates generally (but not in all cases) contain 3 rows of header information.
−	**The first row is generally labelled with f1 through f## and is used to give a consistent column id to ~~each data column. Do not remove this row unless instructed.~~
−	**The second row is labelled with the ~~column data/field name. The values in this row are used~~ for ~~the file mapping screen. Editing these values is generally not needed~~ and ~~may make the field mapping process difficult.~~
−	**The third row (if present) is labelled either with the same values from row 2, ~~or with more detailed field descriptions. The third row is available to create a customer-friendly name for the associated data column.~~
−	***The third row should be removed from the source file prior to importing. It will cause errors since it will be treated as ~~the first import record on the file.~~
−	Import files MUST always be saved as ~~'Microsoft Excel 5.0/95 Workbook (.xls)' format until further notice. The import screens will generate errors if the file type is not correct.~~
−
−	*It is a good idea to ~~perform a Mapping Table Import~~ using ~~a current source list before beginning on any imports. Without a current mapping table,~~ the ~~quality of imports can be compromised. The Mapping Table Import only needs to be run once on a newly set up Adjutant system. It does not need to be run before each import.~~
−	**Export a current ~~list from the Mapping Table Import screen from an updated system (or contact your Implementation Consultant~~ for ~~an updated file).~~
−	**Perform a Mapping Table Import on the target system with the XLS file from the step above.

← Older revision		Revision as of 15:38, 24 October 2018
Line 296:		Line 296:

	[[Category: Address Book]]		[[Category: Address Book]]
−	[[Category: ~~Conversion~~ Guides]]	+	[[Category: Import Guides]]

@@ Line 3: / Line 3: @@
 *Template files are typically generated from their respective Import screen using an 'Export Template' button.
-*Using the 'Export Template' button from an updated system will help ensure that you provide the customer with the most up-to-date import file, and will help avoid errors.
+*Using the 'Export Template' button from an updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors.
 *Templates generally (but not in all cases) contain 3 rows of header information.
 **The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed.
-**The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the mapping process difficult.
+**The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult.
-**The third row is labelled with the same values from row 2, an is available to create a customer-friendly name for the associated data column.
+**The third row (if present) is labelled either with the same values from row 2, or with more detailed field descriptions.  The third row is available to create a customer-friendly name for the associated data column.
 ***The third row should be removed from the source file prior to importing.  It will cause errors since it will be treated as the first import record on the file.
 *Import files MUST always be saved as 'Microsoft Excel 5.0/95 Workbook (*.xls)' format until further notice. The import screens will generate errors if the file type is not correct.
-*It is a good idea to perform a Mapping Table Import using a current source list before beginning on any imports.  Without a current mapping table, the quality of imports can be compromised.
+*It is a good idea to perform a Mapping Table Import using a current source list before beginning on any imports.  Without a current mapping table, the quality of imports can be compromised. The Mapping Table Import only needs to be run once on a newly set up Adjutant system.  It does not need to be run before each import.
-**Export a current list from a good source (such as ABIS)
+**Export a current list from the Mapping Table Import screen from an updated system (or contact your Implementation Consultant for an updated file).
-**Perform a Mapping Table Import on the target system with the XLS file from the step above
+**Perform a Mapping Table Import on the target system with the XLS file from the step above.

← Older revision		Revision as of 19:27, 16 October 2018
Line 275:		Line 275:
	* Run the Update Blank Ship To Tax Tables (UPDATESHIPTOTAX) process to fill in Ship To Tax Tables from the latest tax table data.		* Run the Update Blank Ship To Tax Tables (UPDATESHIPTOTAX) process to fill in Ship To Tax Tables from the latest tax table data.

		+
		+	==Customer Import Database Tables==
		+
		+	Importing customer records can affect the following databases:
		+
		+	'''ENT''' - Each imported organization is assigned a unique ENTID value. This is the keyno. The ENTID value is used to link to other attribute records. However, the ENTID value may be labeled as CUSTID or VENDID in other tables.
		+
		+	'''BILLTO''' - All of the BillTo attributes are stored in this table. Customers marked as BillTo records will have a KEYNO created and linked to the CUSTID (which is the ENTID from the ENT table)
		+
		+	'''SOLDTO''' - All of the SoldTo attributes are stored in this table. Customers marked as SoldTo records will have a KEYNO created and linked to the CUSTID (which is the ENTID from the ENT table)
		+
		+	'''SHIPTO''' - All of the ShipTo attributes are stored in this table. Customers marked as ShipTo records will have a KEYNO created and linked to the CUSTID (which is the ENTID from the ENT table)
		+
		+	'''PCXREF''' - Each attribute record will also create an entry in this table. The PTABLE value for all of these should be ENT, and the TYPE value should match the attribute name from Text1 of the associated attribute rule. The PARENTID and CHILDID values will correspond to ENTIDs from the ENT table.
		+
		+	'''VCONTACT''' - Any contact records added with the Customer Import will create a CONTID record linked to the CUSTID (which is the ENTID from the ENT table)

@@ Line 10: / Line 10: @@
 ***The third row should be removed from the source file prior to importing.  It will cause errors since it will be treated as the first import record on the file.
 *Import files MUST always be saved as 'Microsoft Excel 5.0/95 Workbook (*.xls)' format until further notice. The import screens will generate errors if the file type is not correct.
@@ Line 92: / Line 96: @@
 '''f10 - TaxExempt''' - Enter a 'Y' if the customer is tax exempt. A blank entry is the same as 'N'o
-'''f11 - Custno''' - Customer Number (Organization ID), Leave blank to auto-assign customer numbers.  If you are attempting to update existing organization records, make sure the 'Match Existing Orgs' option is checked - otherwise the import process will create new organizations for any existing, natched custnos.
+'''f11 - Custno''' - Customer Number (Organization ID), Leave blank to auto-assign customer numbers.  If you are attempting to update existing organization records, make sure the 'Match Existing Orgs' option is checked - otherwise the import process will create new organizations for any existing, matched custnos.
 '''f12 - Terms''' - Default payment terms. This must match a value in the TERMS rule.

← Older revision		Revision as of 14:37, 25 September 2018
Line 270:		Line 270:

	* Run the Update Blank Ship To Tax Tables (UPDATESHIPTOTAX) process to fill in Ship To Tax Tables from the latest tax table data.		* Run the Update Blank Ship To Tax Tables (UPDATESHIPTOTAX) process to fill in Ship To Tax Tables from the latest tax table data.
		+

@@ Line 30: / Line 30: @@
 '''Customer Attributes''' - The customer import process can attach all of the required customer attributes and complete many of the data fields in each attribute screen.  If additional attributes need to be assigned during import, the attribute must be flagged to display on the Import screen in the ATT_ENT rule.
@@ Line 230: / Line 246: @@
 ==Customer Import Reconciliation==
-Every customer's import data is different
+Reconciling imported data should begin with spot-checking several records field-by-field for complete data import.  Pick records from the source file that have the most data columns filled in.  Verify that all source file data fields imported correctly and display as expected.

← Older revision		Revision as of 13:49, 25 September 2018
Line 230:		Line 230:
	==Customer Import Reconciliation==		==Customer Import Reconciliation==

−		+	Every customer's import data is different