Cost Tiers Import Guide - Revision history

Amohammad at 15:23, 27 March 2024

2024-03-27T15:23:44Z

Amohammad at 15:19, 27 March 2024

2024-03-27T15:19:10Z

Freddy: /* Cost Tier Import File Definitions */

2019-05-20T16:34:32Z

‎Cost Tier Import File Definitions

Freddy at 19:26, 10 January 2019

2019-01-10T19:26:41Z

Freddy at 15:16, 13 December 2018

2018-12-13T15:16:17Z

Freddy at 17:00, 5 December 2018

2018-12-05T17:00:31Z

Freddy at 16:55, 5 December 2018

2018-12-05T16:55:59Z

Show changes

Freddy at 22:04, 3 December 2018

2018-12-03T22:04:41Z

Freddy at 22:03, 3 December 2018

2018-12-03T22:03:50Z

Freddy at 21:40, 3 December 2018

2018-12-03T21:40:22Z

@@ Line 58: / Line 58: @@
 Menu Location: Transaction >> Import/Export >> Item Control >> Cost Tier Import (dropdown menu)
-[[File:Cost_Tier_Import.jpg]]
+[[File:Cost_Tier_Import.png]]
 '''File Name/Browse:''' Use the Browse button to locate and select the completed Cost Tier import template file (in XLS format).

@@ Line 56: / Line 56: @@
 ==Cost Tier Import Screen (IMPORTCOSTTIER)==
-Menu Location: Transaction>>Importers/Exporters>>Item Control>>Cost Tier Import
+Menu Location: Transaction >> Import/Export >> Item Control >> Cost Tier Import (dropdown menu)
 '''File Name/Browse:''' Use the Browse button to locate and select the completed Cost Tier import template file (in XLS format).
@@ Line 69: / Line 68: @@
 '''Default Owner:''' Sets the inventory owner for any cost tier lines with a blank owner value. This list is populated with Organization records that have the Inventory Owner attribute.
-'''Default HedlFor:''' Sets the inventory holder for any cost tier lines with a blank heldfor value. 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.
+'''Default HedlFor:''' Sets the inventory holder for any cost tier lines with a blank held for value. 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.

@@ Line 93: / Line 93: @@
 '''f8 - SerialLot''' -  Serial or Lot# value for the associated cost tier item
-'''f9 - OCost''' -  Other cost associated with the cost tier (rare)
+'''f9 - OCost''' -  Other cost associated with the cost tier. This field is only used in rare situations and can have adverse effects on inventory costing. This field should be left blank unless specifically instructed by ABIS personnel.
 ==Cost Tier Import Reconciliation==

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

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

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

← Older revision		Revision as of 15:16, 13 December 2018
Line 72:		Line 72:


−	'''File Name~~(Header)~~/Browse:''' Use the Browse button to locate and select the completed Cost Tier import template file (in XLS format).	+	'''File Name/Browse:''' Use the Browse button to locate and select the completed Cost Tier import template file (in XLS format).

	'''Export Template:''' Generates a blank Cost Tier import template file		'''Export Template:''' Generates a blank Cost Tier import template file

@@ Line 53: / Line 53: @@
 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 Check/Correct Cost Tiers (MATCHCTALL) report can be used after a quantity import to generate most of the data needed to create a cost tier import file. After importing quantities, but before cost tiers have been created, this report will show each item or item/lot with an empty tier quantity. The data can be exported to an Excel spreadsheet, then copied and pasted into the cost tier import template. The date value will be missing and must be filled in appropriately for all lines. This report can also be used to create the cost tiers by using the 'Correct' button, however, it only builds the tier for the item's specified cost method, and it assumes the current date as the tier date, which is generally not accurate. Best practices are to use the import to create all cost tiers with the correct tier date based on material receipt date.
+The Check/Correct Cost Tiers (MATCHCTALL) report can be used after a quantity import to generate most of the data needed to create a cost tier import file. After importing quantities, but before cost tiers have been created, this report will show each item or item/lot with an empty tier quantity. The data can be exported to an Excel spreadsheet, then copied and pasted into the cost tier import template. The cost and date values will be missing and must be filled in appropriately for all lines. This report can also be used to create the cost tiers by using the 'Correct' button, however, it only builds the tier for the item's specified cost method, and it assumes the current date as the tier date, which is generally not accurate. Best practices are to use the import to create all cost tiers with the correct tier date based on material receipt date.
 The Cost tier import file is generally created either from data on quantity import files, or from queries into the database after quantity imports have been completed. It is not common during an implementation for customers to provide a file with cost tier data. However, if a customer supplies cost tier data, review the file to standardize the key data fields.

@@ Line 55: / Line 55: @@
 The Cost tier import file is generally created either from data on quantity import files, or from queries into the database after quantity imports have been completed. It is not common during an implementation for customers to provide a file with cost tier data. However, if a customer supplies cost tier data, review the file to standardize the key data fields.
-*Item - Review for item numbers that may have changed during implementation
+*'''Item''' - Review for item numbers that may have changed during implementation
-*Qty - Verify that all quantities are provided in the item's stocking unit
+*'''Qty''' - Verify that all quantities are provided in the item's stocking unit
-*Date - Verify that dates are correct and expressed in MM/DD/YYYY format
+*'''Date''' - Verify that dates are correct and expressed in MM/DD/YYYY format
-*Cost - Verify that the cost is expressed per the item's stocking unit
+*'''Cost''' - Verify that the cost is expressed per the item's stocking unit
-*Seriallot - If the lot numbers have changed, or have been auto-generated during import, update the lot numbers to reflect the actual lot numbers created in Adjutant
+*'''Seriallot''' - If the lot numbers have changed, or have been auto-generated during import, update the lot numbers to reflect the actual lot numbers created in Adjutant

@@ Line 38: / Line 38: @@
 ===General Notes===
 '''Date:''' The cost tier date represents the date that the material was received, and is critically important for determining the correct cost tier to use for LIFO and FIFO methods. The FIFO and LIFO methods rely on the received date and quantity received to track inventory usage cost according to FIFO and LIFO rules. Review the [http://www.abiscorp.com/AdjWiki/Inventory-Costing-Methods.ashx Inventory Costing Methods] Wiki page for more details on how cost tiers affect inventory value.
-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.
+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.
-==Coil Import File Data Scrubbing==
+*Item - Review for item numbers that may have changed during implementation

← Older revision		Revision as of 21:40, 3 December 2018
Line 39:		Line 39:
	===General Notes===		===General Notes===

−	'''Date:''' The cost tier date represents the date that the material was received, and is critically important for determining the correct cost tier to use for LIFO and FIFO methods. The FIFO and LIFO methods rely on the received date and quantity received to track inventory usage cost according to FIFO and LIFO rules. Review the [http://www.abiscorp.com/AdjWiki/Inventory-Costing-Methods.ashx\|Inventory Costing Methods] Wiki page for more details on how cost tiers affect inventory value.	+	'''Date:''' The cost tier date represents the date that the material was received, and is critically important for determining the correct cost tier to use for LIFO and FIFO methods. The FIFO and LIFO methods rely on the received date and quantity received to track inventory usage cost according to FIFO and LIFO rules. Review the [http://www.abiscorp.com/AdjWiki/Inventory-Costing-Methods.ashx Inventory Costing Methods] Wiki page for more details on how cost tiers affect inventory value.