|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: Question on mapping using Mercator
Functional maps is the only way. Initially it may sound a bit strange,
but once you get used to it, its quite simple. I've been usiung
Mercator for 1lmost one and half years, and I can tell you it takes a
bit of getting used to working on Mercator, if you come from a java\c++
programming background.
But regarding teh problem Michael mentioned, I think if you are using
v6 (I'm using v5), then it provides an inbuilt function called
FORMATIN(...) which can solve the input and output being in sync
problem.
Sachin
-----Original Message-----
From: michael.mattias [mailto:
Sent: Tuesday, December 24, 2002 8:12 PM
To: EDI-L; michael.mattias
Subject: Re: [EDI-L] Question on mapping using Mercator
----- Original Message -----
From: <
To: <
Sent: Monday, December 23, 2002 6:56 PM
Subject: [EDI-L] Question on mapping using Mercator
> I'm currently working for a client who uses Mercator to handle its
> mapping...
> do you have to create another functional map for the detail level? For
> example, on an 856 ASN, you'll have one shipment, but you may have
> ten different PO's going out on that shipment. Do you have to create
> another functional map to map each PO level, or is there a Loop
> function that will create each PO as a loop?
You got it. Mercator always creates output "straight down the page" (No
DO...LOOP or FOR..NEXT or IF.. GO TO) so whenever you need
one output per input with a variable number of inputs you need a
functional map. No other way.
Here's a tip for your ASN map: use a passed INDEX($) to each level of
functional map to control your HL01 numbering; you will also
find it handy to pass a 'parent HL01' value as a parameter as well.
Depending on how deep you have to nest the HL loops, passing
these as parameters instead of using COUNT() all the time will speed up
your map.
Of course, you could always engage a qualified Mercator consultant to
do that 'first' ASN for you, and then use that as a guide for
future ASNs (or other deeply-nested outbound documents).
But realistically I've found the bigger problem is getting the input
defined correctly: the type tree for the application interface
file needs to be set up with the 'occurs' in synch with the output
requirements. That all by itself may require a separate
functional map.
Michael Mattias
Tal Systems, Inc.
Racine WI
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/
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
