|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: Re: beginner question: X12 flavours

Charles,
Since your partner evidently doesn't have a grasp of X12 EDI, the chances of
them correctly implementing an EDI solution without help in three days is
nil. How long will it take them to hire or develop the skills? Who knows?
You could map the Oracle POO (puchase order, outbound) record set directly.
While this is not an elegant solution, if it is strategicly important to
have this customer purchase using electronic data transfer, then it may be
your quickest solution.
Nevertheless, your customer will certainly want to implement X12 or EDIFACT
if they will be using EDI to purchase or sell to other partners. Maybe you
could suggest that they join this list, or a local eCommerce or EDI users
group.
Remember that X12 is just one flavor of EDI. The term EDI means Electronic
Data Interchange. We have implemented X12 and UN/EDIFACT because these
standards address concerns that make EDI simpler and more reliable. But
that doesn't mean that adherance to the standards is the only way to get the
job done. Flat file data transfer is still widely used, and XML is being
used more and more as well. Its all EDI. But Oracle interface files are a
pain, and you might decide to avoid having to map them. Moreover, when you
step away from the standards, you lose the standardized acknowledgements,
logging, control numbers, duplication detection, etc. that the standards in
partnership with your EDI software provide.
Good luck,
Art Douglas
Manager, eCommerce Systems
PaperPak
San Dimas, CA
909-971-5025
"There are no victories at bargain prices."
-- Dwight D Eisenhower
-----Original Message-----
From: cmcf_au <
[mailto:
Sent: Monday, January 27, 2003 6:33 PM
To:
Subject: [EDI-L] Re: beginner question: X12 flavours
Thx Art--much appreciated!
I've been in contact with the customer and confirmed that they are indeed s=
ending us an Oracle Interface file. They had been under the impression that
=
this was itself an X12 file--they're now going to see if they can find out
h=
ow to generate valid X12.
Does anyone know if this is likely to be a relatively simple process?We are=
hoping we can get it running in the next three days--does this sound
wildly=
unrealistic in other people's experience?
Our other option is to extract the data we need from the Interface file as =
is, which should be doable in that time frame based on what I've seen so
far=
.
Best regards
charles
--- In "Art Douglas (San Dimas)" <ADouglas@p...> wro=
te:
> Charles,
>
> Your customer has sent you an Oracle EDI Interface file. This is the fil=
e
> Oracle Applications produces, and the expected next step is for them to
> translate it to EDI format, using X12. Either they don't understand EDI,=
or
> they mistakenly sent you the wrong file.
>
> I suggest you contact them and make them aware that you did not receive X=
12.
> Hopefully, if they are sophisticated enough to have implemented Oracle
> Applications, they should also have an understanding of the EDI interface=
> and will be able to help.
>
> Good luck,
>
> Art Douglas
> Manager, eCommerce Systems
> PaperPak (an Oracle Apps shop)
> San Dimas, CA
> 909-971-5025
>
> "There are no victories at bargain prices."
> -- Dwight D Eisenhower
>
>
> -----Original Message-----
> From: cmcf_au <charlesf@c...> [mailto:charlesf@c...]
> Sent: Monday, January 27, 2003 3:10 PM
> To:
> Subject: [EDI-L] beginner question: X12 flavours
>
>
> Hi all
>
> A new customer is asking my company to implement what they've called an X=
12
> 850 for them. In my (very limited) experience with X12 formats I expected=
a
> PO with a data format that used a sequence of asterix-delimited
> lines--identified by 2 or 3 character codes such as "ISA", "GS", "ST", "B=
EG"
> etc--that were typically around 20-50 characters in length.
>
> This customer however--who is using Oracle R11i--is supplying a PO format=
> that's devoid of delimiter chars (other than CR) & primarily identifies d=
ata
> positionally with flds they call Record Number, Record Layout, and Record=
> Layout Qualifier. These flds are positioned at col 92-100 and contain
> combined values like "0010CTCTL" on line 1 of the transaction, "0020A1TH1=
"
> on line 2, "0030A2TH2" on line 3 & so on. The sample data lines are
> typically around 200 - 500 chars in length (mostly whitespace).
>
> The format is reasonably easy to follow, but its radically different from=
> what I was expecting! I had assumed X12 to be a reasonably homogenous for=
mat
> based on premises reasonably similar to EDIFACT, but this current custome=
r
> seems to have blown that idea out of the water :)
>
> Is anyone able to help me out by commenting on the number of X12 flavors
> around, &, if they recognize it, maybe identifying the example I've
> described here from this Oracle customer?
>
> Many thanks in advance!!!! My inexpert web searches so far haven't shed a=
ny
> light on the subject, and I'm keen to get some independent input before I=
go
> back to the customer.
>
> Regards,
> Charles Ferguson
>
>
>
> To unsubscribe from this group, send an email to:
>
> Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
> <OFF-TOPIC>
> Access the list online at: http://groups.yahoo.com/group/EDI-L
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/=
>
>
>
> [Non-text portions of this message have been removed]
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
[Non-text portions of this message have been removed]
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|