|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: Question on mapping using Mercator
Michael is absolutely correct. Another tip is to make sure that only one
of the parameters passed to the functional map iterates, else you get far
too many outputs. If one input has x loops and another y, you will get x*y
outputs, which isn't what you normally want. If you need to pull data from
second input loop, (i.e. any segment or group with more than one possible
instance) pass the whole file/interchange as a parameter and use EXTRACT
or CHOOSE to get what you need. Also remember that if any parameter
evaluates to "NONE" then the functional map will not be called, so do not
use optional data items as parameters to functional maps creating
mandatory outputs!.
Hope this helps,
Graham.
From: "Michael Mattias" <
Reply to: "Michael Mattias"
Tue 24/12/2002 12:11
To: <
Cc:
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/
[Non-text portions of this message have been removed]
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
