[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

Re: <tech> Syteline 830/850 mapping assistance

Re: [EDI-L] <tech> Syteline 830/850 mapping assistance

> 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


















Sat Jun 17, 2006 2:30 pm


"Michael Mattias" <michael.mattias@...>
http://profiles.yahoo.com/mcm_talsystems
Offline


EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.