User Tools

Site Tools


rpsc_matrix_load

This is an old revision of the document!


RPSC Matrix Data Load Procedures

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 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.
  • 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.
  • The import of data to live system five needs to be complete
  • If the customer loads SKU to the System Five part number field (Option when exporting inventory from RPSC), there are additional steps. This scenario describes those steps because it is the common scenario, and it enables the client to use human readable part numbers instead of the numeric part number from RPSC padded to 6 digits.
  • You will need a copy of the Inventory.mdb database file from the RPSC data directory (in the …\Store1\ directory)
  • You will need a copy of the Invent5.btr database file from the Windard System Five data directory (in the …\data\ directory)
  • You will need Microsoft Access 2000 or higher installed on the machine you are doing the conversion on. (This machine should be on our side not the customers side). It is faster to download and work on the files here at the moment. If we were to get a one button macro running other options might be available that allow us to download an access database to the customers system.

Overview / Goals

The goal is to

  1. Do a normal import of parts from RPSC
  2. Add a new field for padded part numbers to match the unique part numbers used for the child parts
  3. Create kit part and matrix child import files from the RPSC database inventory.mdb
  4. Update these matrix import files to use the new part numbering implimented in step 2 above.
  5. Import the matrix files to System Five: This will add the matrix parents, update the Size fields on the child matrix parts, and attatch the child matrix items to their parents.

Queries to Run

  1. Ordered List Item

Fix Numbering in System Five to allow for uniquely identifying the child parts

  1. Add or import module to give the ability to pad strings
  2. Use the query: qry-Step01-A, getting newsku for IMInventory to see these part numbers in a query
  3. Use the query: qry-Step02-A, Matrix Parents to get the Matrix Parent part listing. We are looking at the SKU because the Matrix Parents don't have part numbers in the other system. Since all child parts of the Matrix Parents have the same SKU we use the SKU from the children.
  4. Use the query: qry-Step03-A, Matrix Children to get the Matrix Children part listing including what the new updated SKU will look like. This query does not give out accurate SKU's because the Left VBA function does not seem to work in access which prevents us from properly formatting SKU's over 13 characters in length. Note: The length of a SKU in RPSC could be up to 15 characters.

Pitfalls and things to watch

  • On virtually all imports 2 passes need to be made, when the second pass is made any editing of or creation of System Five inventory items will be lost and the new information will replace this.
  • Due to setup and fixes that need to be made after import some clients elect to only do 1 pass. This works as long as parts the inventory between the system is not changing. We can then update the quantities at go live time to get things in order. Any new items that have been added since the initial import would have to be manually entered after the fact.
rpsc_matrix_load.1183593118.txt.gz · Last modified: 2007/07/04 16:51 (17 years ago) by cliff