Difference between revisions of "Configurable Item (SOC) Import Guide"

From Adjutant Wiki

 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
__NOTOC__
 +
==General Data Import Notes==
  
==General Import Template File 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.
  
*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 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.
 
  
 
+
==Configurable Item (SOC) Import Notes==
==Item Master Import Notes==
 
  
 
===Timing and Preparation===
 
===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.  
 
 
Item Master import files are commonly separated into multiple imports based on item type, department, category, or any number of item grouping details. Item Department is a common file grouping, because if the import files are separated by department, it is easy to assign the correct department attributes during the import.
 
 
 
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.
 
 
 
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.
 
 
 
The Item Master import does not generally need to be run again as a go-live import. Once the base item records are imported and all items are represented, there is generally no need to re-import.
 
 
 
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.
 
 
 
  
  
 
===General Notes===
 
===General Notes===
  
'''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.  
+
The import template file for the SOC Import is generated by using the Export Configurable (SOC) Items screen, detailed below. The Export Configurable Items (SOC) can be requested from any system with configurable items. The export screen has multiple filters to help with selecting the right records for building an import file. The data can also be filled in manually, but it is much easier to use existing SOC records as a reference when creating a new import file.
 
 
'''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'.
 
 
 
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.
 
 
 
 
 
 
 
==Item Master 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 Item Master data scrubbing include:
 
 
 
* '''Units''' - It is common for customer item data to only include a single unit of measure value for each item. Review all item import files carefully and fill in any required unit fields with the correct unit of measure for the different transaction types (purchase, stock, sell). Setting up items with the wrong units can have dramatic effects on costing, GL postings, and other transactions throughout Adjutant. Review the unit details carefully with the customer before importing. It can be difficult to correct unit-related issues after item records have been used.
 
 
 
* '''Cost''' - Verify that the current cost is entered in the AvgCost column for each item. Also make sure the stock unit of measure relates to the AvgCost value, because it will default to use the stock unit for the AvgCost. When imported, it sets the correct cost for the item for sales orders and purchase orders.
 
 
 
* '''Unit Weights''' - Unit weight can be critically important throughout multiple Adjutant systems and processes such as production and shipping. It is best practices to make sure that all sold items have a unit weight that corresponds to the stock unit imported.  
 
  
 +
If you intend to use most of the field data from an SOC Export file, review the data critically before attempting to associate it with a customer's item file. We do not want to propogate bad data.
  
 +
The safest practice is to pick an accurate example of each question type and copy the single, reviewed question down to all new customer items. This way, the same data is used for all questions.
  
 +
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.
  
==Item Master Import Screen (ITEMIMPORT)==
+
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.
  
Menu Location: Transaction>>Importers/Exporters>>Item Control>>Item Master Import
 
  
[[File:ITEMIMPORT.png]]
 
  
 +
==Configurable Item (SOC) Import File Data Scrubbing==
  
'''Item File Name/Browse:''' Use the Browse button to locate and select the completed Item Master import template file (in XLS format).  
+
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.  
  
'''Export Template:''' Generates a blank Item Master import template file
+
The SOC import file is generally built 'from scratch' or by exporting a known good list of SOC items and editing it heavily to match the customer's data. Because there is typically no single source data file from the customer, creating the SOC import file will typically involve pulling bits of data from one or more customer files to create the import. Below are some of the key data columns to review carefully prior to import:
  
'''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.
+
'''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.  
  
'''Default Warehouse:''' Sets the warehouse location for any imported items where the WHSE column on the import file is left blank. This list is populated by Warehouse Control records that have been created.
+
'''Item: ''' When copying data into the file, review the item number fields carefully. Carefully review any items that are being renumbered in Adjutant and make sure the item numbers are correct. Review for any transposed numbers or faulty copy and paste issues.  
  
'''Default Owner:''' Sets the inventory owner for any imported items where the OWNERID column on the import file is left blank. This list is populated with Organization records that have the Inventory Owner attribute.  
+
'''QuestNo: ''' Re-sort the import file by item and look for any question numbering gaps or duplicates.  
  
'''Default HedlFor:''' Sets the inventory holder for any imported items where the HELDFOR column on the import file is left blank. This list is populated from the Item Held For Codes (HOLDER) Rule Maintenance record. If a catch-all code such as 'DEF' is used, make sure the HOLDER rule is set up properly.  
+
'''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.
  
'''Create All Combinations:''' Selecting this box will create separate OHF (ITEMDET) records for each OHF combination based on the owners and held for records that have been set up.
+
'''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.
  
