Using generic maps with many customers requires excellent analysis, testing and
continuous documentation. I tend to use generic maps for inbound documents but
individual maps for outbound documents. I found I had too many flavors of
outbound maps which created more work in testing and documentation than was
saved by using a generic map. I keep a generic format for my outbound docs
that I copy and use to create the specific outbound map. Inbound, on the other
hand is easier.
With gentran server you have to match the version to the envelope and the data
so you have to have a map for each version (4010, 5010 etc) of a document you
receive. There are many ways to use generic maps which you will need to
analyze for yourself based on your data. For instance you can nest rules to
determine what qualifiers you are looking for to identify items (UPC's,
customer items, vendor skus) in such a way that you always take the "UP"
qualifier over the "UK" for instance (or vice versa) but settle for the other
if that is all you get. Or you could set up partner tables to hold the
qualifiers you are going to be looking for in their data. I never put code in
a map that refers to a specific customer. If that is required then they
require their own map.
The biggest plus is that 99% of the time I can start a new partner with inbound
data and my generic maps require no development. Occasionally I have a partner
who uses qualifiers in exact opposition to the way others use them and that
requires them to have their own map (unless you use the partner table method).
The downside is of course testing when you have to modify the generic map. I
generally make my change in test, run production data for all customers through
test and use ultraedit compare to verify that the only differences in the
production and test output are control numbers and anything else I intended to
change.
On Dec 29, 2012, at 7:01 PM, balaphani wrote:
> Hello All,
>
> We are using Gentran server 6.1, OS: 5.3 unix.
> Our client has several Trading partners(some how around 300) and we are using
> different map for each TP. Depending up on the requirement of TP, mapping
> changes.
>
> Now discussion was going to use generic maps to give better performance to
> the EDI maps and to reduce hours of estimation to developments
>
> 1. Could any one please suggest how this needs to be executed in Gentran
> Server?
> 2. Using generic maps; will it be really helpful compare with using different
> maps?
> 3. How many hours of estimations does usually a normal & critical map will be
> given.?
> 4. Please let me know Positive & negative points of using Generic maps
>
> Thanks in advance
> V Balaphanindra
>
>
[Non-text portions of this message have been removed]
------------------------------------
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
[email protected]
[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
