Solution Code Import Guide - Revision history

Freddy at 15:34, 25 July 2025

2025-07-25T15:34:22Z

Tcampbell at 17:00, 7 December 2022

2022-12-07T17:00:24Z

Tcampbell at 23:43, 5 December 2022

2022-12-05T23:43:07Z

Tcampbell at 23:42, 5 December 2022

2022-12-05T23:42:23Z

Tcampbell at 23:42, 5 December 2022

2022-12-05T23:42:09Z

Freddy at 20:46, 30 April 2019

2019-04-30T20:46:06Z

Freddy at 20:29, 30 April 2019

2019-04-30T20:29:40Z

Freddy at 20:49, 14 January 2019

2019-01-14T20:49:40Z

Freddy: Created page with " ==General Data Import Notes== Refer to the Data Import General Information page for information and guidance on general import timeline, formatting import templates, as..."

2019-01-14T20:45:11Z

Created page with " ==General Data Import Notes== Refer to the Data Import General Information page for information and guidance on general import timeline, formatting import templates, as..."

New page

==General Data Import Notes==

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.

==Solution Code Import Notes==

===Timing and Preparation===

The Solution Code Import is a foundational step in using the Task Management or Time Billing systems. It should occur as soon as the required Task Management Rule Maintenance records have been completely set up. Follow the [[Task Management Setup Guide]] for details on the required setup procedures.

The Solution Code Import can also be run to update existing task records where the task code matches.

==Solution Code Import File Data Scrubbing==

Every customer's data will have different issues that need addressing. Some of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing. This is why it is critically important to perform an early import, and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import. Some common things that need attention during Sales Order data scrubbing include:

* '''SolCode''' - Work with customer to develop a solution code numbering/naming scheme that makes sense. Consider how the solution codes will sort in look-ups, and what formatting features of the solution code/name will be most helpful to end-users. If using a numbered system, carefully review for duplicates, and make sure that Excel auto-fill hasn't altered any of the numbers.

* '''Descrip''' - Standardize terms and review spelling on the descriptions. If time allows, standardize capitalization.

* If duplicate solution codes (based on the f1 - SolCode column) are found in the file, only the last solution code found on the spreadsheet will be imported. Review carefully for duplicated solution codes.

==Solution Code Import Screen (IMPPORTGLGRP)==

Menu Location: Transaction>>Importers/Exporters>>Task and Time Billing>>Solution Code Import

[[File:IMPORTGLGRP.png]]

'''File Name/Browse:''' Use the Browse button to locate and select the completed Solution Code Import template file (in XLS format).

'''Export Template:''' Generates a blank Solution Code Import template file

