Migrating Sales History

[Chris Kelleher]

SL4.5
As some of you may have noticed from earlier postings, I am attempting to
migrate sales history (both inv-hdr & corresponding inv-item(s)) into SL. I
have been advised to avoid putting this migrated history into the SL inv
tables due to the possibility of corrupting our AR. So, for the love of
God, can anyone offer any suggestions/comments about creating CO records w/
a status of "C" (or completed) for this imported data?

~~~~~~~~~~~~~~~~~~~~~~~~
Michael Fisher
Programmer/IT Developer
Wallingford Electronics
~~~~~~~~~~~~~~~~~~~~~~~~

 

[Chris Kelleher]

Personally, I would rather create the coh, citemh table and tell the Sales
persons to use Historic Order Query ...

Did you consider a custom "historic" db with a small programs that offers a
connect menu ?

Eric.

The way I would approach this is very simple:
Print the tables schema, and create a pseudo dump-file, load the "converted
data" via progress
You can have the fields "delimited" and use $DLC/bin/quoter to prepare them
...

 

[Chris Kelleher]

Someone can correct me if I'm wrong - but doesn't A/R use the artran for
POSTED invoices, and arinv for UNPOSTED invoices? What would be the harm in
Michael adding history information to inv-hdr and inv-item? Personally I
prefer to run all sales analysis report from invoices NOT from orders - I
figure they are more reliable - and don't get deleted.

 

[Chris Kelleher]

You are right about this. You can use these tables. The biggest problem is
the sequencing of the Invoice Numbers. He is coming from an unrelated
system so this would only work if the invoice numbers would all be below the
current invoice numbers or the last invoice number in lasttran.

 

[Chris Kelleher]

Thx to all who replied. After further discussion I think we will end up
importing these into the inv-hdr and inv-item tables after all. Denise it
seems you were correct. The consensus is that there's nothing wrong w/
importing the info into these tables, as long as the invoice numbers would
all be below the current invoice numbers or the last invoice number in
lasttran.

 

[Chris Kelleher]

You can put the sales history into inv-hdr and inv-item. I would also
create the completed co and coitem records if you expect to report sales
info using standard SyteLine reports. Technically speaking, you might also
consider populating the co-ship table too, if you have reports that rely on
data from that table.

All that aside, what type of reports are your users expecting? I would go
to all this trouble only if they are expecting to use standard SyteLine
reports against this data. If they only need limited or summarized
information, I agree with Eric that you should populate an external (custom)
database with this data and produce the necessary reports.

Also consider that placing more data in co, coitem, inv-hdr, invitem, and
co-ship may cause your existing reports to process longer.