Configurable Item (SOC) Import Guide - Revision history

Freddy at 21:08, 31 March 2023

2023-03-31T21:08:27Z

Tcampbell: /* Configurable Item (SOC) Import Screen (SOCIMPORT) */

2022-12-28T14:22:21Z

‎Configurable Item (SOC) Import Screen (SOCIMPORT)

Tcampbell at 14:21, 28 December 2022

2022-12-28T14:21:54Z

Freddy at 19:25, 10 January 2019

2019-01-10T19:25:16Z

Freddy at 21:42, 19 December 2018

2018-12-19T21:42:56Z

Freddy at 21:41, 19 December 2018

2018-12-19T21:41:22Z

Show changes

Freddy at 21:19, 19 December 2018

2018-12-19T21:19:42Z

Freddy at 20:29, 19 December 2018

2018-12-19T20:29:09Z

Freddy at 19:47, 19 December 2018

2018-12-19T19:47:56Z

Freddy at 19:20, 19 December 2018

2018-12-19T19:20:26Z

← Older revision		Revision as of 21:08, 31 March 2023
Line 80:		Line 80:


−	'''KeyNo''' - Keyno value of the exported SOC Question. This column should be cleared of all data prior to import, but the column position or header should not be changed.	+	'''KeyNo''' - Keyno value of the exported SOC Question. This column should be cleared of all data prior to import, but the column position or header should not be changed. The keyno value should only be used for replacing existing data by matching the keyno to SOCQUESTION.KEYNO. If matched, the SOC import will replace data and rebuild the keynos.

	'''Item''' - Item number in Adjutant		'''Item''' - Item number in Adjutant

@@ Line 47: / Line 47: @@
 '''Menu Location''' Transaction>>Import/Export>>Import Master>>Configurable Item Import
