Difference between revisions of "Inventory Quantity Import Guide"

From Adjutant Wiki

(Created page with " ==General Import Template File Notes== *Template files are typically generated from their respective Import screen using an 'Export Template' button. *Using the 'Export Temp...")
 
Line 21: Line 21:
 
===Timing and Preparation===
 
===Timing and Preparation===
  
The Coil Import is a quantity import, and should occur after all of the coil item records have been imported. An early Coil Import should be completed for parallel testing to create available coil inventory to test production of several types of produced coil material. Testing the coil import early can help find any data issues that show up during the production, inventory reporting, and inventory valuation testing procedures. The Item Control rules should be complete prior to importing item master records. The [[Item Control Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing item master records.   
+
The Inventory Quantity import should occur after all of the item records have been imported. Quantity imports should be completed for parallel testing to create available inventory to test orders and production. The Item Control rules should be complete prior to importing item master records. The [[Item Control Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing item master records.   
  
Coil import files should be separated into multiple imports based on the combination of Owner/HeldFor/Warehouse (OFH). The import template does not have data columns for OHF data, so if coils need to be imported to specific OHF combinations, the data will need to be separated into multiple files and the OHF values must be specified at the time of import. If all coils should be stocked under the same OHF details, you can still separate the coil files by item type, department, category, or any number of item grouping details if it makes formatting or reconciling inventory values easier. However, it is not required.
+
The Inventory Quantity Import will need to be run again at go-live to import the final available inventory as of the go-live date. A 'difference conversion' or 'catch-up conversion' is generally not worth it after quantities have been used in testing, and after purchase order receipts have been completed during testing. The best practice is to delete all of the inventory on hand data, and re-import with the current, final on hand quantities at go-live.
 
 
The Coil Import will need to be run again at go-live to import the final available coil inventory as of the go-live date. A 'difference conversion' or 'catch-up conversion' is generally not worth it after coil quantities have been used in testing, and after purchase order coil receipts have been completed during testing. The best practice is to delete all of the coil inventory and re-import with the current, final on hand coil quantities at go-live.
 
 
 
Coil Items should all have the following settings (at a minimum) in Item Master:
 
*Stock Item flag
 
*Lot# Control flag
 
*Unit Weight (per Stock Unit, not required, but it helps with verification)
 
*Coil Receipt Defaults attribute (also known as COIL LOT or COILJUMP)
 
*Purchase Units and Stock Units should be completed for all items with the correct units
 
 
 
The import can automatically generate lot numbers for coils if the coil number (lot#) column is blank. Review the settings for the LOTNO counter in the 'Counters' tab of CID Maintenance prior to importing and verify that the numbering settings are correct.  
 
  
  
Line 40: Line 29:
 
===General Notes===
 
===General Notes===
  
Do not use the Coil Import for items with the Coil-Like Item (COIL LIKE) item attribute. The Coil Import is specifically designed for importing coil items with the cost expressed as cost per 100 lbs of material, and items with the COIL LIKE attribute may import with unexpected costs. Use the Inventory Qty Import for non-coil items.
+
While the Inventory Quantity import can be used for lot controlled items, it should not be used for coil items. Follow the [Coil Import Guide] for detailed information on how to import coil items.
 
 
The Coil Import will add Item Master records for any item code on the import that doesn't already exist in Adjutant. The system-added Item Master records will be incomplete, and should be reviewed and updated to make sure the item settings are correct.
 
 
 
Review the '''COILPROCESSLIST''' CID Setup Option setting. With this turned on, the imported Processor Name value must exactly match the company name of an organization set up with the PROCESSOR Organization attribute. If this option is off, any valid text wil import as the coil processor.
 
 
 
Review the '''POCOILLBS''' CID Setup Option setting. With this turned on, the coil import assumes coil is stocked in LBS and the catch-weight calculation uses FT. This can affect the cost calculations. Best practices for coil inventory are to stock in FT, so for the majority of customers, this option should be turned off.
 
 
 
'''Coil Cost (Stocked in FT):''' The coil cost (column f5 in the template) should be entered and imported as cost per hundred LBS (catch-weight). The import process will convert and import the cost correctly as long as the cost is expressed in catch-weight, and the linear feet and actual weight columns are correct.
 
*If the customer data includes cost per LB, simply multiply that number by 100 to use as the cost.
 
*If the customer data includes cost per FT, multiply the cost/FT times the Linear Feet to get a total cost for the coil. Divide the calculated total cost by the Actual Weight value to get a cost/LB. Multiply the cost/LB times 100 to get the catch-weight cost.
 
*If the customer data only includes a total cost for the coil, divide the total cost by the Actual Weight to get a cost/LB. Multiple the cost/LB to get the catch-weight cost. See other considerations below.
 
  
'''Coil Cost (Stocked in LBS):''' Verify the the '''POCOILLBS''' setup option is turned on if the customer is stocking in LBS. The coil cost (column f5 in the template) should be entered and imported as cost per hundred LBS (catch-weight), which is the same procedure to use as when stocking in FT. With the setup option turned on, the import process will convert and import the cost correctly as long as the cost is expressed in catch-weight, and the linear feet and actual weight columns are correct.
+
'''IMPORTANT!!''' - Perform the Cost Tiers Import for all imported quantities to establish the historical receipt cost tier. The purchase order receipt process automatically builds cost tier data, but the quantity import process does not create cost tier data. Failing to import cost tiers for the imported quantities can have adverse effects down the road during procurement and production processes. Follow the [[Cost Tiers Import Guide]] for details on importing cost tiers.  
 
 
'''Coil Cost (other considerations):''' If the source data does not include a fixed cost per unit (either LBS or FT), and only includes a total cost per coil, be very careful that the cost does not include used material. For example, if you import a coil with an original total cost of $5000, but that coil has been partially used prior to import, you would get an inflated cost per unit if you only used the remaining quantity to calculate cost/LB. If 10,000 LBS of coil originally cost $5,000, that is .50/LB. However, if you are only importing the remaining 2,500 LBS of that coil and used the total cost of $5000, you would import a cost of $2/LB. If you are using an original cost total, you need to obtain an original quantity total to calculate the correct cost per unit.
 
  
  
Line 63: Line 39:
 
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:
 
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:
  
* '''Date Received''' - Every imported coil should have a date received value. The import process will not auto-fill the date received if the column is left empty. If an original date received cannot be provided, work with the customer to decide on a date value to use for all empty records.  
+
* '''Average Cost''' - The average cost for each imported quantity should be entered as the average cost per stocking unit. Verify that the source data has the correct cost per unit that matches the item's stock unit settings in Item Master. The imported average cost will be factored into the average cost calculations. Do not leave the average cost field empty.
  
* '''Cost''' - Verify that the cost per 100 LBS is entered for each item. See General Notes area above for cost calculations. Cost can be an extremely difficult item to correct once the item has been used in live transactions. Double-check the cost values carefully.
+
* '''Quantity''' - Verify that the quantities imported are entered in each item's stocking unit. If there are any customized stock units such as BAG250 or BOX1000, review the Item Master stock unit to confirm that the imported quantity relates to the item's stock unit.
 
 
* '''Coil Number''' - This converts to LOT#. Work with the customer to confirm whether they want to continue using the same lot numbers, manually assign new ones, or let the system auto-assign lot numbers based on the system counters.  
 
  
  
Line 108: Line 82:
 
Required fields are indicated with an *  
 
Required fields are indicated with an *  
  
'''f1 - Lot''' -  
+
'''f1 - Lot''' - Lot number for lot controlled inventory. Do not use the Inventory Quantity import for coil items. Follow the [Coil Import Guide] for details on importing coil quantities.
  
'''f2 - PrintLabel''' -   
+
'''f2 - PrintLabel''' -  Enter a 'Y' to indicate that a label should be printed
  
'''f3 - LabelNo''' -   
+
'''f3 - LabelNo''' -  Enter the number of labels that should be printed
  
'''f4 - OwnerID''' -   
+
'''f4 - OwnerID''' -  Inventory Owner organization ID. If left blank, the import request screen can fill in the Owner for ALL imported records.
  
'''f5 - HeldFor''' -   
+
'''f5 - HeldFor''' -  Inventory Holder organization ID. If left blank, the import request screen can fill in the Held For for ALL imported records.
  
'''f6 - Serial''' -   
+
'''f6 - Serial''' -  Serial ID for serialized inventory items
  
'''*f7 - AvgCost''' -   
+
'''*f7 - AvgCost''' -  Average cost per stocking unit, as of the transaction date for the associated quantity
  
'''*f8 - Qty''' -   
+
'''*f8 - Qty''' -  On Hand quantity (in stocking unit) for the associated item
  
'''f9 - Whse''' -   
+
'''f9 - Whse''' -  Inventory Warehouse location name. If left blank, the import request screen can fill in the Warehouse For for ALL imported records.
  
'''*f10 - Item''' -   
+
'''*f10 - Item''' -  Item number
  
'''f11 - Bin''' -   
+
'''f11 - Bin''' -  Item bin location. If the Bin does not exist in the Bin Control screen, the import program will add the needed Bin record.
  
  
Line 134: Line 108:
 
==Inventory Quantity Import Additional Steps==
 
==Inventory Quantity Import Additional Steps==
  
'''IMPORTANT!!''' - Perform the Cost Tiers Import for every imported lot record to establish the historical receipt cost tier. The purchase order receipt process automatically builds cost tier data, but the coil import process does not create cost tier data. Failing to import cost tiers for the imported coils can have adverse effects down the road during procurement and production processes. Follow the [[Cost Tiers Import Guide]] for details on importing cost tiers.  
+
'''IMPORTANT!!''' - Perform the Cost Tiers Import for all imported quantities to establish the historical receipt cost tier. The purchase order receipt process automatically builds cost tier data, but the quantity import process does not create cost tier data. Failing to import cost tiers for the imported quantities can have adverse effects down the road during procurement and production processes. Follow the [[Cost Tiers Import Guide]] for details on importing cost tiers.
 
 
Perform the Coil Receipt Defaults (COILJUMP) import to set the default coil receipt tag values for each coil item. Follow the [[Coil Receipt Defaults Import Guide]] for details.
 
 
 
Run the Update Item OH/AL/OO (ITEMUPDATE) report after all coil lots have been imported. This will update the Item Master on hand displays and item search results with the imported values.
 
  
Print coil tags for all imported coils.
+
Run the Update Item OH/AL/OO (ITEMUPDATE) report after all quantities have been imported. This will update the Item Master on hand displays and item search results with the imported values.
*During parallel testing, it is okay to only print coil tags for selected items that will be used for testing. All coil item types should be tested (i.e. coil for panels, coil for cees, etc.)
 
 
 
*For go-live, all imported coil records must have coil  tags printed.
 
  
  
Line 151: Line 118:
 
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 Inventory On Hand Report filtered for the imported records and verify that the imported records all display as expected. Review the lots, cost entries, and on hand value for all imported lot records.  
+
Run the Inventory On Hand Report filtered for the imported records and verify that the imported records all display as expected. Review the lots, cost entries, and on hand value for all imported records.  
  
Perform several searches in the Coil Finder screen to make sure that imported coils show up as expected. Review the coil tags and make sure they print as expected.
+
Compare the Adjutant cost and on hand inventory value for several records against the source data. Verify that imported inventory value matches the source data value. If there are any discrepancies, review, adjust, and try to correct with an updated import. If the differences can't be corrected with a new import, document the reasons for the differences and discuss with customer.
 
 
Compare the Adjutant cost and on hand inventory value for several records against the source data. Verify that imported coil inventory value matches the source data value. If there are any discrepancies, review, adjust, and try to correct with an updated import. If the differences can't be corrected with a new import, document the reasons for the differences and discuss with customer.
 
 
 
Complete different types of production with the imported coils and verify that lot records are available for production assignments. Verify that cost accounting for production usage is accurate.  
 
  
  
Line 163: Line 126:
 
==Inventory Quantity Import Database Tables==
 
==Inventory Quantity Import Database Tables==
  
'''COILRECEIPT''' - Each imported lot creates a KEYNO in this table, linked to the imported LOT and tied to the item's IKEY.
+
'''ITEMTRACK''' - Each imported quantity creates a TRACKNO in this table, linked to the imported item's IKEY and Location (Bin).
 
 
'''ITEMTRACK''' - Each imported lot creates a TRACKNO in this table, linked to the imported LOT and tied to the item's IKEY.  
 
  
'''ITEMMASTER''' - Any coil item that doesn't already exist will create a unique IKEY tied to the ITEM value.  
+
'''ITEMTRAN''' - Each item quantity will create a unique KEYNO with a Note of 'QTYIMP' tied to the item's IKEY value. The ITEM9 field shows the actual item number for the IKEY.
  
'''ITEMMDET''' - Any coil item that doesn't already exist will also create a unique ITEMDET record for the OHF combination specified on the import screen.
+
'''ITEMMACT''' - Each imported quantity will create a unique KEYNO with a TYPE of 'IA' (Inventory Adjustment) tied to the item's IKEY (and Lot, if lot controlled).
  
  

Revision as of 15:42, 5 December 2018

General Import Template File Notes

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


Inventory Quantity Import Notes

Timing and Preparation

The Inventory Quantity import should occur after all of the item records have been imported. Quantity imports should be completed for parallel testing to create available inventory to test orders and production. The Item Control rules should be complete prior to importing item master records. The Item Control Setup Guide covers all of the Rule Maintenance records that should be completed prior to importing item master records.

The Inventory Quantity Import will need to be run again at go-live to import the final available inventory as of the go-live date. A 'difference conversion' or 'catch-up conversion' is generally not worth it after quantities have been used in testing, and after purchase order receipts have been completed during testing. The best practice is to delete all of the inventory on hand data, and re-import with the current, final on hand quantities at go-live.


General Notes

While the Inventory Quantity import can be used for lot controlled items, it should not be used for coil items. Follow the [Coil Import Guide] for detailed information on how to import coil items.

IMPORTANT!! - Perform the Cost Tiers Import for all imported quantities to establish the historical receipt cost tier. The purchase order receipt process automatically builds cost tier data, but the quantity import process does not create cost tier data. Failing to import cost tiers for the imported quantities can have adverse effects down the road during procurement and production processes. Follow the Cost Tiers Import Guide for details on importing cost tiers.


Inventory Quantity 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:

  • Average Cost - The average cost for each imported quantity should be entered as the average cost per stocking unit. Verify that the source data has the correct cost per unit that matches the item's stock unit settings in Item Master. The imported average cost will be factored into the average cost calculations. Do not leave the average cost field empty.
  • Quantity - Verify that the quantities imported are entered in each item's stocking unit. If there are any customized stock units such as BAG250 or BOX1000, review the Item Master stock unit to confirm that the imported quantity relates to the item's stock unit.


Inventory Quantity Import Screen (ITEMQTYIMP)

Menu Location: Transaction>>Importers/Exporters>>Item Control>>Inventory Qty Import

ITEMQTYIMP.png


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

Export Template: Generates a blank Inventory Quantity 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.

Default Owner: Sets the inventory owner for all imported quantity records. This list is populated with Organization records that have the Inventory Owner attribute.

Default Warehouse: Sets the warehouse location for all imported quantity records. This list is populated by Warehouse Control records that have been created.

Default HeldFor: Sets the inventory holder for all imported quantity records. 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.

Transaction Date: Sets the transaction date for the QTYIMP transaction.

Validate to TXT File: Selecting this box will create a TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered.

Add to OnHand: The default option is to add the imported quantities to any existing on hand quantity.

Replace OnHand: Select the replace option if the quantity values in the import file represent the total on hand quantity for each item and they should replace the current on hand quantity.

Skip OHF Counter Update:

Skip Asset Check:


Inventory Quantity Import File Definitions

Required fields are indicated with an *

f1 - Lot - Lot number for lot controlled inventory. Do not use the Inventory Quantity import for coil items. Follow the [Coil Import Guide] for details on importing coil quantities.

f2 - PrintLabel - Enter a 'Y' to indicate that a label should be printed

f3 - LabelNo - Enter the number of labels that should be printed

f4 - OwnerID - Inventory Owner organization ID. If left blank, the import request screen can fill in the Owner for ALL imported records.

f5 - HeldFor - Inventory Holder organization ID. If left blank, the import request screen can fill in the Held For for ALL imported records.

f6 - Serial - Serial ID for serialized inventory items

*f7 - AvgCost - Average cost per stocking unit, as of the transaction date for the associated quantity

*f8 - Qty - On Hand quantity (in stocking unit) for the associated item

f9 - Whse - Inventory Warehouse location name. If left blank, the import request screen can fill in the Warehouse For for ALL imported records.

*f10 - Item - Item number

f11 - Bin - Item bin location. If the Bin does not exist in the Bin Control screen, the import program will add the needed Bin record.


Inventory Quantity Import Additional Steps

IMPORTANT!! - Perform the Cost Tiers Import for all imported quantities to establish the historical receipt cost tier. The purchase order receipt process automatically builds cost tier data, but the quantity import process does not create cost tier data. Failing to import cost tiers for the imported quantities can have adverse effects down the road during procurement and production processes. Follow the Cost Tiers Import Guide for details on importing cost tiers.

Run the Update Item OH/AL/OO (ITEMUPDATE) report after all quantities have been imported. This will update the Item Master on hand displays and item search results with the imported values.


Inventory Quantity 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 Inventory On Hand Report filtered for the imported records and verify that the imported records all display as expected. Review the lots, cost entries, and on hand value for all imported records.

Compare the Adjutant cost and on hand inventory value for several records against the source data. Verify that imported inventory value matches the source data value. If there are any discrepancies, review, adjust, and try to correct with an updated import. If the differences can't be corrected with a new import, document the reasons for the differences and discuss with customer.


Inventory Quantity Import Database Tables

ITEMTRACK - Each imported quantity creates a TRACKNO in this table, linked to the imported item's IKEY and Location (Bin).

ITEMTRAN - Each item quantity will create a unique KEYNO with a Note of 'QTYIMP' tied to the item's IKEY value. The ITEM9 field shows the actual item number for the IKEY.

ITEMMACT - Each imported quantity will create a unique KEYNO with a TYPE of 'IA' (Inventory Adjustment) tied to the item's IKEY (and Lot, if lot controlled).