Hi,
Few thoughts:
1. As you must be knowing there are some tailor-made Translator S/W
available in the market that do this job of mapping. You may have to buy
those. These are generally used if the data that you exchange with your
Business partner is very large and also not consistent (meaning to say that
you may conditionally receive some segements/transaction sets). In this case
its advisable to use the Translator.
If your message content is very limited (say 10 - 25 fields) then its not
advisable to spend for a Translator.
2. If you are in the process of setting up your system and you expect
changes in the datamodel its good that you do or other way with your
business partner.
3. Last but never the least - going by the ground rule of any business -
'Customer is King' or 'Customer is God' - if you are the customer then you
may aswell ask your supplier to do the mapping in the message file that he
sends. If you are the supplier then you win his good-books with this service
for him.
Hope this helps.
Anybody with other suggestions/practices please exchange.
Regards,
Priyesh Waghray
Application Architect
Baan.
Baan - An Invensys Company.
*+91 40 3100525.
-----Original Message-----
From: Geoffrey Carter [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 02, 2002 5:27 PM
To: XMLEDI Group
Subject: Mapping
A question - it is rare to be able to get both partners in an
interchange to use the same schema / standard. Someone has to map.
What is the view as to who should best do this? As a general rule I
prefer to take a message in the format of the issuer and map to my
schemas that tie in with my back-end processes. Similarly I prefer to
send a message in my format and let the recipient map. Is there a "best
practice" view amongst the group?
Geoff Carter
---
You are currently subscribed to xmledi-group as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---
You are currently subscribed to xmledi-group as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
