ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Sales >> Base Prices
http://www.istechforum.com/YaBB.pl?num=1183478797

Message started by GasGiant on 07/03/07 at 09:06:36

Title: Base Prices
Post by GasGiant on 07/03/07 at 09:06:36

Is there an import program for base prices? We need to update several hundred and would like to "find a better way"

Title: Re: Base Prices
Post by David Waldmann on 07/03/07 at 09:26:55

DE-B

But you have to be tricky. I just updated about 10,000 items this way.

From our internal help site (basic plan from Lynn, slightly modified for our own use):

This can also be used to update any other elements of the existing data files.

Create a comma delimited file with the Item Number and base price (and/or anything else you want, but you always need Item Number)

Make a backup and get everybody out of DBA.

Make sure you have a good backup.

Rename the following files:
   BKICEMTR to BKICEMTR.EMPTY
   BKICELOC to BKICELOC.EMPTY
   MTICEMTR to MTICEMTR.EMPTY

Rename the following files:
   BKICMSTR to BKICEMTR
   BKICLOC to BKICELOC
   MTICMSTR to MTICEMTR

Run the DE Inventory Error report to confirm all copied properly

Import the file indicating Replace

Run the DE Inventory Error report to confirm you haven't introduced errors

Rename the following files:
   BKICEMTR to BKICMSTR
   BKICELOC to BKICLOC
   MTICEMTR to MTICMSTR

Rename the following files
   BKICEMTR.EMPTY to BKICEMTR
   BKICELOC.EMPTY to BKICELOC
   MTICEMTR.EMPTY to MTICEMTR

How this works.

The first set of files are the empty temporary data import file.

The second set of files are the live inventory files. By renaming them, it puts all your existing data into the data import location.

Importing the new data then modifies only the part that is changed.

And the third set makes the temporary data import files the live ones.

The .EMPTY files are temporary holding places for the import files (you could also restore originals, or copy them somewhere else - this is just the easiest way I've found). If you don't replace the import files when done, you will have a problem if you Copy that company to a new one.

Title: Re: Base Prices
Post by kkmfg on 07/03/07 at 11:15:00

I'm reminded of a guy named Rube Goldberg. Ever heard of him? ;-) That whole process seems unacceptably complicated for what the original poster wants to do.

Title: Re: Base Prices
Post by Lynn_Pantic on 07/03/07 at 11:19:29

While it may be (relatively) safe to import new base prices to the master tables, the procedure of importing to the temporary tables and run the error report is to ensure you haven't introduced errors by importing invalid field values if you are importing other things such as Class or Type.   I am sure we could develop a program to automate the process, automatically backing up the master files, importing the desired information directly to the master tables, running hte error report and restoring the backup files if errors were introduced but that would cost programming time and $$ and thus far, everybody needing to do it has been willing to use the free (and admittedly awkward) approach.

Title: Re: Base Prices
Post by David Waldmann on 07/03/07 at 11:51:14


kkmfg wrote:
That whole process seems unacceptably complicated for what the original poster wants to do.

"Unacceptably"? Compared to what? If you want to manually enter hundreds or thousands or prices, be my guest. I'll even provide drinks ;)

Once familiar with the procedure and you have the csv file done (which you're going to have to do regardless of the import method), it takes maybe 10-15 minutes.

Title: Re: Base Prices
Post by kkmfg on 07/03/07 at 13:46:25

Unacceptable in that I would not find it acceptable for a commercial program to think it's OK to make you manually copy files around in order to safely update the database. Transactions and triggers and such would prevent any need for such a thing. Or, all import functions could by default import to a temporary table first (or have the option) and then have a program that copies the temporary over to permanent. Or, take a page from Google. We use Google Base to upload our product catalog so that people can search it. It takes an XML file as input. If your input file has errors it tells you and you correct it. It does not try anyway and toast your data.

One may think that I'm a bit too anal about this but I find a lack of data integrity to be the worst of sins in this type of program. Either you can trust your ERP software or you can't. Maybe is not a comforting answer. If you can't trust the program to not trash your data on import without manually copying files behind the software's back then what good is it?

-Grumpy Gus



David Waldmann wrote:
[quote author=kkmfg link=1183478797/0#2 date=1183490100]That whole process seems unacceptably complicated for what the original poster wants to do.

"Unacceptably"? Compared to what? If you want to manually enter hundreds or thousands or prices, be my guest. I'll even provide drinks ;)

Once familiar with the procedure and you have the csv file done (which you're going to have to do regardless of the import method), it takes maybe 10-15 minutes.[/quote]

Title: Re: Base Prices
Post by David Waldmann on 07/03/07 at 14:07:36


kkmfg wrote:
Unacceptable in that I would not find it acceptable for a commercial program to think it's OK to make you manually copy files around in order to safely update the database.

The point is, that DBA/Evo does not "think" that it is OK. It's not an endorsed or documented method. It's a workaround the someone who knows how the program works (Lynn) figured out.

Happy 4th.

Title: Re: Base Prices
Post by kkmfg on 07/03/07 at 20:57:27

Yes, it's good that the workaround exists and that they've taken the time to explain it. But, it's still not acceptable to say, basically 'our program can toast your data but heres a way to fix it that involves logging everyone out and manually copying files around' At least, it'd be nice if the solution didn't involve a total shutdown of the system.

And my point is that without that work around the program could very well totally screw the pooch. That's not a nice state of affairs. It means that you have to be aware of a work around in order to actually have reasonable assurance that your data will be intact. Granted, shame on the company without current backups!

Happy 4th to you as well. Hopefully we all get back on Thursday with all 10 fingers! ;-)

Title: Re: Base Prices
Post by Lynn_Pantic on 07/05/07 at 07:08:53

Not entirely true.  Without the workaround, you won't toast your data.  You just can't import single elements of data such as pricing.

All 10 fingers intact...

Title: Re: Base Prices
Post by kkmfg on 07/05/07 at 07:18:23


Lynn_Pantic wrote:
Not entirely true.  Without the workaround, you won't toast your data.  You just can't import single elements of data such as pricing.

All 10 fingers intact...


Ahh... I see... I was judging my comments from when you said:


Quote:
While it may be (relatively) safe to import new base prices to the master tables, the procedure of importing to the temporary tables and run the error report is to ensure you haven't introduced errors by importing invalid field values if you are importing other things such as Class or Type."


Which makes it sound like you could easily toast your data if you don't use the work around.

Despite my best efforts I still have all 10 fingers too. ;-)

Title: Re: Base Prices
Post by GasGiant on 07/05/07 at 09:13:24

Well, since Base Price only appears in BKICMSTR, I'll write my own update script and take my chances.

ISTech Support Forum » Powered by YaBB 2.1!
YaBB © 2000-2005. All Rights Reserved.