Conversion Data

[Chris Kelleher]

Hi peggers,
As anyone out there gone thru a mainframe to symix conversion. we are
interested in determining the required fields symix needs to run.
We are on syteline version 4.0. Symix's documentation is poor. Thier
descriptions of the fields are impossible to follow. We need to know what
field name means and what should go into that field and is it necessary to
populate all fields. Any help would be appreciated.

TIA

 

[Chris Kelleher]

In syteline 2, if you go under help and import it talks about the Data
Import Utility. There are certain files (about 6) that you can import with
text. I'm sure there are many others, like jobs that need to be converted,
but it's a start. We did our conversion over a year ago, so I'll try to
see what other files we did.

 

[Chris Kelleher]

We do a lot of conversions for our customers. The thing you should do prior
to conversion is go through training as well as some Conference Room
Piloting. This allows you to know how items/customers/etc. will be entered
and coded during actual production. Once you know that, you can manually
enter one item/customer/etc. for each scenario. You then dump the table(s)
and see how the fields were assigned.

The other process would be to manually add an item/customer/etc. and put the
bare minimum data in the screen (it should be the fields that are yellow
that are mandatory). Once the record is saved, go to the query editor and
display the record with 1 col stream-io.

The conversion program writing is typically the smallest part of the project
with the "mapping" of the old data to the new SyteLine fields being the
largest part, and the testing of the data (through quick queries,
update/save tests and full system testing) taking second place in the amount
of time consumed.

I would recommend getting the data converted into a Conference Room Pilot
database so the users can bang on it prior to "go live".

That's my $.02

Tony Petrucciani
Single Source Systems, Inc.