SKUs!? - D-Tools Forum

09-26-2007, 10:14 PM

Does any one use these? I can't find any documentation on them and the training sessions at MED don't go into detail at all (as a matter of fact, they just "skip right over these fields")...

Are the SKUs your INTERNAL skus? Should they match QuickBooks? Are they imported from QuickBooks? OR are they the MANUFACTURER's SKUs/Part Number?

The reason I ask is that a company like Extron has both Part Numbers (SKUs) and Model Names... Which is more appropriate to use in the Model field and which is more appropriate in the SKU?

If I populate the Model field with Extron part numbers, then the product explorer is populated with tons of uninteligible part numbers (I can still use keywords, so that helps)... I'd rather have SKU be the manufacturer SKU (or part number), but could that use of the SKU cause problems with QuickBooks and future use of Quicklinks (especially if our company's INTERNAL SKUs are not the same as the manufacturer's?

Any ideas? How are folks using the SKU and Model fields?

Thanks!

09-27-2007, 01:10 PM

Originally Posted by gnichols

I can't find any documentation on them...

OK, after a little more scrounging around, I've found the docs for SI5... On page 346 of the User Guide, it says, "SKU: This field is optional and can be used for a Manufacturer's part number or your own internal numbering system for identifying parts."

Then on page 350, regarding Item Number on the Pricing tab, "This field holds the Item Number of the corresponding Product from your accounting database. The value is generated by the LinkTools interface."

So I guess that answers both of my questions... Now on to lobby for some changes...

./g

09-27-2007, 03:28 PM

If you want to use the SKU field and have it show up when info is transferred to your QB, you can use the 'Map' function in QuickLinks to assign a QB custom property to any D-Tools Matching field, such as SKU.

Not sure if that will decrease your need for lobbying or not, but thought I would throw it out there.

**Kevin Mikelonis** · 09-27-2007, 03:30 PM

Good example with extron!

Use the model field for the model, and use the SKU field for that long SKU number that determines the configuration of that model.

In general, very few items in databases we have worked with need SKU

Bob Pothier · 10-10-2007, 08:56 PM

Originally Posted by gnichols

Then on page 350, regarding Item Number on the Pricing tab, "This field holds the Item Number of the corresponding Product from your accounting database. The value is generated by the LinkTools interface."
./g

***PLEASE NOTE***

SKU and Item Number are NOT the same thing. If you look at your item in MMPD you will see there is a SKU line towards the top and the Item Number is below (when on the Price tab) along with the Vendor Name (who you purchase this item from). Some for some people that were confused please know that SKU can be what you want it to be, but the Item Number is there for QB (primarily anyway). In the case of Extron I agree... you almost have to do the SKU as the model number because their "model numbers" are more like descriptions.