'''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.

==Solution Code Import File Definitions==

Required fields are indicated with an *

'''*f1 - SolCode''' - Solution code number or name (max 20 characters)

'''*f2 - Descrip''' - Solution code description (max 50 characters)

'''f3 - Notes''' - Expanded notes area for the solution code. The import field is limited to 200 characters, but the notes field on the Solution Codes screen will accept more.

'''*f4 - BillAs''' - Enter the Adjutant item number that the solution code will use in billing. Must be a valid item number.

'''f5 - EqHours''' - Enter the default Time Sheet hours to use for this code (numeric, up to 3 decimals)

'''f6 - SkipBNote''' - Enter a 'Y' to check the Skip Billing Notes Prompt box on the Solution Codes screen. Leave blank or enter 'N' to leave the box unchecked.

'''f7 - GLGroup''' - Enter a GL Group name to control the GL posting for this solution code. Must be a valid GL Group.

'''f8 - HideLabor''' - Enter a 'Y' to check the Hide Labor Lines box on the Solution Codes screen. Leave blank or enter 'N' to leave the box unchecked.

==Solution Code Import Reconciliation==

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.

Run the Solution Code List report for the imported records. Review the report for basic details and look for any missing or incorrect records.

==Solution Code Import Additional Steps==

Manually update any additional details, such as detailed notes, parts, work categories, and any other fields that are not available on the import.

==Solution Code Import Database Tables==

'''SOLCODE''' - Each imported solution code creates a new KEYNO in the this table.

[[Category: Tasks and Time Billing]]
[[Category: Import Guides]]

← Older revision		Revision as of 15:34, 25 July 2025
Line 78:		Line 78:


−	[[Category: ~~Tasks and Time Billing~~]] [[Category: ~~Import Guides~~]] [[Category: ~~Work Order Management~~]]	+	[[Category: Task Management]] [[Category: Time and Materials]] [[Category:Import/Export]]

← Older revision		Revision as of 17:00, 7 December 2022
Line 1:		Line 1:
		+	__NOTOC__
	===General Information===		===General Information===

← Older revision		Revision as of 23:43, 5 December 2022
Line 10:		Line 10:


−	[[image:~~IMPORTGLGRP~~.png]]	+	[[image:solution_code_import_1.png]]

← Older revision		Revision as of 23:42, 5 December 2022
Line 10:		Line 10:


−	[image:IMPORTGLGRP.png]	+	[[image:IMPORTGLGRP.png]]

← Older revision		Revision as of 20:49, 14 January 2019
Line 61:		Line 61:

	'''f8 - HideLabor''' - Enter a 'Y' to check the Hide Labor Lines box on the Solution Codes screen. Leave blank or enter 'N' to leave the box unchecked.		'''f8 - HideLabor''' - Enter a 'Y' to check the Hide Labor Lines box on the Solution Codes screen. Leave blank or enter 'N' to leave the box unchecked.
−

@@ Line 1: / Line 1: @@
-==General Data Import Notes==
+==How To Access==
-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.
+'''Menu Location''' Transaction >> Importers/Exporters >> Other>> Solution Code Import
-==Solution Code Import Notes==
+[image:IMPORTGLGRP.png]
-The Solution Code Import is a foundational step in using the Task Management or Time Billing systems. It should occur as soon as the required Task Management Rule Maintenance records have been completely set up. Follow the [[Task Management Setup Guide]] for details on the required setup procedures.
+===Fields/Filters===
-The Solution Code Import can also be run to update existing task records where the task code matches.
+'''File Name/Browse:''' Use the Browse button to locate and select the completed Solution Code Import template file (in XLS format).
-==Solution Code Import File Data Scrubbing==
+'''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.
-Every customer's data will have different issues that need addressing.  Some of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing.  This is why it is critically important to perform an early import, and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import. Some common things that need attention during Solution Code data scrubbing include:
+===Solution Code Import File Definitions===
-* '''SolCode''' - Work with customer to develop a solution code numbering/naming scheme that makes sense. Consider how the solution codes will sort in look-ups, and what formatting features of the solution code/name will be most helpful to end-users. If using a numbered system, carefully review for duplicates, and make sure that Excel auto-fill hasn't altered any of the numbers.
+Required fields are indicated with an *
-* '''Descrip''' - Standardize terms and review spelling on the descriptions. If time allows, standardize capitalization.
+'''*SolCode''' - Solution code number or name (max 20 characters)
-* If duplicate solution codes (based on the f1 - SolCode column) are found in the file, only the last solution code found on the spreadsheet will be imported. Review carefully for duplicated solution codes.
+'''*Descrip''' - Solution code description (max 50 characters)
-==Solution Code Import Screen (IMPSOLCODE)==
+'''EqHours''' - Enter the default Time Sheet hours to use for this code (numeric, up to 3 decimals)
-Menu Location: Transaction>>Importers/Exporters>>Task and Time Billing>>Solution Code Import
+'''SkipBNote''' - Enter a 'Y' to check the Skip Billing Notes Prompt box on the Solution Codes screen. Leave blank or enter 'N' to leave the box unchecked.
-[[File:IMPSOLCODE.png]]
+'''GLGroup''' - Enter a GL Group name to control the GL posting for this solution code. Must be a valid GL Group.
-'''File Name/Browse:''' Use the Browse button to locate and select the completed Solution Code Import template file (in XLS format).
+'''HideLabor''' - Enter a 'Y' to check the Hide Labor Lines box on the Solution Codes screen. Leave blank or enter 'N' to leave the box unchecked.
-'''Export Template:''' Generates a blank Solution Code Import template file
+==Solution Code Import Notes==
-==Solution Code Import File Definitions==
+The Solution Code Import can also be run to update existing task records where the task code matches.
-'''*f1 - SolCode''' - Solution code number or name (max 20 characters)
+===Solution Code Import File Data Scrubbing===
-'''*f2 - Descrip''' - Solution code description (max 50 characters)
+Every customer's data will have different issues that need addressing.  Some of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing.  Therefore it is critically important to perform an early import and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import. Some common things that need attention during Solution Code data scrubbing include:
-'''f3 - Notes''' - Expanded notes area for the solution code. The import field is limited to 200 characters, but the notes field on the Solution Codes screen will accept more.
+* '''SolCode''' - Work with customers to develop a solution code numbering/naming scheme that makes sense. Consider how the solution codes will sort in lookups, and what formatting features of the solution code/name will be most helpful to end-users. If using a numbered system, carefully review for duplicates, and make sure that Excel autofill hasn't altered any of the numbers.
-'''*f4 - BillAs''' - Enter the Adjutant item number that the solution code will use in billing. Must be a valid item number.
+* '''Descrip''' - Standardize terms and review spelling on the descriptions. If time allows, standardize capitalization.
-'''f7 - GLGroup''' - Enter a GL Group name to control the GL posting for this solution code. Must be a valid GL Group.
+* If duplicate solution codes (based on the SolCode column) are found in the file, '''only the last solution code found on the spreadsheet will be imported.''' Review carefully for duplicated solution codes.
-'''f8 - HideLabor''' - Enter a 'Y' to check the Hide Labor Lines box on the Solution Codes screen. Leave blank or enter 'N' to leave the box unchecked.
+===Solution Code Import Reconciliation===
+Reconciling imported data should begin with spot-checking several records field-by-field for complete data import.  Pick records with the most data columns filled in.  Verify that all source file data fields imported correctly and display as expected.
 Run the Solution Code List report for the imported records. Review the report for basic details and look for any missing or incorrect records.
+===Solution Code Import Additional Steps===
 Manually update any additional details, such as detailed notes, parts, work categories, and any other fields that are not available on the import.
 '''SOLCODE''' - Each imported solution code creates a new KEYNO in this table.
-[[Category: Tasks and Time Billing]]
+[[Category: Tasks and Time Billing]] [[Category: Import Guides]] [[Category: Work Order Management]]