'''Unit Group:''' Sets the unit group for any imported items where the UNITGRP column is left blank
+
==Configurable Item (SOC) Import Screen (SOCIMPORT)==
  
'''Unit:''' Sets ALL unit values for any imported items where any unit-related column (PURUNIT, STKUNIT, SELLUNIT, etc) is left blank
+
'''Menu Location''' Transaction>>Import/Export>>Import Master>>Configurable Item Import
  
'''Validate Units:''' Selecting this box will verify that all unit values on the import are valid defined units in the Unit of Measure (UNITS) rule, and that they are valid units for the selected Unit Group. For example, if FT is not defined as a valid unit in the IND Unit Group according to the rule, it will not pass verification.
+
'''URL''' ImportMaster_S.htm?mode=SOCIMPORT
  
'''Ignore Bad Vendnos:''' Selecting this box will import the VENDNO column data as-is, without verifying that the vendor number exists in Address Book.  
+
'''Item File Name/Browse:''' Use the Browse button to locate and select the completed SOC import template file (in XLS format).
  
'''Check for Inactive Items:''' Selecting this box will check all imported item numbers against existing item numbers that have been marked as inactive, and will reject the imported items if there is a match.
 
  
'''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.  
+
[[image:socimport.png]]
  
 +
==Configurable Item (SOC) Export Screen (SOCEXPORT)==
  
 +
'''Menu Location''' Transaction>>Import/Export>>Import Master>>Configurable Item (SOC) Import >>> Export Tab
  
==Item Master Import File Definitions==
+
'''URL''' ImportMaster_S.htm?mode=SOCIMPORT
  
Required fields are indicated with an * ; Required fields that can be auto-filled by the Import screen are indicated with **
 
  
'''*f1 - Item''' - Item number/code (20 character max, alphanumeric, no spaces allowed). The following special characters are allowed (. - + / _)
+
[[image:SOCEXPORT.png]]
  
'''*f2 - Descrip''' Item Description (99 alphanumeric character max)
+
'''Class:''' Enter a single item class value or a range to filter the SOC Export results by Item Master class.
  
'''**f3 - UnitGrp''' -  Item Unit of Measure Group (examples are LENGTH, WEIGHT, TIME, IND). Must match a value in the UNITS rule.
+
'''Item Range:''' Enter an item code range to filter the SOC Export results by all item numbers that fall between the from and to values.
  
'''**f4 - PurUnit''' - Item purchase unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)
+
'''Item Like Block:''' Enter up to 6 item-like searches to filter the SOC Export results by custom item number searches.
  
'''**f5 - StkUnit''' Item stocking unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)
+
'''Commodity Code:''' Enter a single commodity code or a range to filter the SOC Export results by Item Master commodity code.
  
'''**f6 - SellUnit''' -  Item sell unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)
+
'''Held For:''' Enter a Held For name to filter the SOC Export by Held For.
  
'''*f7 - AvgCost''' -  Item’s current average cost per stocking unit
+
'''Owner:''' Enter an Owner name to filter the SOC Export by Owner.
  
'''*f8 - Price''' -  Item’s price per pricing unit
 
  
'''**f9 - PriceUnit''' -  Item’s pricing unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)
 
  
'''**f10 - CostUnit''' -  Item’s costing unit associated with the Standard Cost (STDCOST) value (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)
+
==Configurable Item (SOC) Import File Definitions==
  
'''*f11 - StkFlag''' -  Y if the item is stocked in the warehouse, N if it is not (made to order items are not stocked)
 
  
'''f12 - SerialFlag''' - Y if the item is serialized, N if it is not (serialized items have a serial number for every quantity of 1)
+
'''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.
  
'''f13 - LotFlag''' - Y if the item is lot controlled, N if it is not (all coils are lot controlled).
+
'''Item''' - Item number in Adjutant
  
'''f14 - Vendno''' - The vendor code of  the item’s default supplier
+
'''QuestNo''' - SOC question number
  
'''f15 - Vpartno''' - The default supplier’s item code
+
'''Question''' - SOC question text (maximum 50 characters)
  
