Differences

This shows you the differences between two versions of the page.

--- rpsc_matrix_load [2016/04/14 11:23 (8 years ago)] – [Overview / Goals] sjackson
+++ rpsc_matrix_load [2016/04/14 11:25 (8 years ago)] (current) – [Pitfalls and things to watch] sjackson
@@ Line 3: / Line 3: @@
 ===== What you need =====
-The overall goal is to import inventory from RPSC to System Five and then add matrix parents to SystemFive linking them to the matrix child parts.
+The overall goal is to import inventory from RPSC to System Five and then add matrix parents to System Five linking them to the matrix child parts.
-  * The first thing to be aware of is to export the Inventory from RPSC using PartNumbers, not SKU's in System Five. This is necessary for being able to data load matrix information without extra hastle.
+  * The first thing to be aware of is to export the Inventory from RPSC using PartNumbers, not SKU's in System Five. This is necessary for being able to data load matrix information without extra hassle.
-  * It is necessary to create a supplier and inventory export from RPSC. The Supplier import needs to be done so that the Inventory can be attatched properly to the supplier name.
+  * It is necessary to create a supplier and inventory export from RPSC. The Supplier import needs to be done so that the Inventory can be attached properly to the supplier name.
   * The import of data to live system five needs to be complete. See warning below.
   * **WARNING:** You must choose to make RPSC Part Numbers your part numbers when asked during the RPSC Export process or it will not be possible to import your matrix items.
@@ Line 56: / Line 56: @@
   - Import **qry-Step02-A, Matrix Parents.csv**, but make sure you save the results. We need to get the unique ID of the first Matrix Parent added for later use in a query to update Part Numbers
   - **WARNING:** I had a problem when first running this file because I ran it before the **qry-Step03-A, Matrix Children.csv** query. I was getting messages about the part already existing. I am trying to run things in this order to prevent this error. I have also Imported the new format sku into the item number field in System Five because I think this is the cause of the problem.
-  - **Caution:** We need to test PO's for matrix parent items working because I don't know if we will have a problem if the Supplier is not attatched to the matrix parent.
+  - **Caution:** We need to test PO's for matrix parent items working because I don't know if we will have a problem if the Supplier is not attached to the matrix parent.
-  - Import **qry-Step03-B, Matrix Children Kit Load** via a kit load which will attatch the child parts to the parent parts.
+  - Import **qry-Step03-B, Matrix Children Kit Load** via a kit load which will attach the child parts to the parent parts.
-  - Since the Item Number is now updated to the NewSKU format, it does not have any size inforamtion in it. Also we need to check about the clients searching methods to make sure things work for them. All of the updates for these can be done afterwards.
+  - Since the Item Number is now updated to the NewSKU format, it does not have any size information in it. Also we need to check about the clients searching methods to make sure things work for them. All of the updates for these can be done afterwards.
   - Behavior: The system will not pull up matrix children when you search for the main parent part. ex: VOLCSHIMCRANE01 will only bring up the parent part in the search window at this time.
   - A query will need to be ran to update all Parts with a unique less than the first Parent Matrix Part Number<code>update Inventry set Part = Item where InvUnique < 10</code> Just make sure you replace 10 with the unique number of the first Parent Matrix Part Number you loaded. Remember there are lots of parts that were not matrix parts that still have only a part number as the primary search method.
@@ Line 93: / Line 93: @@
 === Check to see if only the correct stock is being imported ===
-We use a couple queries to produce a count of items in stock, and compare this with the items that are not in stock (qty = 0). This is a good indicator to bring your attention to missed steps or improper information being added to system five. As a rule of thumb if the percentage items stocked is less than or equal to 50% of the total number of inventory being imported the data has not been cleaned. It may contain items that should be in the auxilliary database, or items that are no longer used and need to be removed. Here is a way to quickly check this figure:
+We use a couple queries to produce a count of items in stock, and compare this with the items that are not in stock (qty = 0). This is a good indicator to bring your attention to missed steps or improper information being added to system five. As a rule of thumb if the percentage items stocked is less than or equal to 50% of the total number of inventory being imported the data has not been cleaned. It may contain items that should be in the auxiliary database, or items that are no longer used and need to be removed. Here is a way to quickly check this figure:
   * Run the query **qryInfo-Percentage of inventory items in stock**
   * Use this formula to calculate the percentage of inventory items in stock: Stocked Items / Total Number of Items * 100
@@ Line 107: / Line 107: @@
 == What is the Virtual Warehouse used for? ==
-The Virtual Warehouse (Formerly known as the Auxilliary database) is used as a price list made up of price lists from each of your suppliers. It is important to understand what the purpose of the Virtual Warehouse is so you can make sure parts that should be in the Virtual Warehouse are not placed into regular inventory. If a part is not normally stocked, and it is not a special order item and is not seasonal item then it should not be an inventory item. To rephrase: If a part is stocked, or is a special order item or is a seasonal item it should be an inventory item; if one of those is not true then it should be a Virtual Warehouse item/part.
+The Virtual Warehouse (Formerly known as the Auxiliary database) is used as a price list made up of price lists from each of your suppliers. It is important to understand what the purpose of the Virtual Warehouse is so you can make sure parts that should be in the Virtual Warehouse are not placed into regular inventory. If a part is not normally stocked, and it is not a special order item and is not seasonal item then it should not be an inventory item. To rephrase: If a part is stocked, or is a special order item or is a seasonal item it should be an inventory item; if one of those is not true then it should be a Virtual Warehouse item/part.