Re: <tech> Syteline 830/850 mapping assistance

Michael,
Thanks for responding, but you read way too much into my question. The Flat
File guidelines I have for the 830 and 850 map are extremely vague.

By a "Pre-Mapping" document, I was hoping someone had already created a
document for Syteline mapping that would clarify where to map the various
ANSI elements to the various flat file fields. This is usually done in an
Excel spreadsheet. I learned this technique years ago when I worked at St.
Paul Software. It says a tremendous amount of time when creating maps.

Some flat file definitions I've mapped from in the past have, reference the
various EDI elements that the data should be populated from. The wording in
the documentation I have from Syteline doesn't provide any type of guidance
as to what elements should be used to map to the flat file.

Thanks,

J



Re: <tech> Syteline 830/850 mapping assistance
Posted by: "Michael Mattias" mcm_talsystems
Date: Sat Jun 17, 2006 7:32 am (PDT)

> I'm working on creating an integrated 850 and 830 document using Catalyst
> Mapper.
>
> Has anyone done a "pre-mapping" matrix which would assist me in trying to
> determine where I should map the ASNI segments to the flat file fields?
> The Syteline documentation for the flat file that I have is lacking.

I'm not exactly sure what you mean by an "integrated 850 and 830" document (
a common intermediate output which supports both
inbound documents? Or maybe outbound documents?)

But...

... There's not that much difference in function between 830 Planning
Schedule with Blanket Order Release and 850 Purchase Order: at
their core, both are not much more than PO#, Part #, Quantity and Date
Wanted. Sure the 830 will have both "firm" and "planned" and
the 850/860 are always "firm" but what you are going to do with the
'planned' is extremely application-dependent.

Seems to me a blanket order release (a "firm" on the 830) is essentially an
860 Purchase Order Change; maybe you could look at the
interface you use for that document? "Pretending" one document is actually
some other document is not really that weird: e.g., I
have one client who gets '862 Shipping Schedule' which we just treat as an
'830 Planning Schedule with Blanket Order Release.'
Works out just fine, and we only need one(1) interface even though it's
nominally two different document types. (We also get EDIFACT
DELFOR but I won't count that as an extra document because that's pretty
much a one-for-one equivalent to ANSI 830).

But regardless, because the number of significant data items is so small, I
would think time spent developing "pre-mapping"
specifications would be largely time wasted, since the needed PO#, Part#,
Quantity and Date Wanted are only four (4) pieces of
information to gather.

Since you are a regular and long-time poster here, I can only assume there
is a lot more to your application requirements than
described above - or you would have had this job done by now and wouldn't be
asking.

Maybe a little more explanation of the application would help. (I guarantee
it would help me)

Michael Mattias
Tal Systems, Inc.
Racine WI