-'''URL'' ImportMaster_S.htm?mode=SOCIMPORT
+'''URL''' ImportMaster_S.htm?mode=SOCIMPORT
 [[image:socimport.png]]
 ==Configurable Item (SOC) Export Screen (SOCEXPORT)==

@@ Line 1: / Line 1: @@
+__NOTOC__
 ==General Data Import Notes==
@@ Line 43: / Line 43: @@
 '''RCode (Report Code): ''' Carefully review the report code values for all questions and ensure that there are no mismatched codes. Review to ensure that questions of the same type all use the same report code. For example, all weight questions should use 'W', rather than some using 'W', and some using 'WT'. If the customer needs multiple versions of the same question, such as Punch Code 1 and Punch Code 2, make sure the associated report codes are consistent.
 ==Configurable Item (SOC) Export Screen (SOCEXPORT)==
-Menu Location: Transaction>>Importers/Exporters>>Item Control>>Configurable Item (SOC) Export
+'''Menu Location''' Transaction>>Import/Export>>Import Master>>Configurable Item (SOC) Import >>> Export Tab
-[[File:SOCEXPORT.png]]
+[[image:SOCEXPORT.png]]
 '''Class:''' Enter a single item class value or a range to filter the SOC Export results by Item Master class.
@@ Line 62: / Line 74: @@
 '''Owner:''' Enter an Owner name to filter the SOC Export by Owner.

← Older revision		Revision as of 19:25, 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 21:42, 19 December 2018
Line 33:		Line 33:
	Be extremely careful when copying data in Excel that you don't accidentally increase values down the page. Use the correct procedures in Excel to copy, rather than copy and sequence, data down columns.		Be extremely careful when copying data in Excel that you don't accidentally increase values down the page. Use the correct procedures in Excel to copy, rather than copy and sequence, data down columns.

−	The SOC Import will add records if they do not exist, but can also be used to update existing records.	+	The SOC Import will add records if they do not exist, but can also be used to update existing records. The SOC Import will also create the Configurable Item (SOC) attribute for the associated item, if it doesn't already exist.

@@ Line 118: / Line 118: @@
 '''Unit''' - UNit of measure associated with the Additional Item number
-'''PAdjustable''' -
+'''PAdjustable''' - Enter 'Y' to check the Price/Cost Adjust box in the Price and/or Other Adjustment Settings area
-priceadj
+'''PriceAdj''' - Enter the dollar value for the price adjustment, or if no price adjustment, enter 0
-qnum1
+'''QNum1''' - Price/Cost Adjustment question number. Enter the SOC question number to fill in the 'or From Q#' value for the Price/Cost Adjust fields
-conquest
+'''ConQuest''' - Enter 'Y' to check the Controlling Qty box
-showadj
+'''ShowAdj''' - Enter 'Y' to check the Display Price Adjustment box
-otheradj
+'''OtherAdj''' - Enter the dollar value for the Other Adjustment field, or if not other adjustment, enter 0.

← Older revision		Revision as of 20:29, 19 December 2018
Line 85:		Line 85:

	Required fields are indicated with an * ; Required fields that can be auto-filled by the Import screen are indicated with **		Required fields are indicated with an * ; Required fields that can be auto-filled by the Import screen are indicated with **
		+
		+	'''KeyNo''' - Keyno value of the exported SOC Question. This column should be cleared of all data prior to import, but the column position or header should not be changed.
		+
		+	'''Item''' - Item number in Adjutant
		+
		+	'''QuestNo''' - SOC question number
		+
		+	'''Question''' - SOC question text (maximum 50 characters)
		+
		+	'''QType''' - SOC question type code. Valid entries are LIST, TEXT, NUM, and CAL.
		+
		+	'''RCode''' - Report code for the associated question. Question 1 should always be report code A. The Length question is always report code B and generally the second question. Some other standard report codes are S=Roof Slope, Q=Square Feet, and W=Weight.
		+
		+	'''CalcVal''' - Enter 'Y' to indicate this is a calculated value, which sets the CALC checkbox. Enter 'N' otherwise.
		+
		+	'''CalcExp''' - Enter a custom formula using report codes, numerical values, and Excel-style formula codes. An example of the formula structure would be (B/2) + 100.
		+
		+	'''DecQty''' - Updates the Dec. Quantity for the associated question. Valid entries are 0 through 5.
		+
		+	'''InOnly''' - Enter 'Y' to check the Inches box for the associated question. Either the InOnly or the FtInOnly box should be checked for length questions, but not both.
		+
		+	'''FtInOnly''' - Enter 'Y' to check the Ft-Inch box for the associated question. Either the InOnly or the FtInOnly box should be checked for length questions, but not both.
		+
		+	'''MinLen''' - Enter the minimum length, if needed, for the length question. Enter 0 if there is no minimum length.
		+
		+	'''MaxLen''' - Enter the maximum length, if needed, for the length question. Enter 0 if there is no maximum length.
		+
		+	'''Inc''' - Enter the length increment value (in decimal form) to control the valid length entries. For example, to limit length entries by the 16th of an inch, enter 0.0625.
		+
		+	'''AItem''' - Additional item number that can be used for contract or special pricing options
		+
		+	'''Unit''' - UNit of measure associated with the Additional Item number
		+
		+	'''PAdjustable''' -
		+
		+	priceadj
		+
		+	qnum1
		+
		+	conquest
		+
		+	showadj
		+
		+	otheradj
		+	qnum4
		+	qnum2
		+	qnum3
		+	costadj
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+

	'''*f1 - Item''' - Item number/code (20 character max, alphanumeric, no spaces allowed). The following special characters are allowed (. - + / _)		'''*f1 - Item''' - Item number/code (20 character max, alphanumeric, no spaces allowed). The following special characters are allowed (. - + / _)

@@ Line 53: / Line 53: @@
 ==Configurable Item (SOC) Export Screen (SOCEXPORT)==
-'''Item File Name/Browse:''' Use the Browse button to locate and select the completed Item Master import template file (in XLS format).
+==Configurable Item (SOC) Import Screen (SOCIMPORT)==
-'''Export Template:''' Generates a blank Item Master import template file
+Menu Location: Transaction>>Importers/Exporters>>Item Control>>Configurable Item (SOC) Import
-'''Select Attributes:''' Attributes selected during the import process will be applied to ALL imported items. Review and verify that the attributes are set correctly before each import. Correcting associated attributes can be a complicated process. Attributes show up in this list based on the 'Show on Import' (Logic2) field in the Item Attributes (ITEMATTRIB) Rule Maintenance record.
+[[File:SOCIMPORT1.png]]

@@ Line 16: / Line 16: @@
-==Item Master Import Notes==
+==Configurable Item (SOC) Import Notes==
 ===Timing and Preparation===
-The Item Master Import should occur early in the setup process, because item records are essential for setup testing, training, and user testing in most of the applications. The Item Control rules should be complete prior to importing. The [[Item Control Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing item master records.
+The Configurable Item (SOC) Import should occur soon after the Item Master records have been imported and reviewed. Importing the SOC details is essential for testing configurable items in the sales and production processes.
-Separating the import files by item type can also help with completing the required unit of measure values in the file. Customer item control data generally does not have the same level of unit related fields as Adjutant, and there may be many blank unit related columns that must be completed prior to importing.
+===General Notes===
-The Item Master import is just the first step in building a complete inventory system.  There are multiple other imports required to complete setting up the Item Control records.  These other imports, such as quantities, cost tiers, coil inventory, configurations, and bills of material, require that the base item record is created first, and should be completed soon after the Item Master import.
+Be extremely careful when copying data in Excel that you don't accidentally increase values down the page. Use the correct procedures in Excel to copy, rather than copy and sequence, data down columns.
-Occasionally, additional item records must be created in order to accomodate a new selling or production procedure, or accomodate a shift in processes due to difference between a legacy system and Adjutant. When creating new item records for these types of situations, be sure to complete any other required imports for the new item codes.
+==Configurable Item (SOC) Import File Data Scrubbing==
-===General Notes===
+'''Keyno: ''' Remove the data in the keyno column before importing. The keyno value is not used during the import, and it can lead to confusion when reviewing and researching SOC imports. The SOC import process will generate new keyno values upon import, and the ones on the import file will no longer relate to anything.
-'''OHF Records'''  If you are importing items for a single warehouse/single owner location, the Item Master import can build the default OHF records automatically.  If you are importing for a multi-warehouse and/or multi-owner locations, and ALL imported items on the file are valid for ALL OHF combinations, the Item Master import can also automatically build the needed OHF records for all combinations. If some items are exclusive to certain OHF records, it may be easiest to handle this with separate Item Master import files. Or, depending on the situation, you may be able to use the Item Import (DET) file, also known as the Min/Max file to create the needed OHF combinations.
+'''QuestNo: ''' Re-sort the import file by item and look for any question numbering gaps or duplicates.
-'''Item Attributes'''  The Item Master import can automatically create the Catch Weight attribute if the CW columns is 'Y' and the related CW columns are filled in. It will also create the Coil Lot (Coil Receipt Defaults) attribute if the Coil column is 'Y'.
+'''Question: ''' Review the import file to standardize question labels for spelling and capitalization. Avoid importing things like 'LENGTH', 'Length', and 'length' for the same type of question. Make them all match before importing.
-Another reason to consider separating the import files is automatically apply other attributes to certain item types during import. For example, the Buyout, Purchase in QuickBuy, Warning Note, and other special attributes can be auto-assigned to every item on the import if the attribute is flagged during the import. To set an attribute as available in the Item Master import, set the 'Show in Import' (Logic2) option in the Item Attributes (ITEMATTRIB) rule.
+'''RCode (Report Code): ''' Carefully review the report code values for all questions and ensure that there are no mismatched codes. Review to ensure that questions of the same type all use the same report code. For example, all weight questions should use 'W', rather than some using 'W', and some using 'WT'. If the customer needs multiple versions of the same question, such as Punch Code 1 and Punch Code 2, make sure the associated report codes are consistent.
-==Item Master Import Screen (ITEMIMPORT)==
+==Configurable Item (SOC) Import Screen (SOCIMPORT)==
-Menu Location: Transaction>>Importers/Exporters>>Item Control>>Item Master Import
+Menu Location: Transaction>>Importers/Exporters>>Item Control>>Configurable Item (SOC) Import
-[[File:ITEMIMPORT.png]]
+[[File:SOCIMPORT.png]]
@@ Line 92: / Line 96: @@
-==Item Master Import File Definitions==
+==Configurable Item (SOC) Import File Definitions==
 Required fields are indicated with an * ; Required fields that can be auto-filled by the Import screen are indicated with **
@@ Line 201: / Line 205: @@
-==Item Master Import Reconciliation==
+==Configurable Item (SOC) 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.
@@ Line 213: / Line 217: @@
-==Item Master Import Additional Steps==
+==Configurable Item (SOC) Import Additional Steps==
 Complete the required additional imports based on how the item will be used. For example:
@@ Line 226: / Line 230: @@
-==Item Master Import Database Tables==
+==Configurable Item (SOC) Import Database Tables==
 '''ITEMMASTER''' - Each imported item creates a unique IKEY tied to the ITEM value. Most of the Item Master fields are imported to the ITEMMASTER table.