'''f16 - HeldFor''' - Item's Held For name from the HOLDER rule. This is generally only used in locations where inventory can be held for other entities. Generally, all items should be imported with the default HeldFor name from the HOLDER rule, unless given specific instructions to create multiple HeldFor records.  
+
'''QType''' - SOC question type code. Valid entries are LIST, TEXT, NUM, and CAL.
  
'''f17 - Whse''' - Enter the warehouse name (not the ID code) for the primary warehouse where these items are located/produced
+
'''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.
  
'''f18 - Taxable''' - Y if the item is taxable, N if it is not
+
'''CalcVal''' - Enter 'Y' to indicate this is a calculated value, which sets the CALC checkbox. Enter 'N' otherwise.
  
'''f19 - UnitW''' - The item’s unit weight per stocking unit
+
'''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.
  
'''f20 - Cubes''' - Used in Warehouse Management System shipping calculations and forms (rare)
+
'''DecQty''' - Updates the Dec. Quantity for the associated question. Valid entries are 0 through 5.
  
'''f21 - DecQty''' - The number of decimals that should be available when entering quantities of the item on a purchase or sales order (valid entries are 0-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.
  
'''f22 - MiscItem''' - Y if the item is miscellaneous, N if it is not
+
'''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.
  
'''f23 - Resell''' - Y if you plan on selling this item, N if you do not. If this field is left blank, the item cannot be added to a sales order.
+
'''MinLen''' - Enter the minimum length, if needed, for the length question. Enter 0 if there is no minimum length.
  
'''f24 - PackCode''' - Item Packing Code (accepts single character letters from A - T). Can be used to group items that should be packed together by this code. (rare)
+
'''MaxLen''' - Enter the maximum length, if needed, for the length question. Enter 0 if there is no maximum length.
  
'''f25 - ABCCode''' - Item ABC ranking code (accepts single character letters from A - Z). Can be used to manually assign ABC rankings to inventory items. The Item ABC Code Assignments screen can be used to automatically assign the ABC Code  based on usage or value, once usage and on-hand quantity information is available. (rarely used during item import)
+
'''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.
  
'''f26 - Pgroup''' - The item’s pricing group. Customer pricing may be broken into item pricing groups; e.g. customer XYZ gets 40% off PANELS, 50% off COLDFORM, and 30% off ACCESSORIES, for component
+
'''AItem''' - Additional item number that can be used for contract or special pricing options
sales. Leaving this field blank can cause pricing issues if pricing is based on price group breakdowns.
 
  
'''f27 - ComCode''' - The item’s commodity code. Commodity codes are used in procurement and determine which suppliers can bid on which items. Commodity Codes can also be used as filters for certain inventory reports.
+
'''Unit''' - UNit of measure associated with the Additional Item number
  
'''f28 - BaseCost''' - The item's base cost. This value can be useful if you are pricing your items using a cost-plus method.
+
'''PAdjustable''' - Enter 'Y' to check the Price/Cost Adjust box in the Price and/or Other Adjustment Settings area
  
'''f29 - ProdLine''' - This field is no longer used
+
'''PriceAdj''' - Enter the dollar value for the price adjustment, or if no price adjustment, enter 0
  
'''*f30 - ItemCat''' - Item’s category for creating transaction categories. Item Categories are combined with Customer Categories to create a Transaction Category that is used to drive revenue and cost to the correct GL accounts. DEF should be entered for most items, unless a specific accounting model has been established based on item category. Review the revenue and cost accounting procedures carefully to determine the desired entries for each item . If left blank, the item record will not be usable until the category is filled in.
+
'''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
  
'''f31 - SqFt''' - The item's square footage per stocking unit
+
'''ConQuest''' - Enter 'Y' to check the Controlling Qty box
  
'''f32 - WarLen''' - If the item has an associated warranty length, enter it here (maximum 5 characters alphanumeric)
+
'''ShowAdj''' - Enter 'Y' to check the Display Price Adjustment box
  
'''f33 - Produce''' - Y if the item is produced in the plant, N if the item is not produced
+
'''OtherAdj''' - Enter the dollar value for the Other Adjustment field, or if not other adjustment, enter 0.
  
'''f34 - SearchCode''' - Custom text that can be used to generate a search screen for items with the same/similar search code value. For example, all items with the search code of 'Trim' will display in a search code display (by double-clicking on the item Search Code field), regardless of their item number or description. (maximum 35 characters, alphanumeric)
+
'''QNum4''' - Other Adjustment question number. Enter the SOC question number to fill in the 'To Q#' value.
  
'''f35 - ProdGrp''' - Item’s product group. Enter one of the following in the column - '''M''' (Material), '''L''' (Labor), '''E''' (Equipment), '''X''' (Expense), or '''S''' (Subcontract). All items must be assigned to one of the 5 system-defined categories that drive revenue and cost accounting.  
+
'''QNum2''' - Pass 1 question number. Enter the SOC question number to fill in the Pass 1 'Multiply Q#' value.
  
'''f36 - OwnerID''' - Item's inventory owner. This is generally only used in locations where inventory can be owned by other entities and the accounting needs to be kept separate. Generally, all items should be imported with the default OwnerID value, unless given specific instructions to create multiple Owner records, and multiple OHF combinations.  
+
'''QNum3''' - Pass 2 question number. Enter the SOC question number to fill in the Pass 2 'Adjustment by Q#' value.
  
'''f37 - iClass''' - Custom text field available for further identifying item groups. Can be used on certain reports or custom reports. (maximum 10 characters, alphanumeric)
+
'''CostAdj''' - Enter the dollar value for the cost adjustment, or if no cost adjustment, enter 0
  
'''f38 - StdCost''' - Item’s standard cost per pricing unit
+
'''Spacer1-Spacer10''' - The spacer fields are placeholder entries for future expansion. They should not be used.
  
'''f39 - Coil''' - Y if the item is a coil. Coil items will automatically be assigned the Coil Receipts Default attribute. All coil items should also have the LotFlag column set to Y.  
+
'''Ans1-Ans43''' - List item descriptive name (max 100 characters) for LIST type questions. 43 list item entries are available for each question. List items display in the order according to the sequence identifier (1-43) on the import.
  
'''f40 - SingleIssue''' - Y if the item is the SingleIssue Item box should be checked in the Catch Weight attribute screen. This is only saved for catch-weight items (CW column set to Y).
+
'''AnsPA1-AnsPA43''' - Price adjustment dollar value for the associated list item.
  
'''f41 - CW''' - Y if the item is a catch-weight item. Catch-weight items will automatically be assigned the Catch Weight attribute.  
+
'''AnsCA1-AnsCA43''' - Cost adjustment dollar value for the associated list item.
  
'''f42 - OldItem''' - This field is no longer used
+
'''AnsOPA1-AnsOPA43''' - Other adjustment dollar value for the associated list item.
  
'''f43 - CWSPriceConv''' - Catch-Weight conversion factor between stock unit and pricing unit. (numeric, up to 5 digits)
+
'''Item1-Item43''' - Additional item number for special or contract pricing for the associated list item.  
  
'''f44 - CWSTKConv''' -  Catch-Weight conversion factor between catch unit and stock unit. (numeric, up to 5 digits)
 
  
'''f45 - CWSellConv''' -  Catch-Weight conversion factor between stock unit and selling unit. (numeric, up to 5 digits)
 
  
'''f46 - CWPurCon''' - Catch-Weight conversion factor between stock unit and purchase unit. (numeric, up to 5 digits)
+
==Configurable Item (SOC) Import Reconciliation==
 
 
'''f47 - CWUnit''' -  Catch-Weight Unit
 
 
 
'''f48 - PackQty''' -  Quantity to pack. (numeric, up to 5 digits)
 
 
 
'''f49 - AllOrder''' - Enter Y to set the Allocate at Order flag in Item Master
 
 
 
'''f50 - EDICode''' - Item's EDI code (alphanumeric, up to 10 digits, rare)
 
 
 
'''f51 - UPCCode''' -  Item's UPC code (alphanumeric, up to 12 characters)
 
 
 
 
 
 
 
==Item Master 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.
 
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 Item Master Report and verify that the imported records all display with the key values filled in. You can also verify that the number of records imported matched the number of records reported. If there are fewer items reported, looks for items that did not get imported and reconcile.
+
Run the SOC Export with filters to match the data just imported, and compare to the SOC Import file used. Verify that the number or records exported matches the number of records that should have been created/updated. Compare the export and import details for any any discrepancies.  
 
 
Try to sell various items on a sales order to verify that the correct flags and defaults are working as expected.
 
 
 
Try to order various items on a purchase order to verify that costs and units work as expected.  
 
  
 +
Try to sell various configurable items on a sales order to verify that the configurations and pricing are working as expected.
  
  
==Item Master Import Additional Steps==
 
  
Complete the required additional imports based on how the item will be used. For example:
+
==Configurable Item (SOC) Import Additional Steps==
  
*Item Quantity (O/H) Data
+
There are no additional steps required for the SOC Import.
*SOC Data
 
*Profile Data
 
*Min/Max Data
 
*Coil Quantity Data
 
*and many more
 
  
  
  
==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.
+
'''SOCQUESTION''' - Each imported question will create a KEYNO in this table. The KEYNOH value ties to the KEYNO value of the SOCITEM table which creates the link to the item number. This table holds most of the question details, length control options, and price/cost adjustment values. The SOC Export file Keyno value refers to the Keyno value from this table. Repeated imports for the same item number will generate new SOCQUESTION KEYNO values and delete the previous SOCQUESTION KEYNO.  
  
'''ITEMDET''' - Item OHF details are created in the ITEMDET table. Each OHF combination has a unique KEYNO based on the associated IKEY (from ITEMMASTER) and the combination of Warehouse (LOCTID), Owner (VENDID), and HELDFOR.
+
'''SOCITEM''' - The KEYNO value in this table links to the KEYNOH value in the SOCQUESTION table. This table holds the IKEY and ITEM values.
  
'''PCXREF''' - Attributes added to item records will create cross-reference entries in the PCXREF table. The TYPE will generally be the attribute name or code. The PARENTID and CHILDID will generally match the IKEY value of the associated item.
+
'''SOCANSWER''' - Each imported question will create a KEYNO in this table. The KEYNOH value ties to the KEYNO value of the SOCQUESTION table for the associated question number. This table holds the list item details. Repeated imports for the same item number will generate new SOCANSWER KEYNO values, but will NOT delete the previous values. The previous values will remain in the table, but will no longer be linked to valid SOCQUESTIONs.
  
'''ATTRIBUTE TABLES''' - Attributes such as Catch Weight and Coil Receipt Defaults create their own data tables with details from the attribute jump screens. For any attribute jump screens created that contain data, you should find a separate data table, such as CWINFO (for Catch Weight) or COILJUMP (for Coil Receipt Defaults). The associated FORM (jump screen) name from the ITEMATTRIB rule is generally the same name as the data table. These tables will usually link to the item using the IKEY value.
+
'''PCXREF''' - The Configurable Item (SOC) attribute added to item records will create a cross-reference entry in the PCXREF table. The TYPE will be 'SOC'. The PARENTID and CHILDID will match the IKEY value of the associated item.
  
  
 
[[Category: Item Control]]
 
[[Category: Item Control]]
 
[[Category: Import Guides]]
 
[[Category: Import Guides]]

Latest revision as of 15:08, 31 March 2023

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.


Configurable Item (SOC) Import Notes

Timing and Preparation

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.


General Notes

The import template file for the SOC Import is generated by using the Export Configurable (SOC) Items screen, detailed below. The Export Configurable Items (SOC) can be requested from any system with configurable items. The export screen has multiple filters to help with selecting the right records for building an import file. The data can also be filled in manually, but it is much easier to use existing SOC records as a reference when creating a new import file.

If you intend to use most of the field data from an SOC Export file, review the data critically before attempting to associate it with a customer's item file. We do not want to propogate bad data.

The safest practice is to pick an accurate example of each question type and copy the single, reviewed question down to all new customer items. This way, the same data is used for all questions.

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 also create the Configurable Item (SOC) attribute for the associated item, if it doesn't already exist.


Configurable Item (SOC) 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.

The SOC import file is generally built 'from scratch' or by exporting a known good list of SOC items and editing it heavily to match the customer's data. Because there is typically no single source data file from the customer, creating the SOC import file will typically involve pulling bits of data from one or more customer files to create the import. Below are some of the key data columns to review carefully prior to import:

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.

Item: When copying data into the file, review the item number fields carefully. Carefully review any items that are being renumbered in Adjutant and make sure the item numbers are correct. Review for any transposed numbers or faulty copy and paste issues.

QuestNo: Re-sort the import file by item and look for any question numbering gaps or duplicates.

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.

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) Import Screen (SOCIMPORT)

Menu Location Transaction>>Import/Export>>Import Master>>Configurable Item Import

URL ImportMaster_S.htm?mode=SOCIMPORT

Item File Name/Browse: Use the Browse button to locate and select the completed SOC import template file (in XLS format).


Socimport.png

Configurable Item (SOC) Export Screen (SOCEXPORT)

Menu Location Transaction>>Import/Export>>Import Master>>Configurable Item (SOC) Import >>> Export Tab

URL ImportMaster_S.htm?mode=SOCIMPORT


SOCEXPORT.png

Class: Enter a single item class value or a range to filter the SOC Export results by Item Master class.

Item Range: Enter an item code range to filter the SOC Export results by all item numbers that fall between the from and to values.

Item Like Block: Enter up to 6 item-like searches to filter the SOC Export results by custom item number searches.

Commodity Code: Enter a single commodity code or a range to filter the SOC Export results by Item Master commodity code.

Held For: Enter a Held For name to filter the SOC Export by Held For.

Owner: Enter an Owner name to filter the SOC Export by Owner.


Configurable Item (SOC) Import File Definitions

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

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 - Enter 'Y' to check the Price/Cost Adjust box in the Price and/or Other Adjustment Settings area

PriceAdj - Enter the dollar value for the price adjustment, or if no price adjustment, enter 0

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 - Enter 'Y' to check the Controlling Qty box

ShowAdj - Enter 'Y' to check the Display Price Adjustment box

OtherAdj - Enter the dollar value for the Other Adjustment field, or if not other adjustment, enter 0.

QNum4 - Other Adjustment question number. Enter the SOC question number to fill in the 'To Q#' value.

QNum2 - Pass 1 question number. Enter the SOC question number to fill in the Pass 1 'Multiply Q#' value.

QNum3 - Pass 2 question number. Enter the SOC question number to fill in the Pass 2 'Adjustment by Q#' value.

CostAdj - Enter the dollar value for the cost adjustment, or if no cost adjustment, enter 0

Spacer1-Spacer10 - The spacer fields are placeholder entries for future expansion. They should not be used.

Ans1-Ans43 - List item descriptive name (max 100 characters) for LIST type questions. 43 list item entries are available for each question. List items display in the order according to the sequence identifier (1-43) on the import.

AnsPA1-AnsPA43 - Price adjustment dollar value for the associated list item.

AnsCA1-AnsCA43 - Cost adjustment dollar value for the associated list item.

AnsOPA1-AnsOPA43 - Other adjustment dollar value for the associated list item.

Item1-Item43 - Additional item number for special or contract pricing for the associated list item.


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.

Run the SOC Export with filters to match the data just imported, and compare to the SOC Import file used. Verify that the number or records exported matches the number of records that should have been created/updated. Compare the export and import details for any any discrepancies.

Try to sell various configurable items on a sales order to verify that the configurations and pricing are working as expected.


Configurable Item (SOC) Import Additional Steps

There are no additional steps required for the SOC Import.


Configurable Item (SOC) Import Database Tables

SOCQUESTION - Each imported question will create a KEYNO in this table. The KEYNOH value ties to the KEYNO value of the SOCITEM table which creates the link to the item number. This table holds most of the question details, length control options, and price/cost adjustment values. The SOC Export file Keyno value refers to the Keyno value from this table. Repeated imports for the same item number will generate new SOCQUESTION KEYNO values and delete the previous SOCQUESTION KEYNO.

SOCITEM - The KEYNO value in this table links to the KEYNOH value in the SOCQUESTION table. This table holds the IKEY and ITEM values.

SOCANSWER - Each imported question will create a KEYNO in this table. The KEYNOH value ties to the KEYNO value of the SOCQUESTION table for the associated question number. This table holds the list item details. Repeated imports for the same item number will generate new SOCANSWER KEYNO values, but will NOT delete the previous values. The previous values will remain in the table, but will no longer be linked to valid SOCQUESTIONs.

PCXREF - The Configurable Item (SOC) attribute added to item records will create a cross-reference entry in the PCXREF table. The TYPE will be 'SOC'. The PARENTID and CHILDID will match the IKEY value of the associated item.