|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: TRADACOMS structure clarification
Quoted text is from
< by Chinmoy Das
<
>What I found in the input file provided to me was that it had the
>following sections i.e ORDHDR, then the ORDERS, then the ORDTLR. But
>when I went through the TRADACOMS specifications I found that these are
>three different message sets. But the input file supplied to me has all
>the three messages together.
>
>How do I code this map? I am using GENTRAN Server and Application
>Integration for mapping. So when I build a new map I am selecting
>ORDERS but what about the ORDHDR and ORDTLR messages that is also
>included in the input file? How do I translate that? Do I have to
>create three separate maps? Or is there any way to process three
>message sets at one time.
The combination of an initial ORDHDR message, one or more ORDERS, and
then an ORDTLR trailer message is a single transaction in Tradacoms
(they call it a 'file'). The ORDERS messages act as a sort of repeating
group within the transaction. I am sorry but I can give you no specifics
about how to process this using Gentran. The only thing which vaguely
resembles this sort of structure in EDIFACT which I can think of offhand
is an interchange containing INVOIC'es and a TAXCON message, where you
have different messages in an interchange which are nevertheless closely
related. If Gentran can handle this then you should be able to use the
same sort of approach for Tradacoms.
Incidentally, it is also possible for an orders file to contain a fourth
and final message type, an RSGRSG reconciliation message.
Regards
Chris
--
Chris Johnson mobile:+44 (0)7785 302122
EDIMatrix Ltd work: 0845 126 0680 or +44 20 8559 2454
fax: +44 (0)20 8559 2497
EDI website http://www.edimatrix.co.uk
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
